Yes, dmesg output when X fails to start with that kernel is in comment #18
#19 is when it starts fine
But when X failed to start it never even got to your debug code cause it
failed in drm_ioctl with EACCESS as can be seen from drm debug output.
This is where it tries to call drm_set_version and
Tomas, did you ever get a chance to test the kernel apw posted in
comment #17?
http://people.canonical.com/~apw/lp982889-precise/
** Changed in: libdrm (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start faster than drm driver is ready
To manage notification
After disabling plymouth-splash I can't reproduce this anymore.
It's a race between plymouth and xorg. Plymouth holds DRM master
(drm_setmaster_ioctl) while xorg tries to start (drm_setversion) and
fails with EACCESS because it needs DRM_MASTER for that.
It works fine if
1. plymouth never starts
Everything starts fine if nothing touches drm before X or it somehow
finishes correctly before X tries to start i guess ...
Apr 21 02:28:24 kujoniq kernel: [2.802193] [drm] Initialized i915 1.6.0
20080730 for :00:02.0 on minor 0
Apr 21 02:28:24 kujoniq kernel: [2.826851] [drm:drm_stub
So I tried a few things with drm.debug=1 kernel param
When I reproduce the problem, something (plymouth?) does drm stuff
before xorg, and xorg then gets EACCESS error from drm_setversion ioctl
(nr=0x07) and dmesg looks like this
Apr 21 02:25:35 kujoniq kernel: [0.00] Command line:
BOOT_I
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
B
Ok it is clear something odd going on with the drm ioctls. As there is
little information in the X logs, I have put some debug in the kernel to
try and help us understand this. If those of you who can reproduce this
issue could try out the following kernels and report back. When you
have success
Maybe related to #927684 #899725
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start faster than drm driver is ready
To manage notifications about this bug go to:
https://
I looked at the code and it seems it fails somewhere in kernel drm_setversion
ioctl after being called from libdrm drmSetInterfaceVersion.
I guess it's because drm driver load didn't finish yet. And there are no
usefull return values in the code involved so there's no way to know libdrm
should t
** Attachment added: "dmesg-2012-04-17"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080497/+files/dmesg-2012-04-17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
** Attachment added: "Xorg.0.log-2012-04-17"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080498/+files/Xorg.0.log-2012-04-17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
udev log and corresponding dmesg and xorg log
In this case it got to a state when lightdm/X thought it was doing fine,
but i got black screen with blinking cursor + mouse pointer
** Attachment added: "udev.txt-2012-04-17"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachmen
slangasek, we know that the drm driver can be opened by splash before its
ready. we had to add an 'EAGAIN' failure there
slangasek, we may or may not cope with that in userspace
commit 6d74feca6235b463ade4ecddd1dfdb73d30a2ff7
Author: Andy Whitcroft
Date: Thu Jul 29 16:48:21 2010 +0100
** Attachment added: "lshw.txt"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080437/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X try
Putting "sleep 1" in /etc/init/lightdm.conf was enough.
When i look at dmesg it says
[2.263168] [drm] Initialized drm 1.1.0 20060810
[2.766592] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
so i guess xorg tries to use it at [ 2.497] in some partially
initialized state
The code that does the kernel module loading is in libdrm; reassigning.
Probably best to forward this upstream for advice before we start
hacking loops into libdrm...
** Package changed: xserver-xorg-video-intel (Ubuntu) => libdrm (Ubuntu)
** Changed in: libdrm (Ubuntu)
Status: Incomplete
>From the X log, it is finding the dri card device file ok:
[ 2.446] drmOpenDevice: node name is /dev/dri/card0
[ 2.446] drmOpenDevice: open result is 9, (OK)
[ 2.497] drmOpenByBusid: Searching for BusID pci::00:02.0
[ 2.497] drmOpenDevice: node name is /dev/dri/card0
[ 2.4
bryceh: line 4396 of the udev log shows drm card0 coming up at
1.901920 after boot; the udev doesn't start on the root filesystem until
2.244658 according to BootDmesg.txt
bryceh: so the drm device *was* there for coldplugging, which makes
this a kernel bug
fundamentally, there is still a rac
A workaround is to add some sleep to /etc/init/lightdm.conf:
sleep 10
exec lightdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start faster than drm driver is re
Also, please attach your /var/log/udev from after reproducing the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start faster than drm driver is ready
To manage notifi
Meanwhile, can you post the output of sudo lshw?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X
22 matches
Mail list logo
