On 2012.12.23 at 10:09 +, Andy Furniss wrote:
> Markus Trippelsdorf wrote:
>
> >> Does booting with radeon.wb=0 fix the issue? Please make sure your
> >> kernel has this patch:
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=86a1881d08f65a42c17071a59c0088dbe28
Markus Trippelsdorf wrote:
>> Does booting with radeon.wb=0 fix the issue? Please make sure your
>> kernel has this patch:
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=86a1881d08f65a42c17071a59c0088dbe2870246
>
> My kernel has this patch and radeon.wb=0 doesn't h
On 2012.12.22 at 20:46 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf
> wrote:
> > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> >> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> >> wrote:
> >> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>
Markus Trippelsdorf wrote:
Does booting with radeon.wb=0 fix the issue? Please make sure your
kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=86a1881d08f65a42c17071a59c0088dbe2870246
My kernel has this patch and radeon.wb=0 doesn't help.
I
On 2012.12.23 at 10:09 +, Andy Furniss wrote:
> Markus Trippelsdorf wrote:
>
> >> Does booting with radeon.wb=0 fix the issue? Please make sure your
> >> kernel has this patch:
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=86a1881d08f65a42c17071a59c0088dbe28
On 2012.12.22 at 20:46 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf
> wrote:
> > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> >> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> >> wrote:
> >> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>
On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf
wrote:
> On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
>> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
>> wrote:
>> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>> >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
>> >>
On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf
wrote:
> On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
>> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
>> wrote:
>> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>> >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
>> >>
Op 19-12-12 15:20, Markus Trippelsdorf schreef:
> On 2012.12.19 at 14:57 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 17:12, Markus Trippelsdorf schreef:
>>> With your supposed debugging BUG_ONs added I still get:
>>>
>>> Dec 18 17:01:15 x4 kernel: [ cut here ]
>>> Dec 18
On 2012.12.19 at 14:57 +0100, Maarten Lankhorst wrote:
> Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> > With your supposed debugging BUG_ONs added I still get:
> >
> > Dec 18 17:01:15 x4 kernel: [ cut here ]
> > Dec 18 17:01:15 x4 kernel: WARNING: at include/linux/kref.
Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
>>> On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17
Op 19-12-12 15:20, Markus Trippelsdorf schreef:
> On 2012.12.19 at 14:57 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 17:12, Markus Trippelsdorf schreef:
>>> With your supposed debugging BUG_ONs added I still get:
>>>
>>> Dec 18 17:01:15 x4 kernel: [ cut here ]
>>> Dec 18
On 2012.12.19 at 14:57 +0100, Maarten Lankhorst wrote:
> Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> > With your supposed debugging BUG_ONs added I still get:
> >
> > Dec 18 17:01:15 x4 kernel: [ cut here ]
> > Dec 18 17:01:15 x4 kernel: WARNING: at include/linux/kref.
Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
>>> On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17
Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
>>> On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17
On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
> > On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
> >> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> >>> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> O
Op 18-12-12 14:38, Markus Trippelsdorf schreef:
> On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
>> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
>>> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> On Mon, De
On 2012.12.18 at 14:38 +0100, Markus Trippelsdorf wrote:
> On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
> > On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> > > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
>
On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote:
> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > >
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > > wrote:
> > > > On 2012.12.17 at 16:32 -0500, Alex Deucher
Op 18-12-12 17:12, Markus Trippelsdorf schreef:
> On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
>> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
>>> On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17
On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote:
> Op 18-12-12 14:38, Markus Trippelsdorf schreef:
> > On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
> >> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> >>> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> O
Op 18-12-12 14:38, Markus Trippelsdorf schreef:
> On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
>> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
>>> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> On Mon, De
On 2012.12.18 at 14:38 +0100, Markus Trippelsdorf wrote:
> On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
> > On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> > > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
>
On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote:
> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > >
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > > wrote:
> > > > On 2012.12.17 at 16:32 -0500, Alex Deucher
On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > wrote:
> > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> > >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> > >
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> wrote:
> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> >> wrote:
> >> > As soon as I open the following website:
> >> > http
On 2012.12.17 at 22:48 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> > wrote:
> > > As soon as I open the following website:
> > > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_
On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> wrote:
> > As soon as I open the following website:
> > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
> >
> > my Radeon RS780 stalls (GPU lockup) leaving the mach
As soon as I open the following website:
http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
my Radeon RS780 stalls (GPU lockup) leaving the machine unusable:
Dec 17 17:41:39 x4 kernel: [drm] Initialized drm 1.1.0 20060810
Dec 17 17:41:39 x4 kernel: [drm] radeon defaulting
On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
wrote:
> On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
>> wrote:
>> > As soon as I open the following website:
>> > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_
On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
wrote:
> As soon as I open the following website:
> http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
>
> my Radeon RS780 stalls (GPU lockup) leaving the machine unusable:
Is this a regression? Most likely a 3D driver
On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > wrote:
> > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> > >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> > >
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> wrote:
> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> >> wrote:
> >> > As soon as I open the following website:
> >> > http
On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
wrote:
> On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
>> wrote:
>> > As soon as I open the following website:
>> > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_
On 2012.12.17 at 22:48 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> > wrote:
> > > As soon as I open the following website:
> > > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_
On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> wrote:
> > As soon as I open the following website:
> > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
> >
> > my Radeon RS780 stalls (GPU lockup) leaving the mach
On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
wrote:
> As soon as I open the following website:
> http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
>
> my Radeon RS780 stalls (GPU lockup) leaving the machine unusable:
Is this a regression? Most likely a 3D driver
As soon as I open the following website:
http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
my Radeon RS780 stalls (GPU lockup) leaving the machine unusable:
Dec 17 17:41:39 x4 kernel: [drm] Initialized drm 1.1.0 20060810
Dec 17 17:41:39 x4 kernel: [drm] radeon defaulting
40 matches
Mail list logo