[SOLVED] cannot login while docked after change to display resolution

[knowtown]

I have a Dell Latitude D620 that has Fedora 11 installed. I have been using Compiz as well. Everything was working great on this laptop until a few days ago when I tried to change the display resolution while the laptop was docked to a docking station and an NEC MultiSync LCD 2170nx. I used the System > Preferences > Display and lowered the resolution and the display crashed. I rebooted and I get to the login screen (gnome) and when I enter my username/password I can hear the start up sound and then just get the default Fedora 11 wallpaper and that is it. The mouse will move but the mouse icon has the arrow and the frozen circle of blue circles chasing its tail that you get when apps are loading. I completely loose the keyboard (no lights when you try cap locks or num lock) and no input from the keyboard does anything.

I tried downgrading the xorg-X11-server-Xorg and that did not help. I have tried a few other things and now I get to the point that when I try to log in it will go to the Fedora 11 wallpaper, flash a couple of times to a black screen and then bring me right back to the log in screen.

The interesting thing is that if I undock the laptop and boot I can log in normally. When I do log in I get a message that there was a Kernel error and asks if I want to send in the info. I did not record the info from that but I am sure I can get it again if it will help. Here is some more info

# uname -a
Linux laptop 2.6.30.5-43.fc11.i686.PAE #1 SMP Thu Aug 27 21:34:36 EDT 2009 i686 i686 i386 GNU/Linux

[root@laptop ~]# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
03:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

While I am still at the login screen I can change to another terminal so I can get more info if needed. If anyone has any ideas on what I can try to continue troubleshooting that would be great.

Thanks!

[knowtown]

I updated to the new xorg-X11-server-Xorg packages that are supposed to fix the log in problem and was hopeful that it would resolve the issue I am having as well. But no such luck. Still, when I attempt to log in while connected to the docking station and type the username/password, I get the start up sound and then the default wallpaper with the mouse cursor but nothing else. At this point I lose my usb keyboard as well and the only thing I can do is power off and power on again.

However, if I boot while not connected to the docking station the laptop will allow me to log in and then I get a notification that there was a kernel error. This time I captured the error:

Kernel failure message 1:
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/i915_gem_tiling.c:473 i915_gem_set_tiling+0x4a0/0x4f2 [i915]() (Not tainted)
Hardware name: Latitude D620                   
failed to unbind object for tiling switchModules linked in: rfcomm sco bridge stp llc bnep l2cap sunrpc vmnet vmblock vmci vmmon ipv6 cpufreq_ondemand acpi_cpufreq fuse dm_multipath uinput snd_hda_codec_idt arc4 ecb snd_hda_intel snd_hda_codec snd_hwdep iwl3945 snd_pcm iwlcore mac80211 snd_timer dell_laptop btusb bluetooth snd lib80211 soundcore snd_page_alloc yenta_socket rsrc_nonstatic tg3 iTCO_wdt iTCO_vendor_support rfkill ppdev i2c_i801 joydev dcdbas parport_pc parport wmi cfg80211 ata_generic pata_acpi i915 drm i2c_algo_bit video output i2c_core [last unloaded: scsi_wait_scan]
Pid: 2399, comm: Xorg Not tainted 2.6.30.5-43.fc11.i686.PAE #1
Call Trace:
[<c0435c6a>] warn_slowpath_common+0x70/0x87
[<f81e8802>] ? i915_gem_set_tiling+0x4a0/0x4f2 [i915]
[<c0435cbf>] warn_slowpath_fmt+0x29/0x38
[<f81e8802>] i915_gem_set_tiling+0x4a0/0x4f2 [i915]
[<f8185bf8>] drm_ioctl+0x202/0x292 [drm]
[<f81e8362>] ? i915_gem_set_tiling+0x0/0x4f2 [i915]
[<c05082b4>] ? ext4_file_write+0xa3/0x11b
[<c04b42ec>] ? do_sync_write+0xae/0xe9
[<c04bec4e>] vfs_ioctl+0x5c/0x76
[<c04bf0d5>] do_vfs_ioctl+0x46d/0x4a7
[<c04b411c>] ? fsnotify_modify+0x54/0x5f
[<c04bafc4>] ? path_put+0x1a/0x1d
[<c04bf155>] sys_ioctl+0x46/0x66
[<c0408478>] sysenter_do_call+0x12/0x2d
---[ end trace 4fb7cf17fda62f4c ]---

I also notice that now, there are some things that I try to do that will generate errors. For example, If I open a file browser window and select Edit > Preferences the file browser crashes with the following details:

Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.30.5-43.fc11.i686.PAE #1 SMP Thu Aug 27 21:34:36 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



---- Critical and fatal warnings logged during execution ----

** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** Gtk **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed 
** GLib-GObject **: g_object_set_data_full: assertion `G_IS_OBJECT (object)' failed 
** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed 
** GLib-GObject **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 
** GLib-GObject **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed 
** GLib-GObject **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed 


----------- .xsession-errors ---------------------
(nautilus:3696): Gtk-CRITICAL **: gtk_combo_box_append_text: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
(nautilus:3696): GLib-GObject-CRITICAL **: g_object_set_data_full: assertion `G_IS_OBJECT (object)' failed
(nautilus:3696): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:3696): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:3696): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(nautilus:3696): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:3696): GLib-GObject-CRITICAL **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(nautilus:3696): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

One more note. If I boot to my laptop successfully and then shut the lid and connect it to the docking station it will come up correctly from the suspend but if I reboot it locks up again. So it is something related to the login process when I am connected to the docking station but I have no idea what. Does anyone have any ideas on what I can try to get my docking station functionality back?

[knowtown]

I forgot that I still had this thread out here and open so I thought I would document why, in my case, this was being a problem. I am still not sure exactly what caused the problem to begin as everything was working perfectly until after an update. Anyway, turned out to be simpler than I was making it.

For some reason, when I was docked to the docking station, the laptop monitor was still staying on and was my primary display even though I did not know it. So the docking station monitor was my secondary monitor with no icons or panels. I had to position my docking station so that I could open the laptop and see the screen. Then I could log in on the laptop screen and go in and change the display options and drag the external monitor to the primary monitor. Once I did that and saved the settings I could reboot with the laptop lid closed and the external monitor acted like it did previously.