Bug 58801 - [sna ivb] X won't start at all
Summary: [sna ivb] X won't start at all
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-27 12:10 UTC by Jiri Slaby
Modified: 2012-12-27 12:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log from failed start (34.47 KB, text/plain)
2012-12-27 12:10 UTC, Jiri Slaby
no flags Details

Description Jiri Slaby 2012-12-27 12:10:24 UTC
Created attachment 72176 [details]
xorg log from failed start

X with current HEAD (46af1ff126f3fb1f9470b0cbb19c7c2b09d5b92a) won't start at all. I see only a cursor on the left top. It is caused by some commit in the range of these:
1d2fa5731b7ecfe34a8af809e45bcd3b0b70c890
46af1ff126f3fb1f9470b0cbb19c7c2b09d5b92a
Comment 1 Chris Wilson 2012-12-27 12:12:48 UTC
No errors/warnings there. Any other logs (xdm, gdm, xsession-errors, dmesg)?
Comment 2 Jiri Slaby 2012-12-27 12:19:16 UTC
(In reply to comment #1)
> No errors/warnings there. Any other logs (xdm, gdm, xsession-errors, dmesg)?

Not at all. This was tested only with X + xterm. X "graphics" is not started in the failing case, it's still in "text mode" (it's actually a fb console with proper LCD resolution).
Comment 3 Jiri Slaby 2012-12-27 12:20:26 UTC
Comment on attachment 72176 [details]
xorg log from failed start

And I attached a worng file. I had to restart X to have graphics back again and forgot to attach .old log file.
Comment 4 Jiri Slaby 2012-12-27 12:29:57 UTC
(In reply to comment #3)
> And I attached a worng file. I had to restart X to have graphics back again
> and forgot to attach .old log file.

OK, it was a linker error: a missing symbol. git clean -f -x helped as usual.
Comment 5 Chris Wilson 2012-12-27 12:33:49 UTC
That's a relief, thanks!


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.