On Fri, Mar 01, 2013 at 08:03:17AM -, Mark Murphy wrote:
Installed PPA, rebooted, aok. Rebooted / Shutdown another couple of
times to be sure, every restart successful. It looks like the PPA works
for me, Raring Ringtail development branch with Intel GM965 graphics.
** Attachment added:
** Also affects: hundredpapercuts/precise
Importance: Undecided
Status: New
** Also affects: hundredpapercuts/quantal
Importance: Undecided
Status: New
** Also affects: hundredpapercuts/raring
Importance: Undecided
Status: Confirmed
** Changed in:
** Changed in: libx11 (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1129389
Title:
libx11: add arm64 support
Status in “libx11” package
I need someone to install the xserver from this ppa, and verify it fixes
the issue:
https://launchpad.net/~bryce/+archive/lp982889
All the Xorg.0.log files posted since I mentioned this PPA are from the
stock xserver (or older). What we need is an Xorg.0.log from a session
with this PPA
The low graphics and VT boots sound like the drm race condition bug
#982889. There is a workaround posted in comment #5, and I've coded
what I think is a possible fix. The fix is in a PPA, but I'm waiting on
someone to test it to verify it does fix it before I upload it. (I'm
not 100% certain
** Description changed:
- Starting some weeks ago my graphics has been misbehaving a bit. This
- started with starting in low graphics mode from time to time, or booting
- to a VT instead of the LightDM greeter. Today I had a complete crash
- while running a Google Hangout. I've attached a
** Description changed:
Testing Raring. Suspend works ok. Resume not so much: I get the PC up,
- my screen is working but my mouse is almos freeze. Keyboard not working.
+ my screen is working but my mouse is almost freeze. Keyboard not
+ working.
+
+ #4 0x7fe492f24f32 in AbortServer ()
** Description changed:
This bug has been haunting me for a couple of weeks now.
It happens only sometimes when I interact with tabs in Firefox or
Chrome/Chromium (all three tested, both stable and beta), about 3-5
times per day.
What did I do before the crash:
Interacting
** Description changed:
didnt find any special error, just i had to reboot because 1280x1024 res
does not work for me
+
+ #9 __memcpy_ssse3_back () at
../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:97
+ No locals.
+ #10 0x7f1aecc1185e in memcpy (__len=4096, __src=0x0,
** Tags added: precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1130974
Title:
mesa_8.0.4-0ubuntu0.3 fails to build on 12.04.2
Status in “mesa” package in Ubuntu:
New
Bug
@Franck, yes the bugs belong in the same general class of issue (race
condition with drm), but the stacktraces and code paths differ so the
patch does not address the type of fault you saw.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1130974
Title:
mesa_8.0.4-0ubuntu0.3 fails to
[ 614.374] (WW) Falling back to old probe method for cirrus
[ 614.374] (--) Assigning device section with no busID to primary device
[ 614.374] (--) Assigning device section with no busID to primary device
[ 614.374] (WW) CIRRUS: More than one matching Device section found:
Autoconfigured
Looks like yet another instance of the drm race condition (bug #982889).
** Summary changed:
- SIGABRT
+ SIGABRT - cannot run in framebuffer mode [cirrus]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Invalid stacktrace. (Yay proprietary drivers?)
Got steps to reproduce? Otherwise shall assume it dupish of bug
#1126516
** Changed in: xorg-server (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1126516
Title:
Xorg crashed with SIGABRT in unavailable in ??() (Nexus 7)
Thanks for the logs.
Unfortunately neither of these match the OP's sequence of events, and
thus does not hit the problematic drm loading race that the original
reporter was seeing. So, not surprising that this patch does nothing
for your cases. I'd like to see someone who has Thomas' bug to
@Adam, interesting. Indeed your problem also appears to be distinct
from the OP. It looks like you have a hybrid graphics system and both
intel and nouveau drivers are loading. It sounds like the nouveau
driver isn't detecting any connected outputs and eventually unloads
itself. The
On Wed, Feb 20, 2013 at 02:18:25PM -, Tomas Vanderka wrote:
I don't think the patch from #31 will fix this because X is really
getting EACCESS (0xfff3) not EAGAIN as can be seen in #22
No it will; I don't check for EAGAIN specifically yet, but just a
non-zero return. I want to make it
@Adam, thanks; will follow up on bug 1130667 for the crash.
@Franck, thanks for reopening #1129220; will re-review and follow up
there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Description changed:
Posting the crash file from booting into low graphics mode
+ Related bugs: bug 1125759 (dup) and bug 982889
- Related bugs: bug 1125759 (dup) and bug 982889
+
+ #3 0x7f2a18f6a5cc in __GI___fortify_fail (msg=optimized out,
+ msg@entry=0x7f2a18fde4c7
Yes, clone mode.
This bug was opened really just for collecting a set of logs to compare
with another bug about this issue.
Effectively the problem is that gnome is responsible for setting multi-
monitors to extended when present, however it's inconsistent doing this
and comes up cloned in
** Description changed:
Posting the crash file from booting into low graphics mode
Related bugs: bug 1125759 (dup) and bug 982889
-
- #3 0x7f2a18f6a5cc in __GI___fortify_fail (msg=optimized out,
- msg@entry=0x7f2a18fde4c7 buffer overflow detected) at fortify_fail.c:37
-
** Description changed:
Posting the crash file from booting into low graphics mode
Related bugs: bug 1125759 (dup) and bug 982889
+
+
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3537980/+files/Xorg.0.log
#3 0x7f2a18f6a5cc in __GI___fortify_fail
*** This bug is a duplicate of bug 1127023 ***
https://bugs.launchpad.net/bugs/1127023
** This bug has been marked a duplicate of bug 1127023
Xorg crashed with SIGABRT in RRSetChanged()
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1127023 ***
https://bugs.launchpad.net/bugs/1127023
** This bug is no longer a duplicate of bug 1112699
Xorg crashed with SIGABRT in RRSetChanged()
** This bug has been marked a duplicate of bug 1127023
Xorg crashed with SIGABRT in RRSetChanged()
--
** Description changed:
Please note I am in recovery mode due to bug#1124661
+
+ #8 signal handler called
+ No symbol table info available.
+ #9 0x7faea458ba63 in drmmode_from_scrn (scrn=0x7faea9cbc830) at
../../src/drmmode_display.c:109
+ conf = 0x7faea9cac010
+ crtc =
from nouveau ddx, drmmode_display.c:
if (scrn) {
xf86CrtcConfigPtr conf = XF86_CRTC_CONFIG_PTR(scrn);
drmmode_crtc_private_ptr crtc = conf-crtc[0]-driver_private;
return crtc-drmmode;
}
crtc is being set to 0x1b0, which is not a
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Triaged
** Summary changed:
- Xorg crashes when exiting steam
+ Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()
--
You received this bug notification because you are a member of Desktop
Packages, which is
I think he didn't deliberately set nomodeset; it sounds like we're doing
this via grub for failsafe. Perhaps we shouldn't, but until that's
changed we should continue tracking this issue. Ideally the system
should give the user an error rather than crashing, or default to
something safe when
Offhand this sounds like a compiz crashed bug, particularly if you're
finding the issue does not appear with lubuntu or other non-unity
ubuntu's. If this is true, then you should be able to launch a terminal
window via ctrlalt t when the system is showing just the
background.
In any case, since
Thanks for the additional information; it's not evident what's gone
wrong but this is worth further investigation. Stick with the
proprietary driver in the meantime until we have something new to test.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided = High
**
Btw, 'nomodeset' is not a recommended or supported option on nouveau any
longer.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
** Description changed:
Ubuntu crashes on graphical login, unless I use boot option nomodeset or
acpi=off
lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
jolo@conroe:~$ apt-cache policy xserver-xorg-video-nouveau
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status:
** Description changed:
Testing Raring, browsing web with Chromium, then mouse almost freeze,
keyboard undesponsive, then I need to hard reset the PC.
+
+ (EE) [mi] EQ overflowing. Additional events will be discarded until
+ existing events are processed.
ProblemType: Crash
It looks like nouveau is gpu hanging on boot for some reason.
When you're setting nomodeset, it's disabling nouveau entirely so you're
booting with vesa, which won't give the best graphics. Anyway, that's
why it works in that case.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
** Description changed:
Happens when resuming from standby. Can be reproduced. Every time.
+
+
+ Jan 31 22:18:29 ubuntu kernel: [15811.392338] nouveau E[
PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9
SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
+ Jan 31
I've packaged the patch in the following PPA:
https://launchpad.net/~bryce/+archive/lp982889
Since I've so far not reproduced the bug on my own hw, I need someone
else who does see this problem to install and run the ppa and verify it
fixes the issue.
Potentially we may need to adjust
Oh, and if you do run the PPA, I'd like to see your Xorg.0.log,
regardless of whether it worked or not, so I can verify the error code
being passed up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1127023 ***
https://bugs.launchpad.net/bugs/1127023
** This bug has been marked a duplicate of bug 1127023
Xorg crashed with SIGABRT in RRSetChanged()
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Description changed:
Error after booting up
+ Not sure if it's related, but I am also experiencing bug 1125759
- Not sure if it's related, but I am also experiencing bug 1125759
+ #5 0x7fd8e83977cd in FatalError (
+ f=f@entry=0x7fd8e83c13c8 Caught signal %d (%s). Server
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = High
** Changed in: xorg-server (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1127023
Title:
Xorg crashed with
This is crashing in code added by patch autoconfig-fixup-tell-changed-
so-randr-clients-can-t.patch, added in version 2:1.13.2-0ubuntu1, which
improves hybrid graphics support. Maarten will follow up with you for
additional testing; meantime downgrading to 2:1.13.1.901-0ubuntu2 would
presumably
apport-unpack can be used to decompress the .crash file to review things
locally, however note this doesn't run the apport hook itself, so it
contains a subset of the stuff usually collected into bug reports.
apport-collect bug-number run from the troubled machine will collect
the appropriate
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
The xserver crash we'll follow up on as bug #1127023 which has full
stack trace info. The plymouthd race (actually we're not sure plymouth
is really the root cause) is effectively dupe of #982889, which is
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1125759
Intel integrated graphics boots in low graphics mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
Please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
In answer to #2, from my raring chroot:
/build/buildd/xserver-xorg-video-
intel-2.21.2/build/src/sna/../../../src/sna/sna_dri.c:186
** Changed in: xserver-xorg-video-intel (Ubuntu)
My guess is the artifacts are related to SNA, rather than to the (false)
lockup. Please test this by putting the following in your
/etc/X11/xorg.conf and then rebooting:
Section Device
Identifier Card0
Driver intel
Option AccelMethod uxa
EndSection
Assuming that eliminates the corruption
** Description changed:
This came after Rhythymbox and Movie Player stopped playing any of my
movies and songs.
+
+ [ 849.292005] i915: render error detected, EIR: 0x0010
+ [ 849.292005] i915: IPEIR: 0x
+ [ 849.292005] i915: IPEHR: 0x0a02
+ [ 849.292005] i915:
Can you explain in more detail about how your video players stopped
playing movies and songs? E.g. were the media files available locally
or over the network (e.g. cloud, nfs, etc.) I ask because there is also
an error from your Atheros ethernet driver coincident to the gpu lockup.
Iff those
Created attachment 74452
man_device_not_mandatory.patch
Here's a more thorough patch. This removes one more mention of the
mandatoriness of this optional parameter.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Created attachment 74455
Xorg.0.log
Log from verification
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/261577
Title:
Manpage needs update - Device entry no longer mandatory
Created attachment 74454
xorg.conf
xorg.conf test case used to verify
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/261577
Title:
Manpage needs update - Device entry no longer
)
Importance: Undecided = High
** Changed in: xdiagnose (Ubuntu Quantal)
Assignee: (unassigned) = Bryce Harrington (bryce)
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** No longer affects: xserver-xorg-video-intel (Ubuntu Quantal)
** Also affects: xdiagnose (Ubuntu Raring
Applied the same change as done in 2.5.1 for precise (see bug #997470).
Leaving a raring task open as a reminder that this needs disabled when
raring releases as well.
** Description changed:
+ [Impact]
+ Apport hook is triggered for GPU lockups in the stable release, in cases
where the system
Thanks for the clarification. The situation you described could well be
associated with the gpu lockup. The way to be certain is to look at
dmesg after experiencing one of these lags:
[ 630.190999] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1124699
Title:
[gm45] GPU lockup
Let's give it 2-3 weeks and see if it can still be repro'd with newer
bits. If not, we'll close as expired/unreproducible.
** Description changed:
- No idea what happened.
+ #8 signal handler called
+ #9 _sna_pixmap_move_to_cpu (pixmap=pixmap@entry=0x7fd2ac56a150,
flags=flags@entry=3) at
Fixed in revision 351
** Changed in: xdiagnose (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1119808
Title:
TypeError: unorderable
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = Low
** Summary changed:
- [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
+ [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 - no hang or
other symptoms
--
You received this bug
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
From the core dump:
#4 0x7f105c20880d in FatalError (
f=f@entry=0x7f105c210148 Cannot run in framebuffer mode. Please specify
busIDsfor all framebuffer devices\n) at ../../os/log.c:793
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1124296
Title:
Xorg crashed with SIGABRT
Status in “xorg-server” package in
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1123166
Title:
Xorg crashed with SIGABRT in DamageRegister()
Status in
For some reason apport didn't generate a proper stack trace on this one,
so please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Information type changed from Private to Public
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
** Description changed:
- crashed on upgraded
+ crashed on upgrade
+
+ #10 signal handler called
+ #11 elf_machine_runtime_setup (profile=0, lazy=1, l=0xb8d18b40) at
../sysdeps/i386/dl-machine.h:113
+ got = 0xb699d000
+ #12 _dl_relocate_object (scope=0xb8d18cf8,
** Description changed:
LENOVO T500 Raring Ringrail 3.8.0.5-generic
KDE crash while LogIn
+
+ #10 signal handler called
+ No symbol table info available.
+ #11 DamageRegister (pDrawable=0x0, pDamage=0xb90e9520) at
../../../miext/damage/damage.c:1774
+ pScrPriv = 0xb8d7b2e0
+ #12
** Summary changed:
- Xorg crashed with SIGABRT
+ Xorg crashed with SIGABRT in dl_open
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** Description changed:
#4 0x7f4ddcfde3ed in FatalError (f=f@entry=0x7f4ddcfe5d08 Cannot run in
framebuffer mode. Please specify busIDsfor all framebuffer devices\n)
at ../../os/log.c:793
-
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT Cannot run in framebuffer mode
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/bryce
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x182a76: Cannot access memory at address 0x182a76
PC (0x00182a76) not located in a known
Ringtail - Alpha amd64 (20121120)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/bryce
ProcEnviron:
- PATH=(custom, user)
- XDG_RUNTIME_DIR=set
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ XDG_RUNTIME_DIR=set
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SegvAnalysis
Similar patch, for xorg-server.
** Patch added:
0001-If-drm-device-couldn-t-be-opened-keep-trying-for-a-s.patch
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3527196/+files/0001-If-drm-device-couldn-t-be-opened-keep-trying-for-a-s.patch
** Changed in: xorg-server
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Desktop
** Patch added: First cut at a patch for this issue
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3525858/+files/drm_check_for_eagain.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
There is udev code to detect gpu lockups which will capture
i915_error_state in that case, but the general apport-collect script
doesn't (we haven't needed it up til now, but probably can't hurt to
collect). Since it sounds like that didn't happen here, it suggests
you're experiencing something
[Hook error filed as bug #1119808]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1119793
Title:
[arrandale] GPU lockup IPEHR: 0x0200
Status in
There are also bugs 1116732 and 1112871 with IPEHR: 0x0200, but the
chipset and reproduction steps are different from here, so not obviously
dupes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1117563
Title:
X hard lockup in
Looks like you got apport to pick up the gpu lockup after all: bug
#1119793
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1117563
Title:
X hard lockup in raring,
We've carried this patch for a few years, meantime a number of
improvements have been made to upstream handling of multi-GPU.
We're going to optimistically drop this patch in hopes that whatever
situation led to the crash are long since gone. This bug is kind of a
corner case we don't expect
** Bug watch added: freedesktop.org Bugzilla #24181
https://bugs.freedesktop.org/show_bug.cgi?id=24181
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=24181
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
For GPU lockup bugs with Intel graphics, you need to collect the output
of 'dmesg' and your /sys/kernel/debug/dri/0/i915_error_state file. Both
of these must be collected while the machine is locked up (e.g. by
sshing into the sick machine over ethernet). See
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
Thanks, so that confirms it is the same issue.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1112699
Title:
Xorg crashed with SIGABRT in RRSetChanged()
We're closing this bug since it is has been some time with no response
from the original bug reporter. However, if the issue still exists in
the latest development version of Ubuntu and you are the original
reporter please feel free to reopen with the requested information. If
you are not the
Unreproducible - closing.
Feel free to reopen if you discover steps to reproduce (other than
'random')
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hi Giovanni Fasino,
Hmm... I'm not sure I totally understand your description of the problem.
Could you please elaborate and clarify? You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html or the Ubuntu-X bug
reporting guidelines
401 - 500 of 1150 matches
Mail list logo
