Displaying 7 results from an estimated 7 matches for "00cf26c0".
2017 Jul 14
3
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
...er get lost in that link magic :/
>
> +1
>
> drm.ko
> 20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
> CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
> vmlinux
> 15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
> CONTENTS, ALLOC, LOAD, READONLY, DATA
>
> Danged if I know... um um RELOC business mucks things up?
Argh, it shouldn't be READONLY for vmlinux either, but apparently that
is working for mysterious reasons.
Some architectures were in fact complaining that I...
2017 Jul 14
0
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
...ding up in RO memory?
>
> I forever get lost in that link magic :/
+1
drm.ko
20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
vmlinux
15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
Danged if I know... um um RELOC business mucks things up?
-Mike
2017 Jul 17
0
suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
...:/
>>
>> +1
>>
>> drm.ko
>> 20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
>> CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
>> vmlinux
>> 15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
>> CONTENTS, ALLOC, LOAD, READONLY, DATA
>>
>> Danged if I know... um um RELOC business mucks things up?
>
>Argh, it shouldn't be READONLY for vmlinux either, but apparently that
>is working for mysterious reasons.
If I'm not mistaken, thi...
2017 Jul 14
0
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
...t;
> > > drm.ko
> > > 20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
> > > CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
> > > vmlinux
> > > 15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
> > > CONTENTS, ALLOC, LOAD, READONLY, DATA
> > >
> > > Danged if I know... um um RELOC business mucks things up?
> >
> > Argh, it shouldn't be READONLY for vmlinux either, but apparently that
> > is working for mysterious r...
2017 Jul 14
1
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
On Fri, Jul 14, 2017 at 03:36:08PM +0200, Mike Galbraith wrote:
> Ok, a network outage gave me time to go hunting. Indeed it is a bad
> interaction with the tree DRM merged into. All DRM did was to slip a
> WARN_ON_ONCE() that nouveau triggers into a kernel module where such
> things no longer warn, they blow the box out of the water. I made a
> dinky testcase module (attached),
2017 Jul 14
1
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
...gt;
> > +1
> >
> > drm.ko
> > 20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
> > CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
> > vmlinux
> > 15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
> > CONTENTS, ALLOC, LOAD, READONLY, DATA
> >
> > Danged if I know... um um RELOC business mucks things up?
>
> Argh, it shouldn't be READONLY for vmlinux either, but apparently that
> is working for mysterious reasons.
>
> Some archit...
2017 Jul 14
4
[regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
On Wed, 2017-07-12 at 07:37 -0400, Ilia Mirkin wrote:
> On Wed, Jul 12, 2017 at 7:25 AM, Mike Galbraith <efault at gmx.de> wrote:
> > On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote:
> >> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote:
> >> >
> >> > Some display stuff did change for 4.13 for GM20x+ boards. If it's not
> >>