http://bugzilla.kernel.org/show_bug.cgi?id=7767
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-05-16 00:39 ---
DRM still broken in 2.6.21.1. Building drm.ko and savage.ko from the
freedesktop.org development tree works again after some recent breakage, and
the resulting modules
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-04-10 03:09 ---
Issue still open for kernel 2.6.21-rc6-git1. Anything I can do here?
--- You are receiving this mail because: ---
You are the assignee for the bug, or are
On Wed, 2007-02-28 at 10:55 +0100, Michel Dänzer wrote:
On Sun, 2007-02-25 at 19:35 +, Alan Hourihane wrote:
I know what the problem is here. And bugzilla #5714 will cure it. So I'm
getting inclined to pull the frontbuffer-removal branch into master and
fix up the drivers on the fly.
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-03-09 12:53 ---
Reply-To: [EMAIL PROTECTED]
I know what the problem is here. And bugzilla #5714 will cure it. So I'm
getting inclined to pull the frontbuffer-removal branch into
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-03-02 11:08 ---
Created an attachment (id=10584)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10584action=view)
Output of dmesg for 2.6.20-1.2953.fc7 [2.6.21rc1] git kernel tree
On Sun, 2007-02-25 at 19:35 +, Alan Hourihane wrote:
I know what the problem is here. And bugzilla #5714 will cure it. So I'm
getting inclined to pull the frontbuffer-removal branch into master and
fix up the drivers on the fly.
How does this sound to others.
At FOSDEM, I chatted about
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-28 12:19 ---
Reply to comment #25:
In the meantime, I have reverted my system from FC rawhide to FC6, and so I
have pulled in your DRM tree from kernel.org into the
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-28 12:29 ---
Created an attachment (id=10558)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10558action=view)
Output of dmesg for 2.6.19-1.2911.6.3.fc6 [2.6.19.5rc1] git kernel
I know what the problem is here. And bugzilla #5714 will cure it. So I'm
getting inclined to pull the frontbuffer-removal branch into master and
fix up the drivers on the fly.
How does this sound to others.
Alan.
On Sat, 2007-02-24 at 15:00 -0800, [EMAIL PROTECTED]
wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-25 11:35 ---
Reply-To: [EMAIL PROTECTED]
I know what the problem is here. And bugzilla #5714 will cure it. So I'm
getting inclined to pull the frontbuffer-removal branch into
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-24 04:25 ---
I do not see any difference between the savage source files [savage_bci.c,
savage_drm.h, savage_drv.c, savage_drv.h, savage_state.c] from kernel
2.6.20-1.2940.fc7
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-24 15:00 ---
did you test it though?
As I said further up this bug, there are no functional difference between the
savage in the drm tree and the one in the kernel tree, they are
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-17 22:20 ---
Okay I've added some changes to the drm-2.6 git tree to see if they fix this
problem..
Can you test the next -mm kernel when Andrew releases it or grab the tree from
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-09 01:21 ---
Created an attachment (id=10364)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10364action=view)
Output of dmesg for 2.6.20-1.2922.fc7 git kernel DRM modules with
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-08 02:41 ---
In reply to comment #17:
After disabling AIGLX and extension Composite altogether, entries:
(**) Option AIGLX off
(**) Extension Composite is disabled
appear in
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-08 02:46 ---
please send the drm logs from the failure with glxinfo, please note you only add
debug=1 to the drm module not the savage module, which is why it broke in the
other
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-08 05:15 ---
Created an attachment (id=10342)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10342action=view)
Output of dmesg for 2.6.20-1.2922.fc7 stock kernel DRM modules with
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-08 14:39 ---
Okay can you try the git modules with debugging again and log that?
I'm not really sure what could be causing this,
make sure you rmmod the kernel drm and savage ones
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-05 20:51 ---
Joachim had you try disable AIGLX ?
Section ServerFlags
Option AIGLX off
EndSection
Section Extensions
Option Composite Disable
EndSection
--- You are
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-04 02:13 ---
Created an attachment (id=10277)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10277action=view)
Output of dmesg for 2.6.19-1.2917.fc7 stock kernel DRM modules with
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-04 02:14 ---
Created an attachment (id=10278)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10278action=view)
Output of dmesg for 2.6.19-1.2917.fc7 git kernel DRM modules with
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-04 02:48 ---
Attachment http://bugzilla.kernel.org/attachment.cgi?id=10278action=view turns
out to be not useful as turning on the debug flag inhibits direct rendering
completely:
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 03:16 ---
I cannot confirm the claim of comment #3. By merely looking at the handful of
savage related source files, it becomes clear that there actually -are-
differences
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 13:06 ---
I think it is a change elsewhere in the drm that is affecting your system, just
comparing the files isn't valid around the savage in this case as the out of the
kernel
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 13:49 ---
Ok, I never claimed anything different. However, I do continue to insist, that
albeit 2.6.20rc7 being a recent kernel, it is not up to date regarding the
git
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 13:54 ---
Okay I looked at the logs, you do have hardware rendering, dri works fine it is
in fact AIGLX that is broken, that is indeed strange, there must be something in
the drm
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 14:10 ---
And that is true at all stages, the git tree is a development tree, it isn't
always suitable for inclusion in the upstream kernel... you can check if an -mm
kernel
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 14:56 ---
can you load the drm modules in both cases with debug=1 option and attach those
logs...
the drm buffer stuff is quite different between both trees at the moment due to
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 20:41 ---
Created an attachment (id=10276)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10276action=view)
/var/log/Xorg.0.log
Hi, I tried to disable AIGLX
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-03 22:25 ---
please don't attached other problems to this bug... that isn't the same problem
you are seeing, you have i915 reporter has a savage...
--- You are receiving this
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-02 08:29 ---
Created an attachment (id=10258)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10258action=view)
Xorg.0.log for FC kernel 2.6.19-1.2917.fc7 [2.6.20rc7]
The kernel
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-02 08:39 ---
Created an attachment (id=10259)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10259action=view)
Xorg.0.log for FC kernel 2.6.19-1.2917.fc7 [2.6.20rc7] using DRM
http://bugzilla.kernel.org/show_bug.cgi?id=7767
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED],
|
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-01-31 14:42 ---
it should all be synced up for ages, I've no outstanding differences between the
2.6.20 savage and drm git tree that I can see with a quick look.
Can you send me a
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-01-04 00:27 ---
Sorry, the correct link is [git://anongit.freedesktop.org/git/mesa/drm].
--- You are receiving this mail because: ---
You are the assignee for the bug, or are
36 matches
Mail list logo
