First try with sna+swapbufferswait+tearfree gave me this after a while

Xorg.log

[  1901.000] (EE) intel(0): sna_mode_redisplay: page flipping failed,
disabling CRTC:3 (pipe=0)
[  1901.365] (EE) intel(0): sna_mode_redisplay: page flipping failed,
disabling CRTC:5 (pipe=1)
[  1901.441] (EE) intel(0): Detected a hung GPU, disabling acceleration.
[  2841.578] (II) UnloadModule: "mouse"
[  2841.578] (II) UnloadModule: "kbd"
[  2841.579] (II) intel(0): switch to mode 1366x768@60.0 on pipe 0 using
LVDS1, position (0, 0), rotation normal
[  2841.632] (EE) intel(0): failed to set mode: Unknown error: -22
[  2841.632] (II) intel(0): switch to mode 1280x720@60.3 on pipe 1 using
VGA1, position (0, 0), rotation normal
[  2841.683] (EE) intel(0): failed to set mode: Unknown error: -22
[  2841.710] Server terminated successfully (0). Closing log file.

messages log

Sep 12 09:47:13 kernel:
Sep 12 09:47:13 kernel: error: [drm:pid1488:intel_pipe_set_base] *ERROR*
pin & fence failed
Sep 12 09:47:13 kernel: error: [drm:pid1488:drm_crtc_helper_set_config]
*ERROR* failed to set mode on [CRTC:3]
Sep 12 09:47:13 kernel: error: [drm:pid1488:intel_pipe_set_base] *ERROR*
pin & fence failed
Sep 12 09:47:13 kernel: error: [drm:pid1488:drm_crtc_helper_set_config]
*ERROR* failed to set mode on [CRTC:5]
Sep 12 09:47:14 syslogd: exiting on signal 15


Unfortunately I could not access the console after this so I could not get
the intel error state.

Now I'm trying another run without swapbufferswait and tearfree, only sna
enabled.

--
Johannes Lundberg


On Fri, Sep 12, 2014 at 9:29 AM, Lundberg, Johannes <
johan...@brilliantservice.co.jp> wrote:

> I have a feeling I tried that before but I will try it again and report
> back the results.
>
> I would also like to enable tear free by setting swapbufferswait and
> tearfree to true but when testing with glxgears I get very variable
> framerate and jerky animation. I don't know if this is a bug in glxgears or
> somewhere else... Any experience with this?
>
> --
> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD.
>
> On Fri, Sep 12, 2014 at 8:46 AM, Henry Hu <henry.hu...@gmail.com> wrote:
>
>>
>>
>> On Thu, Sep 11, 2014 at 7:18 PM, Lundberg, Johannes <
>> johan...@brilliantservice.co.jp> wrote:
>>
>>> I often get this on HD3000 when I push the GPU too hard.. (Well not
>>> really
>>> hard at all, but the harder I push it the sooner I get GPU crash). After
>>> the crash the desktop works fine but pure OpenGL apps don't (ie nothing
>>> shows up on the screen). I assume it has switched to software
>>> rendering(?)
>>>
>>> I'll try to get the error_state next time and post it.
>>>
>>> This is the only problem I have running FreeBSD on my Intel laptop and it
>>> is quite annoying when computer (GPU) crashes during demo for visitors
>>> and
>>> potential customers..
>>>
>>> Anyone have any clue on what the problem might be?
>>>
>>
>> If possible, have you tried the "SNA" acceleration method? Just add
>>     Option "AccelMethod" "sna"
>> to your device section of xorg.conf.
>>
>> I had GPU hung before, and after I switched to SNA, it never happened.
>>
>>
>>>
>>> On Thu, Sep 11, 2014 at 11:49 PM, Ranjan1018 . <21474...@gmail.com>
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > I have just upgrade my laptop, a Samsung Ativ Book 2 with an integrated
>>> > Intel HD Graphics 4000, to:
>>> >
>>> > FreeBSD ativ.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r271400: Wed
>>> Sep 10
>>> > 21:40:48 CEST 2014     root@ativ.local:/usr/obj/usr/src/sys/NEWCONS
>>> amd64
>>> >
>>> > Using Firefox, after some minutes, I receive the error:
>>> >
>>> > error: [drm:pid12:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
>>> > elapsed... GPU hung
>>> > info: [drm] capturing error event; look for more information in sysctl
>>> > hw.dri.0.info.i915_error_state
>>> >
>>> > This error is not related to r271400, but I first saw it few months
>>> ago in
>>> > current.
>>> >
>>> > The output of the command
>>> > sysctl hw.dri.0.info.i915_error_state
>>> > is:
>>> >
>>> >
>>> >
>>> https://drive.google.com/file/d/0BzoWQoMqq1sfa0tyVGJVYVBhRnc/edit?usp=sharing
>>> >
>>> > After the error I am not able to run mplayer for videos: the window is
>>> > black.
>>> >
>>> > Regards,
>>> > Maurizio
>>> > _______________________________________________
>>> > freebsd-current@freebsd.org mailing list
>>> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> > To unsubscribe, send any mail to "
>>> freebsd-current-unsubscr...@freebsd.org"
>>> >
>>>
>>> --
>>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>> 秘密保持について:この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
>>> もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
>>> 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
>>> ---
>>> CONFIDENTIALITY NOTE: The information in this email is confidential
>>> and intended solely for the addressee.
>>> Disclosure, copying, distribution or any other action of use of this
>>> email by person other than intended recipient, is prohibited.
>>> If you are not the intended recipient and have received this email in
>>> error, please destroy the original message.
>>> _______________________________________________
>>> freebsd-...@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
>>> To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"
>>>
>>
>>
>>
>> --
>> Cheers,
>> Henry
>>
>
>

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について:この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to