[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
I have the same issue here, random freeze, espacially when working hard
on the video card.
I'm a bit worried because they claim here that 5.4.0 does not solve it
https://bugzilla.kernel.org/show_bug.cgi?id=205545
** Bug watch added: Linux Kernel Bug Tracker #205545
https://bugzilla.kernel.org/show_bug.cgi?id=205545
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Here is an interesting observation (I think). I have a demo program that
makes strong use of the GPU. Here is what happens with two close kernel
versions:
* 5.3.0-45-generic
=> everything ok, no hang, no noise
* 5.3.0-46-generic
=> I CAN HEAR COIL NOISE when running the demo! And the whole system FREEZES
(as described above) regularly for 3-4 seconds, every 20 to 40 seconds, and
dmesg shows
Apr 8 08:31:47 XPS-13-9350 kernel: [ 1604.860896] i915 :00:02.0: GPU HANG:
ecode 9:0:0x, hang on rcs0
Apr 8 08:31:47 XPS-13-9350 kernel: [ 1604.861939] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Apr 8 08:32:51 XPS-13-9350 kernel: [ 1668.814516] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Apr 8 08:33:13 XPS-13-9350 kernel: [ 1690.794398] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Apr 8 08:33:39 XPS-13-9350 kernel: [ 1716.814185] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
This is on XPS13 with intel graphics.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
@oded, thanks for the message!
Maybe it's a different bug, however I think that the bug is still very close.
If you look at the original poster's dmesg output, you see that the freezes
(reported by the "hang" message) also occur multiple times.
The only difference is that the frequency is about every 2 seconds, which makes
the user feel it completely freeze all the time.
In my case it was a bit less frequent, but maybe that's just because I
was putting less strain on the GPU.
I will open a new ticket, as you suggested
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
Installati
[Kernel-packages] [Bug 1872009] Re: System Freeze with "Resetting rcs0 for hang on rcs0"
I first posted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395 because I thought it was related -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: New Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872009] Re: System Freeze with "Resetting rcs0 for hang on rcs0"
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+attachment/5351024/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: New Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872009] [NEW] System Freeze with "Resetting rcs0 for hang on rcs0"
Public bug reported: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: New Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872009] Re: System Freeze with "Resetting rcs0 for hang on rcs0"
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+attachment/5351025/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: New Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872009] Re: System Freeze with "Resetting rcs0 for hang on rcs0"
*** This bug is a duplicate of bug 1872001 *** https://bugs.launchpad.net/bugs/1872001 you're right, it seems to be exactly the same bug. I am attaching my test program (binary: you need the SDL library, and maybe more) ./test.exe it will open a graphics window and run a simulation of virus transmission (human virus, not computer virus, there is no risk for the computer ;) ) ** Attachment added: "test.exe" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+attachment/5352362/+files/test.exe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: Confirmed Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I agree, it seems exactly the same as bug #1872009 I have uploaded a test program (needs SDL1.2) that kind of immediately triggers the hang https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+attachment/5352362/+files/test.exe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I'm sorry I realized you need more dependencies to run my test program, it's going to be complicated. But I think any program that intensively sends data to the GPU should trigger the problem as well -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.ven
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
OK here is a new version, I think now you just need to do sudp apt install libsdl-ttf2.0-0 ./test.exe it should work ** Attachment added: "test.exe" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5352404/+files/test.exe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.v
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
interestingly, my demo runs also 25% faster on 5.3.0-45 than on 5.3.0-46... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0K0DFT:rvr
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
and 50% faster on 4.4.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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0K0DFT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family:
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
running 5.3.0-52-generic for a couple of weeks I still have occasional hangs, maybe not triggered by the same things. It seems for instance to happen when I open a PDF from within chromium-browser. It lasts 3-4 seconds. [12467.199744] perf: interrupt took too long (2520 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 [12872.912144] i915 :00:02.0: GPU HANG: ecode 9:1:0xfffe, in chromium-browse [6961], hang on rcs0 [12872.913153] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 Upgra
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
So, this problem is serious. I am surprised that no one else has mentioned the coil noise issue. I can repeatedly and consistently hear it on 5.3.0-46, while it's absent in 5.3.0-45. I think this is the sign of something quite bad happening. (maybe too much data transiting on the bus between cpu and gpu?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@Andrea, for me this seems to solve the problem. Thanks! (except that my demo is still slightly slower than with 4.4.0 (13fps instead of 15fps) but this is probably unrelated) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.mod
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@arighi I cannot test with glxgears because it syncs with screen refresh, so always 60FPS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@arighi It's graphical demo using openGL via SDL1.2 where 1000 small discs move around and all collisions are detected, and print FPS. It uses both CPU and GPU quite heavily. (On my XPS 13 9350, intel_gpu_top reports about 55% GPU usage, and top reports 46% CPU). I was developing this for my research and this is why the hanging bug stroke me strongly. I made quick tests with the kernels that are currently on my laptop: 5.3.0-48-generic #41+lp1861395v1: 12 FPS 5.3.0-469 FPS + Noise (inbetween hangs, of course) 5.3.0-45 12 FPS 5.3.0-42 12 FPS 4.4.0 15 FPS (aside remark: on my antique desktop PC with Athlon 64 5600 CPU and Radeon HD6450 GPU, the performance is better: 16FPS, which is quite humiliating ;) ) ** Attachment added: "test demo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5360104/+files/test.exe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLi
[Kernel-packages] [Bug 1895378] [NEW] cpu frequency stuck to max when pugging USB device
Public bug reported: When I start my laptop with AC plugged in, the CPU frequency oscillates around 1.5Ghz, but as soon as I plug some USB device, like an external mouse, the frequency goes up to the max (3.2Ghz) and stays there, even though the system monitor tells me that no app is eating CPU power. (see picture) If I unplug the mouse, this doesn't go back to normal: still stuck max frequency. If I start my laptop with mouse already plugged in, it starts normally (scalable frequency around 1.5Ghz), if I unplug the mouse, still good, but if I plug the mouse again, it jumps to max frequency and stays there. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cpufreq.png" https://bugs.launchpad.net/bugs/1895378/+attachment/5410077/+files/cpufreq.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895378 Title: cpu frequency stuck to max when pugging USB device Status in linux package in Ubuntu: New Bug description: When I start my laptop with AC plugged in, the CPU frequency oscillates around 1.5Ghz, but as soon as I plug some USB device, like an external mouse, the frequency goes up to the max (3.2Ghz) and stays there, even though the system monitor tells me that no app is eating CPU power. (see picture) If I unplug the mouse, this doesn't go back to normal: still stuck max frequency. If I start my laptop with mouse already plugged in, it starts normally (scalable frequency around 1.5Ghz), if I unplug the mouse, still good, but if I plug the mouse again, it jumps to max frequency and stays there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895378] Re: cpu frequency stuck to max when pugging USB device
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+attachment/5410078/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895378 Title: cpu frequency stuck to max when pugging USB device Status in linux package in Ubuntu: New Bug description: When I start my laptop with AC plugged in, the CPU frequency oscillates around 1.5Ghz, but as soon as I plug some USB device, like an external mouse, the frequency goes up to the max (3.2Ghz) and stays there, even though the system monitor tells me that no app is eating CPU power. (see picture) If I unplug the mouse, this doesn't go back to normal: still stuck max frequency. If I start my laptop with mouse already plugged in, it starts normally (scalable frequency around 1.5Ghz), if I unplug the mouse, still good, but if I plug the mouse again, it jumps to max frequency and stays there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895378] Re: cpu frequency stuck to max when pugging USB device
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+attachment/5410079/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895378 Title: cpu frequency stuck to max when pugging USB device Status in linux package in Ubuntu: New Bug description: When I start my laptop with AC plugged in, the CPU frequency oscillates around 1.5Ghz, but as soon as I plug some USB device, like an external mouse, the frequency goes up to the max (3.2Ghz) and stays there, even though the system monitor tells me that no app is eating CPU power. (see picture) If I unplug the mouse, this doesn't go back to normal: still stuck max frequency. If I start my laptop with mouse already plugged in, it starts normally (scalable frequency around 1.5Ghz), if I unplug the mouse, still good, but if I plug the mouse again, it jumps to max frequency and stays there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895378] Re: cpu frequency stuck to max when pugging USB device
sorry I'm running KDE neon, and they don't let me install apport without breaking neon-apport, which I'd prefer not do. But I can send any info you wish ** 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/1895378 Title: cpu frequency stuck to max when pugging USB device Status in linux package in Ubuntu: Confirmed Bug description: When I start my laptop with AC plugged in, the CPU frequency oscillates around 1.5Ghz, but as soon as I plug some USB device, like an external mouse, the frequency goes up to the max (3.2Ghz) and stays there, even though the system monitor tells me that no app is eating CPU power. (see picture) If I unplug the mouse, this doesn't go back to normal: still stuck max frequency. If I start my laptop with mouse already plugged in, it starts normally (scalable frequency around 1.5Ghz), if I unplug the mouse, still good, but if I plug the mouse again, it jumps to max frequency and stays there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
Christopher, I have upgraded to 3.15-rc8, but the problem is still there. uname -a Linux pr036037 3.15.0-031500rc8-generic #201406012235 SMP Mon Jun 2 02:36:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux dmesg output = [...] 488.947955] cfg80211: (5724 KHz - 6588 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) [ 4940.374152] psmouse serio1: Trackpad at isa0060/serio1/input0 lost sync at byte 1 [ 4940.386220] psmouse serio1: Trackpad at isa0060/serio1/input0 - driver resynced. [11987.705683] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training [11987.712346] [drm:intel_dp_complete_link_train] *ERROR* failed to start channel equalization [11987.743541] [drm:cpt_verify_modeset] *ERROR* mode set failed: pipe B stuck [11987.807522] [ cut here ] [11987.807560] WARNING: CPU: 2 PID: 1364 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_display.c:9761 check_encoder_state+0x1fa/0x270 [i915]() [11987.807562] encoder's hw state doesn't match sw tracking (expected 1, found 0) [11987.807563] Modules linked in: ctr ccm snd_usb_audio snd_usbmidi_lib snd_hrtimer nvram pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev btusb snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic dell_wmi sparse_keymap snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dcdbas snd_pcm kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd microcode snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 snd_seq iwldvm joydev snd_seq_device serio_raw mac80211 snd_timer iwlwifi snd mei_me lpc_ich cfg80211 mei soundcore intel_smartconnect rfcomm bnep bluetooth 6lowpan_iphc parport_pc ppdev mac_hid lp parport binfmt_misc hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse drm ahci libahci wmi video [11987.807607] CPU: 2 PID: 1364 Comm: Xorg Tainted: G OE 3.15.0-031500rc8-generic #201406012235 [11987.807609] Hardware name: Dell Inc. Dell System XPS L321X/085X6F, BIOS A08 01/22/2013 [11987.807610] 2621 880119057b38 81762641 0007 [11987.807613] 880119057b88 880119057b78 81069e2c 0008030419057b88 [11987.807616] 880119022000 88003662c320 88003662c000 [11987.807618] Call Trace: [11987.807624] [] dump_stack+0x46/0x58 [11987.807628] [] warn_slowpath_common+0x8c/0xc0 [11987.807631] [] warn_slowpath_fmt+0x46/0x50 [11987.807650] [] check_encoder_state+0x1fa/0x270 [i915] [11987.807667] [] intel_modeset_check_state+0x5d/0xa0 [i915] [11987.807684] [] intel_set_mode+0x25/0x30 [i915] [11987.807699] [] intel_crtc_set_config+0x196/0x2f0 [i915] [11987.807703] [] ? kmem_cache_alloc_trace+0x1b4/0x1f0 [11987.807718] [] drm_mode_set_config_internal+0x60/0xf0 [drm] [11987.807731] [] drm_mode_setcrtc+0x280/0x4e0 [drm] [11987.807743] [] ? drm_modeset_unlock_all+0x52/0x60 [drm] [11987.807753] [] drm_ioctl+0x25b/0x580 [drm] [11987.807765] [] ? drm_mode_setplane+0x3f0/0x3f0 [drm] [11987.807769] [] do_vfs_ioctl+0x75/0x2c0 [11987.807772] [] ? syscall_trace_enter+0x165/0x280 [11987.807775] [] ? __fget_light+0x25/0x70 [11987.80] [] SyS_ioctl+0x91/0xb0 [11987.807780] [] tracesys+0xe1/0xe6 [11987.807782] ---[ end trace 6a4eb77f7ea2ce64 ]--- [11987.807809] [drm:intel_pipe_config_compare] *ERROR* mismatch in has_dp_encoder (expected 1, found 0) [11987.807811] [ cut here ] [11987.807828] WARNING: CPU: 2 PID: 1364 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_display.c:9834 check_crtc_state+0x255/0x340 [i915]() [11987.807829] pipe state doesn't match! [11987.807830] Modules linked in: ctr ccm snd_usb_audio snd_usbmidi_lib snd_hrtimer nvram pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev btusb snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic dell_wmi sparse_keymap snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dcdbas snd_pcm kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd microcode snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 snd_seq iwldvm joydev snd_seq_device serio_raw mac80211 snd_timer iwlwifi snd mei_me lpc_ich cfg80211 mei soundcore intel_smartconnect rfcomm bnep bluetooth 6lowpan_iphc parport_pc ppdev mac_hid lp parport binfmt_misc hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse drm ahci libahci wmi video [11987.807867] CPU: 2 PID: 1364 Comm: Xorg Tainted: GW OE 3.15.0-031500rc8-generic #201406012235 [11987.807868] Hardware name: Dell Inc. Dell System XPS L321X/085X6F, BIOS A08 01/22
[Kernel-packages] [Bug 1171257] Re: 8086:0085 wireless lan interruptions and Microcode SW error detected. Restarting 0x82000000
I confirm that this bug (same as #779159) happens sytematically on my laptop running ubuntu 12.04 LTS (with up-to-date upgrades) and that it seems to be solved by reverting to older firmware iwlwifi-4965-ucode-228.57.2.23 as suggested by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/779159/comments/11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1171257 Title: 8086:0085 wireless lan interruptions and Microcode SW error detected. Restarting 0x8200 Status in “linux” package in Ubuntu: Expired Bug description: likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/779159 Same issue description as for bug #779159, wlan works but with many interruptions. Running command dmesg | grep "SW error" shows a large occurence of the following log trace : iwlwifi :25:00.0: Microcode SW error detected. Restarting 0x200. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-40-generic 3.2.0-40.64 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lab1948 F pulseaudio /dev/snd/controlC0: lab1948 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd152 irq 56' Mixer name : 'IDT 92HD81B1X5' Components : 'HDA:111d7605,103c1631,00100105' Controls : 19 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xd100 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Mon Apr 22 00:40:59 2013 HibernationDevice: RESUME=UUID=2ab2a97a-a0ed-40d4-aebe-da55f3ee7ac2 MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-40-generic root=UUID=9c1ce852-768c-4237-91a8-090079d27b1b ro RelatedPackageVersions: linux-restricted-modules-3.2.0-40-generic N/A linux-backports-modules-3.2.0-40-generic N/A linux-firmware1.79.2 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.22 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.39 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
I still have the same problem with kernel 3.13.0-35 I'm sorry, I didn't have the time to bisect; this is my work laptop and it's not so easy to install many kernels. The tests I did: 3.12.0-031200: GOOD 3.13.0-24: BAD after 5 sleep/wake up 3.15.0-031500rc8: BAD after 1 sleep/wake up 3.13.0-35: BAD after 2 sleep/wake up I'll try to bisect more properly when I have the time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in “linux” package in Ubuntu: Expired Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 06:57:33 2014 xserver.configfile: None xserver.errors: Failed to load module "displaylink" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4920 vendor
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
I'm progressing slowly in my dissection: 3.13.0-17.37: BAD 3.13.0-7.26: GOOD (but issue with USB sound card) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in “linux” package in Ubuntu: Expired Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 06:57:33 2014 xserver.configfile: None xserver.errors: Failed to load module "displaylink" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4920 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lis
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
@Aldo 3.13.0-12.32 seems to work for me. So what you can do: * download 4 packages in a new directory: (if you have a 64 bits system) https://launchpad.net/ubuntu/+source/linux/3.13.0-12.32/+build/5624936/+files/linux-headers-3.13.0-12-generic_3.13.0-12.32_amd64.deb https://launchpad.net/ubuntu/+source/linux/3.13.0-12.32/+build/5624936/+files/linux-image-3.13.0-12-generic_3.13.0-12.32_amd64.deb https://launchpad.net/ubuntu/+source/linux/3.13.0-12.32/+build/5624936/+files/linux-image-extra-3.13.0-12-generic_3.13.0-12.32_amd64.deb https://launchpad.net/ubuntu/+source/linux/3.13.0-12.32/+build/5624939/+files/linux-headers-3.13.0-12_3.13.0-12.32_all.deb * install all: cd to this directory and type sudo dpkg -i *.deb * then restart and at boot, make sure you select the 3.13.0-12 kernel (not the default 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/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in “linux” package in Ubuntu: Expired Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xor
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
** Changed in: linux (Ubuntu) Status: Expired => 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/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in “linux” package in Ubuntu: Incomplete Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 06:57:33 2014 xserver.configfile: None xserver.errors: Failed to load module "displaylink" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4920 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://la
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
so my conclusion is that * it works with 3.13.0-16.36 * it is broken in 3.13.0-17.37 what should I do next ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in “linux” package in Ubuntu: Incomplete Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 06:57:33 2014 xserver.configfile: None xserver.errors: Failed to load module "displaylink" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4920 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
I think I found what triggers the error (of course, this is just the
manifestation of the error, maybe not the root cause):
from 3.13.0-17.37 a limited number of "retries" has been introduced, which
fails after 7 retries; this seems to be not enough:
--- linux-3.13.0/drivers/gpu/drm/i915/intel_dp.c
+++ linux-3.13.0/drivers/gpu/drm/i915/intel_dp.c
@@ -537,6 +537,7 @@
uint8_t msg[20];
int msg_bytes;
uint8_t ack;
+ int retry;
if (WARN_ON(send_bytes > 16))
return -E2BIG;
@@ -548,18 +549,20 @@
msg[3] = send_bytes - 1;
memcpy(&msg[4], send, send_bytes);
msg_bytes = send_bytes + 4;
- for (;;) {
+ for (retry = 0; retry < 7; retry++) {
ret = intel_dp_aux_ch(intel_dp, msg, msg_bytes, &ack, 1);
if (ret < 0)
return ret;
if ((ack & AUX_NATIVE_REPLY_MASK) == AUX_NATIVE_REPLY_ACK)
- break;
+ return send_bytes;
else if ((ack & AUX_NATIVE_REPLY_MASK) ==
AUX_NATIVE_REPLY_DEFER)
- udelay(100);
+ usleep_range(400, 500);
else
return -EIO;
}
- return send_bytes;
+
+ DRM_ERROR("too many retries, giving up\n");
+ return -EIO;
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1322644
Title:
[Dell XPS 13 (L321X)] External monitor does not wake up after sleep
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
The problem started after I upgraded from kubuntu 13.10 to 14.04.
the monitor is connected to my laptop via a VGA mini display port.
At boot, it works correctly, but if the screen goes blank after some
inactivity, then it stays black forever.
WORKAROUND: If I unplug the VGA adapter, and plug it back, it works
again.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: kwin
CurrentDesktop: KDE
Date: Fri May 23 16:02:09 2014
DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sputnik-20120802-0
DistroCodename: trusty
DistroVariant: kubuntu
DkmsStatus:
fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed
fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed
vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:052e]
InstallationDate: Installed on 2012-11-13 (555 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf
in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13
LightdmGreeterLog:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun
fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
LightdmGreeterLogOld:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun
fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
MachineType: Dell Inc. Dell System XPS L321X
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic
root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash
crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago)
dmi.bios.date: 07/02/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 085X6F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L321X
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0
[Kernel-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep
this is just a reminder that the problem is still present with the latest ubuntu kernel 3.16.0-29-generic. bisecting is not completely obvious to me, so I didn't have the time to look into it yet. I just tested the precompiled kernels available in https://launchpad.net/ubuntu/trusty/+source/linux and noticed that the problem started to happen strictly after 3.13.0-16.36 ** Changed in: linux (Ubuntu) Status: Expired => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => 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/1322644 Title: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep Status in linux package in Ubuntu: Confirmed Bug description: The problem started after I upgraded from kubuntu 13.10 to 14.04. the monitor is connected to my laptop via a VGA mini display port. At boot, it works correctly, but if the screen goes blank after some inactivity, then it stays black forever. WORKAROUND: If I unplug the VGA adapter, and plug it back, it works again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri May 23 16:02:09 2014 DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sputnik-20120802-0 DistroCodename: trusty DistroVariant: kubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2012-11-13 (555 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13 LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Dell Inc. Dell System XPS L321X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 06:57:33 2014 xserver.configfile: None xserver.errors: Failed to load module "displaylink" (module does not exist, 0) xs
[Kernel-packages] [Bug 1591669] [NEW] duplicate touchpad reported and syndaemon/synclient does not work
Public bug reported: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: New Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
apport information ** Tags added: apport-collected xenial ** Description changed: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ - Of course this fix is not universal because I had to use the precise - name of the "false touchpad" as reported by xinput. + Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: san1743 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 + InstallationDate: Installed on 2016-06-03 (9 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0c45:670c Microdia + Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 13 9350 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-24-generic N/A + linux-backports-modules-4.4.0-24-generic N/A + linux-firmware1.157 + Tags: xenial + Uname: Linux 4.4.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/01/2016 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.3 + dmi.board.name: 09JHRY + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: XPS 13 9350 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682118/+files/AlsaInfo.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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "f
[Kernel-packages] [Bug 1591669] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682143/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682134/+files/AlsaInfo.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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-gene
[Kernel-packages] [Bug 1591669] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682125/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682137/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-gene
[Kernel-packages] [Bug 1591669] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682123/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/
[Kernel-packages] [Bug 1591669] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682130/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic
[Kernel-packages] [Bug 1591669] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682142/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4
[Kernel-packages] [Bug 1591669] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682141/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682127/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682136/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0
[Kernel-packages] [Bug 1591669] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682128/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-ge
[Kernel-packages] [Bug 1591669] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682124/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682145/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic
[Kernel-packages] [Bug 1591669] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682135/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A
[Kernel-packages] [Bug 1591669] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682131/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: san1697 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 + InstallationDate: Installed on 2016-06-03 (9 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0c45:670c Microdia + Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 13 9350 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-24-generic N/A + linux-backports-modules-4.4.0-24-generic N/A + linux-firmware1.157 + Tags: xenial + Uname: Linux 4.4.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserG
[Kernel-packages] [Bug 1591669] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682146/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic
[Kernel-packages] [Bug 1591669] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682140/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-2
[Kernel-packages] [Bug 1591669] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682129/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic
[Kernel-packages] [Bug 1591669] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682144/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-ge
[Kernel-packages] [Bug 1591669] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682122/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4
[Kernel-packages] [Bug 1591669] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682126/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4
[Kernel-packages] [Bug 1591669] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682138/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4
[Kernel-packages] [Bug 1591669] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682139/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/
[Kernel-packages] [Bug 1591669] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682147/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-
[Kernel-packages] [Bug 1591669] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682119/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
ABOUT THE LOGS: I'm sorry I'm not used to reporting bugs. After I received the email telling me to "apport-collect 1591669" I did it, but then I realized I had already implemented the "fix"... So I have removed the fix, rebooted, and re-run "apport-collect 1591669" ===> you may ignore #2 -- #14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSi
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
I think this is a regression: I've just tested a live USB Linux Mint 17.3 cinnamon (based on ubuntu 14.04) and there the touchpad is not duplicated. only "SynPS/2 Synaptics TouchPad" is reported by the system -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricte
[Kernel-packages] [Bug 1591669] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682120/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0
[Kernel-packages] [Bug 1591669] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1591669/+attachment/4682121/+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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1743 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-gene
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
** Description changed: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" - Identifier "touchpad ignore SynPS/2 Synaptics duplicate" - MatchProduct "SynPS/2 Synaptics TouchPad" - Option "Ignore" "on" + Identifier "touchpad ignore SynPS/2 Synaptics duplicate" + MatchProduct "SynPS/2 Synaptics TouchPad" + Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ - Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. - --- + Of course this fix is not universal because I had to use the precise + name of the "false touchpad" as reported by xinput. + + + --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: san1743 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0c45:670c Microdia - Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. - Bus 001 Device 002: ID 8087:0a2b Intel Corp. - 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 0c45:670c Microdia + Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: - linux-restricted-modules-4.4.0-24-generic N/A - linux-backports-modules-4.4.0-24-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-24-generic N/A + linux-backports-modules-4.4.0-24-generic N/A + linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. - --- - ApportVersion: 2.20.1-0ubuntu2.1 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: san1697 F pulseaudio - CurrentDesktop: Unity - DistroRelease: Ubuntu 16.04 - HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 - InstallationDate: Installed on 2016-06-03 (9 days ago) - InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0c45:670c Microdia - Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. - Bus 001 Device 002: ID 8087:0a2b Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - M
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
Hi Joe. I've just tested the latest kernel, but the bug is not fixed in 4.7.0-040700rc3-generic (same behaviour) ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work
another way to "fix" the bug is to suspend/resume. Indeed, after resume, the false device is removed. $ tail -n 3 /var/log/Xorg.0.log (EE) SynPS/2 Synaptics TouchPad: Read error 19 [ 285.414] (II) config/udev: removing device SynPS/2 Synaptics TouchPad [ 285.430] (II) UnloadModule: "synaptics" (but then the touchscreen doesn't work anymore... but this is probably a different bug) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu: Confirmed Bug description: This is on a Dell XPS 13 9350 DE running ubuntu 16.04. This laptop has a touchpad and a touchscreen. I'm reporting here about the touchpad. One can see from Xorg.0.log and "xinput list" that *two* touchpads are registered by the system one is called "DLL0704:01 06CB:76AE Touchpad" and the other "SynPS/2 Synaptics TouchPad" As a result, syndaemon is not working. To check this, open two terminals, press and hold some key, like "e" in one of them. It starts filling with "eee". Now while holding the key, use the touchpad to tap on the other terminal. Then "" fills the new terminal. Expected behaviour: tapping on the other terminal should have no effet, the "e"'s should continue to fill the first terminal. Moreover, configuring the touchpad with synclient is not working either. FIX: Since invoking xinput disable "SynPS/2 Synaptics TouchPad" has no effect, it is clear that this one is a "false" touchpad. Hence this fix is: Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf I added, line 29: Section "InputClass" Identifier "touchpad ignore SynPS/2 Synaptics duplicate" MatchProduct "SynPS/2 Synaptics TouchPad" Option "Ignore" "on" EndSection Now it works. The touchpad is correctly disabled when using the keyboard, and moreover I can configure it using synclient, or adding a file to /etc/X11/xorg.conf.d/ Of course this fix is not universal because I had to use the precise name of the "false touchpad" as reported by xinput. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: san1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7 InstallationDate: Installed on 2016-06-03 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
