Bug 27079 - System halts when starting X server
Summary: System halts when starting X server
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XFree86 4.4.0
Hardware: x86 (IA32) Linux (All)
: low major
Assignee: Jesse Barnes
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2010-03-14 22:54 UTC by russell bell
Modified: 2017-07-24 23:08 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
The Xorg.0.log (8.59 KB, text/plain)
2010-03-14 22:54 UTC, russell bell
no flags Details

Description russell bell 2010-03-14 22:54:30 UTC
Created attachment 34051 [details]
The Xorg.0.log

When I start X the machine halts, the screen goes blank, only a hard
reboot makes anything new happen.  No log records any error.  The i915
module loads, but the problem happens without it.

-- chipset: GM45
-- system architecture: i686
-- xf86-video-intel: 2.10.0 (Slackware's package)
-- xserver: 4.4rc2 (Slackware's package)
-- mesa: 7.7
-- libdrm: 2.4.18
-- kernel: 2.6.33
-- Linux distribution: Slackware 13.2 (kept up-to-date daily)
-- Machine or mobo model: eMachines 725-4520
-- Display connector: internal
-- Display: 1366x768 LCD
Comment 1 russell bell 2010-03-15 18:44:12 UTC
I built xf86-video-intel and libdrm from tarballs that I downloaded 2010 March 15 and still have the same problem, producing the same Xorg.0.log.

I welcome debugging hints.
Comment 2 russell bell 2010-03-16 17:04:53 UTC
I scheduled a shutdown in 2 minutes, then started X.  The scheduled shutdown happened.  So it would appear that keyboard input is being ignored (I can't be sure about mouse input) and nothing displays.

Comment 3 Jesse Barnes 2010-04-12 15:13:58 UTC
If a scheduled shutdown works, you can probably also log in to the target machine and figure out where X is hanging.  You can try attaching to it with gdb and/or doing 'cat /proc/`pidof Xorg`/wchan (or `pidof X` if that's how you're calling it).

The X log stops right where we first access the framebuffer, which means something is pretty seriously wrong...  Can you also attach your dmesg?
Comment 4 Jesse Barnes 2010-06-01 12:26:00 UTC
Any update here?  Hopefully it was just an old bug that's been fixed in more recent kernels and libdrm...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.