Public bug reported:
I am encountering this following erratic error with Wily kernel 4.2.
With Kernel, 4.1 I did not encounter such issues with drm i915.
[ 5437.034758] [ cut here ]
[ 5437.034784] WARNING: CPU: 2 PID: 0 at
/build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i
Okay on my side, I am going to test with the latest mainline Kernel (4.3
rc1) once it will have landed to the repository. Currently, only the
Kernel headers are there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I tested with the latest upstream kernel (v4.3-rc1-unstable) and the
problem does not occur.
In summary :
linux-image-4.1.0-3-generic (4.1.0-3.3) amd64 : Ok
linux-image-4.2.0-7-generic (4.2.0-7.7) amd64 : Not Ok (Kernel DRM stack trace
mentionned in this bug report)
linux-image-4.2.0-10-generic
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1494903/+attachment/4467562/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494903
apport information
** Tags added: apport-collected
** Description changed:
I am encountering this following erratic error with Wily kernel 4.2.
With Kernel, 4.1 I did not encounter such issues with drm i915.
[ 5437.034758] [ cut here ]
[ 5437.034784] WARNING: C
** Attachment removed: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494903/+attachment/4467561/+files/JournalErrors.txt
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494903/+attachment/4467562/+files/ProcEnviron.
Christopher, understood. Thanks for the advice.
Reverse commit bisecting ? Easy, but needs some mental contorsion.
I started a "Reverse" bisect between v4.2 final and v4.3-rc1. The first
test kernel is built up to the following commit:
[dd5cdb48edfd34401799056a9acf61078d773f90] Merge
git://git.k
** Summary changed:
- Kernel 4.2 drm/i915 erractic error
+ Kernel 4.2 drm/i915 erratic error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494903
Title:
Kernel 4.2 drm/i915 erratic error
To manag
Bisect progress
*
Test kernel up to the following commit:
[f377ea88b862bf7151be96d276f4cb740f8e1c41] Merge branch 'drm-next' of
git://people.freedesktop.org/~airlied/linux
Result : No Stack trace (Bad)
*
Test kernel up to the following commit:
[a
*
Test kernel up to the following commit:
[97d3308ab245c51ae237b3444afa7ae87aa9bcd4] drm/i915: Add HAS_CORE_RING_FREQ
macro
Result : No Stack trace (Bad)
*
Test kernel up to the following commit:
[75289874e4484cd4702b3341b654b45b4a09b9d3] drm/i915
Christopher,
I have completed the reverse commit bisecting. it pointed me the
following commit :
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b1b38278e12b04cf9a227f6af2c24651cf6e8a85
Please find in attachment the "bisect log" file ans the "bisect
visualize" file
**
** Attachment added: "git bisect visualize"
https://bugs.launchpad.net/ubuntu/wily/+source/linux/+bug/1494903/+attachment/4469773/+files/bisect_visualize.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I was facing to this behaviour.
I blacklisted the dell_laptop module and this issue was solved. Now my keyboard
backlight act as it should be.
in /etc/modprobe.d directory
create this file blacklist-dell.conf
and add in it the followinf thing : blacklist dell_laptop
then excute : sudo update-i
I did not say that it was the solution.
I suggest this tip because at the moment NOT blackisting this module prevents
us to use the keyboard backlight feature.
This suggestion only focus on Dell Xps 13 9343, model that I own.
Blacklisting the module allows me to enjoy this feature.
--
You recei
14 matches
Mail list logo
