No feedback, closing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To manage notifications about this bug go to:
** Changed in: xserver-xorg-video-intel
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst
Waiting for feedback in order to change the status.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To manage
*** Bug 87163 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To
(In reply to Andy Furniss from comment #17)
(In reply to Andy Furniss from comment #16)
(In reply to Andy Furniss from comment #15)
I only recently started seeing locks - turns out that dri3 was OK for me,
but of course it then got disabled by default and I started getting locks.
(In reply to Andy Furniss from comment #16)
(In reply to Andy Furniss from comment #15)
I only recently started seeing locks - turns out that dri3 was OK for me,
but of course it then got disabled by default and I started getting locks.
It seems I was a bit hasty in calling dri3 OK - I
*** Bug 87163 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To
(In reply to Chris Wilson from comment #13)
Implemented the bspec recommendation:
commit d247cb7d0cdb73736f31612157e47f166af68ba0
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Dec 8 10:07:25 2014 +
sna/gen6: Poke PSMI control around WAIT_FOR_EVENT to prevent idling
(In reply to Andy Furniss from comment #15)
I only recently started seeing locks - turns out that dri3 was OK for me,
but of course it then got disabled by default and I started getting locks.
It seems I was a bit hasty in calling dri3 OK - I can lock if I try long
enough, just that it takes
Implemented the bspec recommendation:
commit d247cb7d0cdb73736f31612157e47f166af68ba0
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Dec 8 10:07:25 2014 +
sna/gen6: Poke PSMI control around WAIT_FOR_EVENT to prevent idling
The bspec recommends preventing the hardware
I just saw today that there is a recommendation to toggle PMSI_CTL
around WAIT_FOR_EVENT in the SNB bspec. That is probably worth trying...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Hm, another option might be to switch to timeout mode on SNB. With a
long enough timeout, we could apply the emit a primitive workaround
everytime we come out of rc6 and hopefully make things more stable...
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Could you please retest with latest drm-intel-nightly?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To manage
Leon Winter, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
Timeout.
Michael, are you stills seeing the issue with later kernels? There seems
to have been some back and forth with the patch referenced by Chris in
comment #6 - please try 3.13-rc1 or later.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Nothing has changed. SNB can still randomly hard lock with rc6 and
vsync.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using
*** Bug 67856 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To
I applied (apt-get source, patch -p1, dpkg-buildpackage -b, dpkg -i) the
patch against the current ubuntu stock kernel (3.8.0-25-generic) but to
no avail, a mplayer with xv will instantly result in the lockup state.
Due to that I have configured my mplayer to use the gl backend which is
running
Can you please try with this patch:
https://patchwork.kernel.org/patch/2707341/ as it claims to fix some
instability with rc6 on SandyBridge?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
@Chris,
What makes you say the hardware is different? Both machines use the same intel
video driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb]
@Mark, you have a gen3 device which has no known issues with Xv, this
bug report is about a gen6 device which still has instability when using
rc6 (new hardware feature on gen6).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Understood, the Atom N455 is different. What about the macbook i5?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To
Could be gen5, gen6 or gen7 depending upon the model.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
[snb] random hard lockup whilst using Xv
To manage
@Mark please file a separate bug as your hardware is completely
different and cannot suffer the same root cause as this bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Regarding the backends, I used gl/x11 for the last few days and did not
encounter the lockup. While at the same time, the machine will lockup instantly
(after 5secs) when using -vo xv. Sorry, that this does not confirm your
suspicion but maybe my gl backend does not trigger the code path you
Regarding my last entry, fortunately my system now recovered from the
behaviour of not detecting external monitors.
Concerning the hangup issue I want to add that HTML5/Flash videos also does not
seem to trigger the hangup, however I am not aware of the subsystem used for
this video playback
Another thing to test would be whether i915.i915_enable_rc6=0 makes any
difference.
** Summary changed:
- Random Xorg freezes occuring hours after login
+ [snb] random hard lockup whilst using Xv
** Bug watch added: freedesktop.org Bugzilla #62373
Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=62373.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
I have also experienced this bug on 2 different machines running 13.04.
The first is an eeepc with an Atom 1.66GHz N455 CPU, and the second is a
macbook pro 8,1 with a Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz.
The bug is most reproduceable when playing videos, but on rare occasions
(3) it has
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Out of the backend I tried (xv, gl_nosw, x11, sdl/x11, gl, gl2) xv seems
to be causing the problem. I am currently using the backend x11 and have
yet to observe a crash using it. However during my tesing cauing the
crash was not as reliable as in real-world usage before but at the time
of the
Can you try the gl backend in real world usage? I expect it to fail as
well, as I think the failure mode here is the machine dying whilst
waiting up a scanline - and both the Xv and gl backends should trigger
that code. (Except in the case of fullscreen gl, which will go through
another path).
For some other reason I switched my window manager to dwm and can now
almost reliably reproduce the failure by simply starting a video in
mplayer and wait for approx. 5 seconds. Before with gnome/metacity I
could sometimes watch entire movies of multiple hours. Sometimes it
would crash in between
How are you playing the video? If you are using mplayer, can you try the
various backends to see if any are more susceptible?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Hmm, suggests that the fresh data never reached disk before the system
hang. Maybe try 'while :; do sleep 1; cat ... error_state; sync;
done'
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
The symptoms are consistent with a GPU hang, so please try to grab the
/sys/kernel/debug/dri/0/i915_error_state after the event (and before
rebooting).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Since the affected maschine is not reachable via SSH, I just dumped the
error state every second (while [ 1 ]; sleep 1; do cat
/sys/kernel/debug/dri/0/i915_error_state error_state; done) and
deleted all the no error state lines from the file before the actual
error dump after the crash. As it
The bug can occur as early as 1 minute after boot up. I tried watching a video
in mplayer. Several times the system locked up which I handled with a hard
reset. Once I just started mplayer, skipped to the correct position in the
video and could only watch 5 seconds more as the system froze
I continue to experience this bug several times a day. The bug can occur
as early as 20 minutes after boot, but may also not occur during several
hours of usage. I do not see anything suspicious in the log files
though. It might be a coincidence but it may especially occur when using
mplayer.
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1176647
Title:
Public bug reported:
When using the system for some time, at some point display freezes. The system
seems to continue working as mplayer remains streaming internet radio and also
the audio output works properly. During this lock-up the mouse can be moved but
any click is ignored. Furthermore
42 matches
Mail list logo
