Bug 557051 - Xorg crashes when second screen is connected at login
Summary: Xorg crashes when second screen is connected at login
Keywords:
Status: CLOSED DUPLICATE of bug 558632
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_GM45
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-20 09:23 UTC by birger
Modified: 2018-04-11 07:18 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-30 22:36:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/Xorg.0.log.bak (136.29 KB, text/plain)
2010-01-20 09:23 UTC, birger
no flags Details
dmesg output (51.00 KB, text/plain)
2010-01-20 09:32 UTC, birger
no flags Details
/var/log/gdm/:0.log.1 (131.66 KB, text/plain)
2010-01-20 09:37 UTC, birger
no flags Details
Another log of crashed Xorg, added by An00biS (62.60 KB, text/plain)
2010-03-11 21:20 UTC, An00biS
no flags Details

Description birger 2010-01-20 09:23:43 UTC
Created attachment 385630 [details]
/var/log/Xorg.0.log.bak

Description of problem:
When trying to log in with dual screens X crashes.


Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.9.1-1.fc12.x86_64

How reproducible:
Always. Started when I updated my system today.

Steps to Reproduce:
1. Boot with external screen attached
2. Log in
3. 
  
Actual results:
X crashes and drops me back to login screen

Expected results:
Normal login

Additional info:
I can log in with one screen and then attach the other one.
Error messages in the Xorg.0.log.bak file seem to indicate a driver problem.
This is on a HP EliteBook 2530p laptop with an external Samsung SyncMaster 244T hooked up to the docking station. This setup has worked fine since I first installed Fedora 10 on it.

Comment 1 birger 2010-01-20 09:32:55 UTC
Created attachment 385632 [details]
dmesg output

Comment 2 birger 2010-01-20 09:37:09 UTC
Created attachment 385634 [details]
/var/log/gdm/:0.log.1

The last line is interesting, I guess:
Xorg: i830_batchbuffer.h:79: intel_batch_emit_dword: Assertion `pI830->batch_ptr != ((void *)0)' failed.

Comment 3 Chris Campbell 2010-01-23 22:21:17 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 An00biS 2010-03-11 21:20:20 UTC
Created attachment 399456 [details]
Another log of crashed Xorg, added by An00biS

Comment 5 An00biS 2010-03-11 21:32:27 UTC
Hello.

I'm havig the very same problem here. When I start X and login with external monitor plugged in, X crashes and starts anew - I get back to the login screen. Happens always.

I have notebook with intel 945GM chip and 1920x1080 external monitor.

I attached my Xorg.log. BTW sorry for the double-post.

Comment 6 birger 2010-03-12 00:09:03 UTC
I *think* the problem went away for a while, but it was definitely back today. Will test again tomorrow after todays large bunch of updates.

Comment 7 Johannes Goller 2010-06-29 02:55:52 UTC
I have a very similar problem, using the same xorg-x11-drv-intel version, but for 32 bit, on a core i5 with Intel GMA HD. The monitor can handle up to 1920x1200.

When the external monitor is conntect before or during boot, the login screen never appears and the system apparentely freezes before I can log in.

(In addition, the external monitor cannot be activated even when plugged in after log-in. xrandr then causes a total freeze of the system, as reported in Bug 608954.)

Comment 8 birger 2010-06-30 08:11:46 UTC
I have since upgraded to F13. F13 had its own display quirks, but they soon went away. I now have no problems with dual screens. Sadly I cannot do any more testing on F12.

On F13 I can now boot with 1 or 2 screens, move my laptop into or out of the docking station while powered on or while suspended. It all seems to work.

At the moment I am running xorg-x11-drv-intel-2.11.0-4.fc13.x86_64

Comment 9 Matěj Cepl 2010-06-30 22:36:37 UTC

*** This bug has been marked as a duplicate of bug 558632 ***


Note You need to log in before you can comment on or make changes to this bug.