panning crash

panning crash

[Felix Miata]

Dell Optiplex GX280
P4 32 bit Hyperthreading enabled 0F34 2.8GHz CPU
00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)

/etc/X11/xinit/xinitrc.d/setup contains:
xrandr --fbmm 387x218 --fb 2560x1440 --output VGA1 --mode 1920x1440 --panning 2560x1440

Panning mouse out of initial CRTC desktop space into virtual desktop space and back in
some installations causes crash, in others not. Can someone here tell if this is a kernel,
server or other issue and not a driver issue from a look at Xorg.0.log? My suspicion is
kernel as primary if not sole.

Successes:
Rawhide, kernel 4.1.0-0.rc7, driver 2.99.917, server 1.17.1, KDE5
Mageia 5, kernel 3.19.8, driver 2.99.917, server 1.16.4, KDE4
openSUSE 13.1, kernel 3.12.39, driver 2.99.917, server 1.15.99.903, KDE3
openSUSE 13.2, kernel 3.16.7, driver 2.99.917, server 1.17.1, KDE3

Failures:
Fedora 21, kernel 4.0.4, driver 2.99.916, server 1.16.3, KDE4
Tumbleweed, kernel 4.0.4, driver 2.99.917, server 1.17.1, KDE3

Skipped testing due to unrelated issue (refuses mode 1920x1440 that xrandr claims
available, uses 1600x1200 instead, and no crashing):
Fedora 22, kernel 4.0.5, driver 2.99.917, server 1.17.1, KDE5

Logs:
http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/panfault/
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: panning crash

[Chris Wilson]

On Sat, Jun 13, 2015 at 02:17:34AM -0400, Felix Miata wrote:
> Dell Optiplex GX280
> P4 32 bit Hyperthreading enabled 0F34 2.8GHz CPU
> 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)
> 
> /etc/X11/xinit/xinitrc.d/setup contains:
> xrandr --fbmm 387x218 --fb 2560x1440 --output VGA1 --mode 1920x1440 --panning 2560x1440
> 
> Panning mouse out of initial CRTC desktop space into virtual desktop space and back in
> some installations causes crash, in others not. Can someone here tell if this is a kernel,
> server or other issue and not a driver issue from a look at Xorg.0.log? My suspicion is
> kernel as primary if not sole.

I think the crash is in the rejection handling code. If the kernel
rejects the modeset, we try again with via a shadow. The crash is very
unexpected. You can run the stacktraces though addr2line (e.g.
addr2line -i -e /usr/lib/xorg/modules/drivers/intel_drv.so 0x638f7
0x68fbc 0x6a02b) but also compiling your own ddx with
--enable-debug=full would be very useful. A drm.debug=6 dmesg would tell
you what is going on kernel side.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: panning crash

[Felix Miata]

Chris Wilson composed on 2015-06-13 09:19 (UTC+0100):

Thank you for responding!

> On Sat, Jun 13, 2015 at 02:17:34AM -0400, Felix Miata wrote:

>> Dell Optiplex GX280
>> P4 32 bit Hyperthreading enabled 0F34 2.8GHz CPU
>> 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)
 
>> /etc/X11/xinit/xinitrc.d/setup contains:
>> xrandr --fbmm 387x218 --fb 2560x1440 --output VGA1 --mode 1920x1440 --panning 2560x1440
 
>> Panning mouse out of initial CRTC desktop space into virtual desktop space and back in
>> some installations causes crash, in others not. Can someone here tell if this is a kernel,
>> server or other issue and not a driver issue from a look at Xorg.0.log? My suspicion is
>> kernel as primary if not sole.

> I think the crash is in the rejection handling code. If the kernel
> rejects the modeset, we try again with via a shadow. The crash is very
> unexpected. You can run the stacktraces though addr2line (e.g.
> addr2line -i -e /usr/lib/xorg/modules/drivers/intel_drv.so 0x638f7
> 0x68fbc 0x6a02b)

Brief googling this didn't find anything I can grok. It's probably doable with
minimal hand-holding, e.g. a URL explaining what tools need to be installed
(gdb + ???) and how to use them. Debugging is something I do so infrequently I
forget everything I managed to slog through from one session to the next.

> but also compiling your own ddx with
> --enable-debug=full would be very useful.

Not doable. I tried programming in college over 4 decades ago. English remains
as much language as I can cope with, and not even that much WRT OBS. OTOH, RPMs
I can deal with.

> A drm.debug=6 dmesg would tell you what is going on kernel side.

Tell you maybe. :-)

http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/panfault/

Fedora 21, kernel 4.0.4:
dmsg-i915G-f21-k404crash.txt

Tumbleweed, kernel 4.0.4:
dmsg-i915G-os133-k404crash.txt

Looks like maybe the crash occurred in the vicinity of [433.26] in F21,
[111.57] in TW, but there's minimal sense I can make of dmesg generally.

All this said, crash didn't happen in Rawhide, so maybe it's a kernel
problem that has resolved itself post-4.0.4?

HTH
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx