[Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

[Bryce Harrington]

On Wed, Feb 20, 2013 at 02:18:25PM -0000, Tomas Vanderka wrote:
> I don't think the patch from #31 will fix this because X is really
> getting EACCESS (0xfffffff3) 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 check for specific error codes but
want to see what actually is coming through when the patch's code gets
hit.  I agree that while the kernel guys say it should be EAGAIN, the
data I've seen so far suggests a different error code (maybe EACCESS).
 
> 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. Maybe there should be "plymouth --wait quit"
> instead of "plymouth quit" in /etc/init/plymouth-stop.conf? I tried to
> find how exactly "plymouth quit" is handled (especially if the plymouth
> daemon really releases drm before that command returns) but I never got
> to the answer.

Well maybe, however we've seen people disable plymouth but still hit the
race condition.  My goal with this patch is to fix it on the X side so
it'll work in the general case of anything holding the drm device too
long.
 
> You can try to change the X patch in #31 to spin also on EACCESS (bad
> solution imho) or plymouth should be fixed to really release drm when
> told to quit.
> 
> And I also had this problem in Fedora, someone else reported it at
> https://bugzilla.redhat.com/show_bug.cgi?id=855677

Thanks.
 
> I reenabled plymouth-splash and will play a little with it again, but it
> happens randomly in maybe 1/10 reboots so it's not easy to hit.

Yeah, and it's possible there are several different failure modes
depending on how the race is run, each needing a separate fix.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libdrm 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 in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  In Progress

Bug description:
  X server fails to start the first time after boot, it works fine when
  I start it again.

  Looks like a race condition with intel drm initialization, i guess X
  tries to start faster than drm driver is initialized so it fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Apr 16 10:35:28 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. Device [1462:7750]
   Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller])
     Subsystem: Giga-byte Technology Device [1458:21fa]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: MSI MS-7750
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-G43 (G3) (MS-7750)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7750
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.7.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions