Public bug reported:
Xorg crashes for a few seconds and screen turns black during normal
desktop activity, running on Radeonsi drivers.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
Uname: Linux 3.16.0-23-generic
Tested Trusty and Kernel 3.13-rc8. The issue is still there.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-v3.13-rc8
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.lau
@Christopher: I will retest the latest Kernels within the next few days.
@Jon: I propose to keep an eye on the upstream bug-report, which I linked here
in the past (https://bugzilla.kernel.org/show_bug.cgi?id=8740). Even though it
was removed from this bug tracker, it's still open in the Kernel'
If you have these problems running Dota 2, you should try Mesa Git or wait for
Mesa 10. It contains several patches to remove lockups.
For me on Dota 2 the lockups are completely gone, probably they're also gone in
other applications.
--
You received this bug notification because you are a mem
@popey:
I tested kernel 3.12.0-031200rc7-generic with Mesa 9.2.2 and xf86-video-
intel-2.99.905 running Dota 2 which, is a useful test case to produce
hangs and I can assure that there are still plenty lockups. Only the
output differs now:
[ 2937.818867] [drm:i915_set_reset_status] *ERROR* render
@thomas303: Since 12.04.3 uses the video stack and kernel of Raring it's no
wonder that it's also affected.
If you didn't have the errors before 12.04.3 you can still revert to the video
stack / kernel of 12.04.2 (Quantal) or 12.04 (Precise).
--
You received this bug notification because you a
Correct me if I am wrong, but if it's an Intel DRI bug (and thats what
it is), wouldn't it mean that "xserver-xorg-video-intel" is the "real
affected" package ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
(In reply to comment #113)
> On snb the blorp engine in mesa has become a bit more hang-happy, see bug
> #70151
> Not all gpu hangs are created equal ;-)
>
Actually it was on Sandybridge.
> You mean a gpu hang happens while when doing a vt switch?
No I meant, if you suffer a lockup you just hav
Just a few remarks.
I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904.
Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups
highly increased (especially in games).
Additionally with running the latest drivers complete system lockups are gone,
but it's still
@Gero: Tried the performance govenor using Kernel 3.8.0-30-generic. It
did not fix the issue, the touchpad still lost sync.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/89
@ Christopher: sorry, I mixed up the release name. I meant 11.10 Oneiric
and not Lucid. As I already stated, all releases < 11.04 won't work
because Sandybridge Support was added after the 10.10 release. If you
want I can test 11.04 if it helps somehow.
Nevertheless I believe that my upstream bug-
@ christopher: Edgy won't work, as the Lenovo L520 is a Sandybridge
Laptop which is supported by Kernel since Ubuntu 11.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/89
Retested with Saucy and latest stable upstream kernel 3.11. It is still
possible to trigger the issue.
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg
@Jaroslav, this issue is also trigged when wifi is disabled via hardware
switch.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/896922
Title:
Lenovo L520 - "psmouse.c: to
As you can see from this log, I heavily typed and at the same time moved
the mouse via touchpad until the lost-sync event was trigged.
Immedeately after the event was trigged I switched to terminal using
ALT-L+TAB and killed xev with STRG+C.
** Attachment added: "xev.log - 3.11-rc2"
https://b
** Attachment added: "xinput - 3.11-rc2"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/896922/+attachment/3746770/+files/xinput
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubun
This contains the evtest using 3.11-rc2. As this was testet using VT
where I don't see the mouse pointer, I cannot be sure whether the lost
sync event was triggered.
** Attachment added: "evtest file"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/896922/+attachmen
** Attachment added: "xmodmap - 3.11-rc2"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/896922/+attachment/3746769/+files/xmodmap
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ub
Tested 3.11-rc2, the issue persists.
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.11-rc2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/b
Tested Kernel 3.10.2, issue still exists:
[ 153.617780] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at
byte 1
[ 153.622898] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at
byte 1
[ 153.627499] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at
byte
I started to use this Laptop on Lucid (11.10) therefore filed the bug
against Lucid kernel. As this was an issue in every kernel from update
to update (11.10 -> 12.04 -> 12.10 -> 13.04), the issue is now also in
13.04 and also still mainline [1]
[1] https://bugzilla.kernel.org/show_bug.cgi?id=8740
I tested v.3.10-rc7. It brought improvement as the timeout-time, where
the touchpad is unusable is reduced but it is still reproducable to
trigger the error [1] by heavy typing during using the touchpad.
I already used the latest bios version (1.21) of my laptop, as you can
see in the output [2] o
@jakub-o: It seems that there was an regression in kernel 3.9 which
introduced this issue for certain users. Which kernel do you use at the
moment ?
Do you get a similar dmesg output ?
In kernel 3.10 a patch was applied which brings some improvement in this
situation according to a number of test
23 matches
Mail list logo
