Has anyone tested if this bug is fixed in kernel 3.12 final released
today?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1167301
Title:
8086:0166 [ThinkPad Twist S230u 3347]
Till Kamppeter, I noticed you omitted following the kernel.org format,
on the grounds of you having identified the regression commit, and
others noted they are experiencing a similar issue. The kernel.org
format as outlined by Linus was created to be in addition to regression
commit identification
Christopher, the URL of my improved posting to the dri-devel mailing
list is:
http://lists.freedesktop.org/archives/dri-
devel/2013-September/046056.html
Also no reply so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Till, thanks for the URL.
Unfortunately, attachments are silently discarded before being posted to
the archive so only the direct subscriber would get the kernel.org
format information, versus wider audience. Not all of upstream would be
directly subscribed, some just check the mailing list when
Till Kamppeter, while reverting GIT commit 740922e downstream is technically
possible, it would be best to engage upstream for a wider audience input on
reversion or fix. Would you have the URL of the maintainer mailing list archive
when you e-mailed them, that was CC'ed to the regression
Can the removal of GIT commit 740922e be done in the kernel package for
Ubuntu Saucy?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1167301
Title:
8086:0166 [ThinkPad Twist S230u 3347]
Yes, I have found out already that in the mainline I have to check 3.8
as newest good and 3.8.1 as oldest bad kernel release. Currently I am
doing a doing a GIT bisect between these two. According to the estimates
by git bisect I am currently building for the third-last stage,
finishing in 20
Thanks for all the info, Till. Can you also test the latest 3.11 kernel
to confirm the bug happens there as well? If it does, we should send
you patch upstream for inclusion in Mainline and cc stable to have it
propagated to the stable trees.
[0]
Actually I see that you already tested 3.11 final, per comment #50.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1167301
Title:
8086:0166 [ThinkPad Twist S230u 3347] REGRESSION:
I think I have found the culprit:
till@till-twist:~/kernel/linux-stable$ git bisect good
Bisecting: 4 revisions left to test after this (roughly 2 steps)
[740922ee575f8ee4daa2bfd3db5f69dd7573fc76] drm: don't add inferred modes for
monitors that don't support them
Thanks for identifying the culprit, Til. Since the problem still exists
from 3.8.8 all the way through to current mainline (3.11), I think the
best course of action is for you to file a bug against DRM on
bugzilla.kernel.org, so that upstream can sort out how they want to
address it. We'll
Till, oops it's actually called DRI on bugzilla... Use these
selections:
Product:Drivers
Component: Video(DRI - non Intel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The final result of my bisect is actually what I guessed in the previous
comment (see output below). The patch (also below) is simple and one can
easily see that undoing it would solve the problem.
It seems that some monitors (including my monitor) report that they are
non-continuous frequency
Kamak, which product/component should I choose on bugzilla.kernel.org?
There is no DRM.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1167301
Title:
8086:0166 [ThinkPad Twist S230u
** Tags removed: performing-bisect
** Tags added: bisect-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1167301
Title:
8086:0166 [ThinkPad Twist S230u 3347] REGRESSION: Mirroring
Problem still persists with the new mainline kernel:
Linux till-twist 3.11.0-031100-generic #201309021735 SMP Mon Sep 2
21:36:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left
Till Kamppeter, the next step would be to bisect the kernel from 3.8.0-7
to 3.8.0-19 in order to identify the offending regression commit. Could
you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Tags removed: kernel-bug-exists-upstream-v3.11.0-031100
** Tags added:
The last good kernel was 3.8.0-8.17 and the first bad kernel was
3.8.0-9.18. The changelog between the two releases is rather small but I
do not really have an idea which change could be the culprit.
See
https://launchpad.net/ubuntu/+source/linux/3.8.0-9.18
I tried to bisect commits with git,
Till Kamppeter, as per
https://wiki.ubuntu.com/Kernel/KernelBisection#Why_did_the_folders_debian_and_debian.master_disappear.3F
one would want to switch to commit bisecting the mainline kernel as the
tags are linear.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You
Kernel regression - Invalid for xorg-server
** Tags added: needs-bisect
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** Changed in: xorg-server (Ubuntu)
Status: Triaged = Invalid
** Description changed:
- I have a Lenovo Thinkpad Twist with Core i7
Till Kamppeter, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue. Please do not test the
daily folder, but the one all the way at the bottom. Once you've tested
21 matches
Mail list logo