Commit 63e28a7a5ffce59b645ca9cbcc01e1e8be56bd75, "uvesafb: Clean up
MTRR code" contains the following change:
@@ -1930,6 +1891,9 @@ static int uvesafb_setup(char *options)
}
}
+if (mtrr != 3 && mtrr != 1)
+pr_warn("uvesafb: mtrr should be set to 0 or 3; %d is
Commit 63e28a7a5ffce59b645ca9cbcc01e1e8be56bd75, uvesafb: Clean up
MTRR code contains the following change:
@@ -1930,6 +1891,9 @@ static int uvesafb_setup(char *options)
}
}
+if (mtrr != 3 mtrr != 1)
+pr_warn(uvesafb: mtrr should be set to 0 or 3; %d is
unsupported,
On Wed, Feb 22, 2012 at 8:56 PM, Dave Airlie wrote:
> Eugeni Dodonov (4):
> ? ? ?drm/i915: gen7: implement rczunit workaround
> ? ? ?drm/i915: gen7: Implement an L3 caching workaround.
> ? ? ?drm/i915: gen7: work around a system hang on IVB
> ? ? ?drm/i915: do not enable RC6p on Sandy Bridge
On Wed, Feb 22, 2012 at 8:56 PM, Dave Airlie airl...@linux.ie wrote:
Eugeni Dodonov (4):
drm/i915: gen7: implement rczunit workaround
drm/i915: gen7: Implement an L3 caching workaround.
drm/i915: gen7: work around a system hang on IVB
drm/i915: do not enable RC6p on Sandy
On Tue, Jan 24, 2012 at 8:34 AM, Torsten Kaiser
wrote:
> On Mon, Jan 23, 2012 at 7:01 PM, Torsten Kaiser
> wrote:
>> On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse wrote:
>>> On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
>>>> After updating to
On Tue, Jan 24, 2012 at 8:34 AM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
On Mon, Jan 23, 2012 at 7:01 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse j.gli...@gmail.com wrote:
On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten
On Mon, Jan 23, 2012 at 7:01 PM, Torsten Kaiser
wrote:
> On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse wrote:
>> On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
>>> After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
>>> I left m
On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse wrote:
> On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
>> After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
>> I left my KDE desktop running until the screensaver turned off the
>> monitor
On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse j.gli...@gmail.com wrote:
On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
I left my KDE desktop running until the screensaver turned off the
monitors
On Mon, Jan 23, 2012 at 7:01 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse j.gli...@gmail.com wrote:
On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
I
After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
I left my KDE desktop running until the screensaver turned off the
monitors. But on key presses it would not turn back on. Ctrl+Alt+F1 to
switch to another virtual console also did not work.
Alt+SysRq magic still worked, so I
After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
I left my KDE desktop running until the screensaver turned off the
monitors. But on key presses it would not turn back on. Ctrl+Alt+F1 to
switch to another virtual console also did not work.
Alt+SysRq magic still worked, so I
On Fri, Jul 23, 2010 at 1:42 PM, Rafael J. Wysocki wrote:
> Bug-Entry ? ? ? : http://bugzilla.kernel.org/show_bug.cgi?id=16372
> Subject ? ? ? ? : Regression 2.6.34->2.6.35-rc4: radeaon KMS an RS690 broken
> Submitter ? ? ? : Torsten Kaiser
> Date ? ? ? ? ? ?: 2010-07-11 19:
On Fri, Jul 23, 2010 at 1:42 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16372
Subject : Regression 2.6.34-2.6.35-rc4: radeaon KMS an RS690 broken
Submitter : Torsten Kaiser just.for.l...@googlemail.com
Date
On Thu, Jul 15, 2010 at 12:16 AM, Alex Deucher wrote:
> I discussed this with Jerome and I think we found the root cause.
> Does this patch help?
(patch 0001-drm-radeon-kms-fix-gtt-MC-base-alignment-on-rs4xx-rs.patch)
Yes:
[0.426978] Linux agpgart interface v0.103
[0.427141] [drm]
On Wed, Jul 14, 2010 at 9:30 PM, Jerome Glisse
wrote:
> On 07/14/2010 02:51 PM, Torsten Kaiser wrote:
>>
>> On Tue, Jul 13, 2010 at 9:10 PM, Alex Deucher
>> ?wrote:
>>>
>>> On Tue, Jul 13, 2010 at 2:29 PM, Torsten Kaiser
>>&g
On Tue, Jul 13, 2010 at 9:10 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Tue, Jul 13, 2010 at 2:29 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
But the CP is still broken:
Is this a regression? If so, can you bisect it?
Alex
I bisected it to this commit
On Wed, Jul 14, 2010 at 9:30 PM, Jerome Glisse gli...@freedesktop.org wrote:
On 07/14/2010 02:51 PM, Torsten Kaiser wrote:
On Tue, Jul 13, 2010 at 9:10 PM, Alex Deucheralexdeuc...@gmail.com
wrote:
On Tue, Jul 13, 2010 at 2:29 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote
On Thu, Jul 15, 2010 at 12:16 AM, Alex Deucher alexdeuc...@gmail.com wrote:
I discussed this with Jerome and I think we found the root cause.
Does this patch help?
(patch 0001-drm-radeon-kms-fix-gtt-MC-base-alignment-on-rs4xx-rs.patch)
Yes:
[0.426978] Linux agpgart interface v0.103
[
On Tue, Jul 13, 2010 at 9:10 PM, Alex Deucher wrote:
> On Tue, Jul 13, 2010 at 2:29 PM, Torsten Kaiser
> wrote:
>> On Mon, Jul 12, 2010 at 11:38 PM, Alex Deucher
>> wrote:
>>> On Mon, Jul 12, 2010 at 3:54 PM, Torsten Kaiser
>>> wrote:
>>>> 0888e
On Mon, Jul 12, 2010 at 11:38 PM, Alex Deucher wrote:
> On Mon, Jul 12, 2010 at 3:54 PM, Torsten Kaiser
> wrote:
>> 0888e883ea5ff8fac27e813256d6c1eaede5a234 is the first bad commit
>> commit 0888e883ea5ff8fac27e813256d6c1eaede5a234
>> Author: Alex Deucher
>> Da
On Mon, Jul 12, 2010 at 11:38 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Mon, Jul 12, 2010 at 3:54 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
0888e883ea5ff8fac27e813256d6c1eaede5a234 is the first bad commit
commit 0888e883ea5ff8fac27e813256d6c1eaede5a234
Author: Alex Deucher
On Tue, Jul 13, 2010 at 9:10 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Tue, Jul 13, 2010 at 2:29 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
On Mon, Jul 12, 2010 at 11:38 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Mon, Jul 12, 2010 at 3:54 PM, Torsten Kaiser
just.for.l
On Mon, Jul 12, 2010 at 5:23 PM, Alex Deucher wrote:
> On Sun, Jul 11, 2010 at 3:56 PM, Torsten Kaiser
> wrote:
>> I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
>> that this kernel will only boot with radeon.modeset=0.
>>
>> If KMS i
On Mon, Jul 12, 2010 at 5:23 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Sun, Jul 11, 2010 at 3:56 PM, Torsten Kaiser
just.for.l...@googlemail.com wrote:
I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
that this kernel will only boot with radeon.modeset=0.
If KMS
I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
that this kernel will only boot with radeon.modeset=0.
If KMS is active the display turns off and the system is completely
dead, not even SysRq+B is working.
I build a new kernel with the radeon driver as a module and
I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
that this kernel will only boot with radeon.modeset=0.
If KMS is active the display turns off and the system is completely
dead, not even SysRq+B is working.
I build a new kernel with the radeon driver as a module and
27 matches
Mail list logo
