[Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34

2010-12-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=28402 Alex Deucher changed: What|Removed |Added CC||anton.b...@gmail.com --- Comment #98 from

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Keith Packard
On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler wrote: > On Fri, 26 Nov 2010 10:45:59 -0800 > Keith Packard wrote: > > > In order to correctly report monitor connected status changes, the > > previous monitor status must be recorded in the connector->status > > value instead of being discarde

Re: [PATCH 09/10] MCDE: Add build files and bus

2010-12-05 Thread Daniel Vetter
On Sat, Dec 04, 2010 at 04:34:22PM -0500, Alex Deucher wrote: > This doesn't seem that different from the graphics chips we support > with kms. I don't think it would require much work to use KMS. One > thing we considered, but never ended up implementing was a generic > overlay API for KMS. Mos

Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Florian Mickler
On Fri, 26 Nov 2010 10:45:59 -0800 Keith Packard wrote: > In order to correctly report monitor connected status changes, the > previous monitor status must be recorded in the connector->status > value instead of being discarded. > > Signed-off-by: Keith Packard Keith, am I right to assume that

[Bug 24382] New: 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Summary: 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream Product: Drivers Version: 2.5 Kernel Version: 2.6.37-rc4 Platform: All

[Bug 24382] 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Maciej Rutecki changed: What|Removed |Added Blocks||21782 -- Configure bugmail: https:/

[Bug 24382] 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #1 f

[Bug 23222] 2.6.36 radeon KMS: [drm] Cannot find any crtc or sizes

2010-12-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=23222 Rafael J. Wysocki changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALRE

2.6.37-rc4-git4: Reported regressions 2.6.35 -> 2.6.36

2010-12-05 Thread Rafael J. Wysocki
This message contains a list of some post-2.6.35 regressions introduced before 2.6.36, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved post-2.6.35 regressions, please let us kno

Re: 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread Alex Deucher
On Sat, Dec 4, 2010 at 8:16 AM, jurriaan wrote: > on my up-to-date Debian Unstable system, running on an Phenom X4, on > an ATI RS880/SB700/built-in Radeon HD 4200 system, kdm crashes > consistently when trying to start X.org when running kernel 2.6.37-rc4. > It doesn't when running 2.6.36. > > Wh

[Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34

2010-12-05 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=28402 Alex Deucher changed: What|Removed |Added CC||anton.bugs at gmail.com --- Comment #98 f

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Keith Packard
vailable URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20101205/7120c79d/attachment.pgp>

[Bug 24382] New: 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Summary: 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream Product: Drivers Version: 2.5 Kernel Version: 2.6.37-rc4 Platform: All

[PATCH 09/10] MCDE: Add build files and bus

2010-12-05 Thread Daniel Vetter
On Sat, Dec 04, 2010 at 04:34:22PM -0500, Alex Deucher wrote: > This doesn't seem that different from the graphics chips we support > with kms. I don't think it would require much work to use KMS. One > thing we considered, but never ended up implementing was a generic > overlay API for KMS. Mos

[Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute

2010-12-05 Thread Florian Mickler
On Fri, 26 Nov 2010 10:45:59 -0800 Keith Packard wrote: > In order to correctly report monitor connected status changes, the > previous monitor status must be recorded in the connector->status > value instead of being discarded. > > Signed-off-by: Keith Packard Keith, am I right to assume that

[Bug 24382] 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Maciej Rutecki changed: What|Removed |Added Blocks||21782 -- Configure bugmail: https:/

[Bug 24382] 2.6.37-rc4: kdm crashes consistently, 2.6.36 not affected, drm:radeon_cs_ioctl Invalid command stream

2010-12-05 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=24382 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #

[Bug 23222] 2.6.36 radeon KMS: [drm] Cannot find any crtc or sizes

2010-12-05 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=23222 Rafael J. Wysocki changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALRE

2.6.37-rc4-git4: Reported regressions 2.6.35 -> 2.6.36

2010-12-05 Thread Rafael J. Wysocki
This message contains a list of some post-2.6.35 regressions introduced before 2.6.36, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved post-2.6.35 regressions, please let us kno