Here is my log with latest from PPA.
** Attachment added: Xorg.0.log, PPA at 20130306-0900
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3559875/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
xserver-xorg-core:
Installed: 2:1.13.2-0ubuntu3~lp982889~2
Which I guess means the newer build is installed?
I'm having more success with this one. Before it was failing everytime,
now it fails about 50% of the time.
I have got logs of the successful boot and failed boot if that helps
This
This is the failed log
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3560649/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
This is the failed crash file
** Attachment added: _usr_bin_Xorg.0.crash
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3560650/+files/_usr_bin_Xorg.0.crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Thanks Adam and Bruce - for those logs it looks like you just lucked out
and didn't hit the bug, but that at least verifies the patch doesn't
introduce any regressions. I'll go ahead and upload it. It's probably
going to be largely random whether or not you hit the bug, but with the
patch
This bug was fixed in the package xorg-server - 2:1.13.2-0ubuntu3
---
xorg-server (2:1.13.2-0ubuntu3) raring; urgency=low
* Add drm_device_keep_trying.patch: When kernel reports drm device is
not available, don't give up immediately, but keep retrying for a
little bit.
On Tue, Mar 05, 2013 at 02:57:55AM -, Adam Bruce wrote:
Apport won't let me report as it's not an official package
I don't know if you can make use of the crash file itself?
Otherwise let me know how I can report it to you
Thanks, yes I know how to unpack .crash files. The file
Thanks everyone for the recent testing. In comparing everyone's logs
the following observations can be drawn:
1. The assertions made in comment #11 are incorrect. We are not seeing
EAGAIN (error code 11) but apparently EACCES (error code 13).
2. The patch I prepared is suited for handling
I've polished up the patch and tweaked it to give more informative error
messages. I've stuck the patch into the PPA if anyone would like to
test.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Still no amd64...
From the PPA status page:
Build status
[CANCELLED] Cancelled build
Started on 2013-03-03
Finished 8 hours ago (took 20 hours, 38 minutes, 42.3 seconds)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have compiled xorg-server from PPA localy. So now I have tried it, and kind
of works. Not really satisfactory, although.
What happens is that lightdm end up starting, BUT in the meantime, I have a TTY
console showing off (ie no plymouth), and it takes a looong time.
Here is the log of such a
I ran apt-cache policy xserver-xorg-core yesterday and realised the
patched hadn't been applied when I originally posted my Xorg logs.
I saw a update today from your PPA and now I see
xserver-xorg-core:
Installed: 2:1.13.2-0ubuntu3~lp982889~1
So it has now been applied. I guess this was due
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3557630/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
On Tue, Mar 05, 2013 at 01:13:39AM -, Adam Bruce wrote:
It did not boot successfuly though and went to Low Graphics mode. There
is a crash report if you want me to upload that as a report. But I don't
know if it will just be the same as: bug 1130667 - let me know if you
want me to post
Apport won't let me report as it's not an official package
I don't know if you can make use of the crash file itself?
Otherwise let me know how I can report it to you
** Attachment added: _usr_bin_Xorg.0.crash
Hmmm, I was fairly sure I added the PPA, it's in my sources.list. I did
another apt-get update and dist-upgrade this morning though and the Xorg
build date didn't change, so I'm not sure what I'm doing wrong. I can
tarball up the Xorg.0.logs as they are if you wish but I'm not sure if they
would
Just looking at the dpkg log myself and noticed this:
2013-03-01 07:31:31 upgrade xserver-xorg-core:i386 2:1.13.2-0ubuntu2
2:1.13.2-0ubuntu3~lp982889~1
2013-03-01 07:31:31 status half-configured xserver-xorg-core:i386
2:1.13.2-0ubuntu2
2013-03-01 07:31:31 status unpacked xserver-xorg-core:i386
Build for amd64 running for 12 hours and an half, and ils still
ongoing... ils that expected ??
--
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/982889
Title:
X trying to start
On Sun, Mar 03, 2013 at 10:50:43AM -, Mark wrote:
Hmmm, I was fairly sure I added the PPA, it's in my sources.list. I did
another apt-get update and dist-upgrade this morning though and the Xorg
build date didn't change, so I'm not sure what I'm doing wrong. I can
tarball up the
I think I was a bit confused this morning!
I've done a few cold boots and restarts since then, I've included them
in the attached file. I included all the Xorg log files in the first
directory. The first four directories in the tar contain log files from
cold boots, the last one is a reboot.
On Sun, Mar 03, 2013 at 04:06:47PM -, Franck wrote:
Build for amd64 running for 12 hours and an half, and ils still
ongoing... ils that expected ??
Yes, unfortunately. PPA rebuilds are executed at the lowest priority,
and it's possible all the ARM virtualized builds for phone stuff may be
64-bit 3.8.0-9-generic #18-Ubuntu SMP Thu Feb 28 17:02:06 UTC 2013
Desktop with Intel e8500 cpu, Nvidia GT9500 and default (non-Nvidia) video
driver.
I get this problem frequently following a restart from 12.04.
Pressing the reset button or executing a FULL power shutdown prior to
completion of
On Sun, Mar 03, 2013 at 06:39:55PM -, Mark Murphy wrote:
I think I was a bit confused this morning!
I've done a few cold boots and restarts since then, I've included them
in the attached file. I included all the Xorg log files in the first
directory. The first four directories in the
I was quite sure I activated the PPA, and it failed. But looking at the
version in Xorg.0.log, it seems I didn't get the right version. I did
not pin any specific version... Looking at what is installed, I only
have xerver-common coming from the PPA...
And looking at the PPA web page, it seems
On Sat, Mar 02, 2013 at 04:34:00PM -, Franck wrote:
I was quite sure I activated the PPA, and it failed. But looking at the
version in Xorg.0.log, it seems I didn't get the right version. I did
not pin any specific version... Looking at what is installed, I only
have xerver-common coming
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: Xorg.0.log
Sorry, wrong attachment file extension... here it is.
** Attachment added: Failed with PPA
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3552485/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
Tested the PPA: it still fails here. Attached is the log...
I'm availalbe to do test whatever is needed.
--
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/982889
Title:
X trying to
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:
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:
Yes, SSD too here. but I guess this ain't extraordinary nowdays... Also
this most probably has an impact, as it seems to be a race condiction...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I just have a plain old hdd, no ssd.
On Feb 28, 2013 8:41 a.m., Franck a...@mecadu.org wrote:
Yes, SSD too here. but I guess this ain't extraordinary nowdays... Also
this most probably has an impact, as it seems to be a race condiction...
--
You received this bug notification because you are
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
Bryce, would love to try this but I'm a bit worried that this is a
raring PPA with for example xserver-common 2:1.13.2-0ubuntu3 based
package and my system (12.10) has 2:1.13.0-0ubuntu6.1 installed. Warning
bells in my head say upgrading could break my work computer.
What do you think? Any chance
I also just had a success on rebooting ! Here is the relevant
Xorg.0.log. Hopes that helps.
** Attachment added: Successful Xorg.0.log on reboot
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3549545/+files/Xorg.0.log.ok
--
You received this bug notification
Yesterday booted first time, today took 5 times. Computer has SSD if
that has something to do with things (timings).
Xorg logs logs attached. Interesting ending to the .old log :)
** Attachment added: Xorg.0.log
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+attachment/3550695/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Mine has an ssd too, ocz agility 3 120GB. Maybe loading certain parts of
the system too fast make this happen if there aren't any checks
On Feb 28, 2013 8:06 AM, Jason Robinson jayw...@basshero.org wrote:
** Attachment added: Xorg.0.log.old
On 13 Feb 19, Bryce Harrington wrote:
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.
Please find my Xorg.0.log and Xorg.0.log.old attached. I see Xorg win
sometimes (1 out of 5 reboots?).
@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
in ubiquity-dm installer, we pre-empt lightdm. Then execute plymouth
deactivate followed by plymouth quit if plymouth does not have an
active-vt. Then we start Xorg straight away, if Xorg fails to start, we
retry with modified 'fallback' configs using fbdev and finally vesa. I
guess in ubiquity-dm
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
I don't know what boot this is from
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+attachment/3537982/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/982889/+attachment/3537980/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Sorry, please see attached. I see no mention of drm like you said
But it does seem to have done something as I could never boot before
without either that xorg config file or the sleep delay
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
@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
Yes it did
Reported: bug 1130667
--
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/982889
Title:
X trying to start before plymouth has finished using the drm driver
Status in
Ok, I reopen bug report #1129220 as it is not an exact duplicate...
--
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/982889
Title:
X trying to start before plymouth has finished
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
I also think this is probably an issue in plymouth because plymouth is
told to quit and release drm before X starts but it somehow does not
allways do this in time.
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.
@Bryce: Chris Wilson commented on bug #1129220 saying both bugs are really
related. I quote:
It is that bug. What's changed in the meantime is Xorg now has a platform
probe first so hits the error even earlier.
--
You received this bug notification because you are a member of Desktop
Packages,
Maybe this is related ???
http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-
nextid=735dc0d1e29329ff34ec97f66e130cce481c9607
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
No, the race here is in the global_mutex used for serialising setting
up, tearing down and opening the device. My preferred workaround is
exactly what Bryce implemented.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
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 the
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.
I have just install xserver-common from the PPA, but it did not solve
the issue here.
Here is my Xorg.0.log on failure.
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3536867/+files/Xorg.0.log
--
You received this bug notification
I have added the PPA and installed the update
First restart went to low graphics mode
I then went to recovery mode to fix the errors, restarting after that
booted successfully
Restarting again boots to low graphics mode
I go to recovery mode again to fix the errors, restarting after that
boots
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
** 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
** Tags added: patch
--
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/982889
Title:
X trying to start before plymouth has finished using the drm driver
Status in “libdrm” package
I hope this info helps... I also had this problem (and another possibly
related problem) until I replaced my new Radeon HD 6450 video card with an old
GeForce 7900 GS card. You can see more details of my problem here:
https://answers.launchpad.net/ubuntu/+source/apt/+question/221246
I would
Bug #1037518 is a dupe.
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryce)
** Tags added: raring
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = Critical
** Changed
** Tags added: quantal
--
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/982889
Title:
X trying to start before plymouth has finished using the drm driver
Status in “libdrm”
I had this bug on 12.04 and now have it on 12.10.
64-bit Thinkpad X220, Core i7 (2nd gen) and Intel 320 SSD, with external
monitor.
Bryce's workaround in comment #5 seems to have fixed it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Can confirm this bug on recent ubuntu 12.10. The workaround from Bryce
Harrington (comment #5) fixed the problem for me. thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
101 - 166 of 166 matches
Mail list logo
