** Description changed:

  Binary package hint: gdm
  
  I am using Jaunty Jackalope.
  
  If I log on, then "switch user" to another user, and do anything to get
  out of that second session, laptop freezes up. It does not respond to
  any keyboard or mouse movement.
  
  Steps to reproduce:
  
  1) Log on as myself
  2) Open a "Guest session" (but this will work with ANY second session)
  3) Do anything to get out of the guest session, for example Ctrl-Alt-F1 or 
"Switch user"
  
  The laptop freezes up and becomes unusable. However, linux kernel
  continues to run and I can SSH to the machine.
  
  If I ssh, su to root, and do /etc/init.d/gdm restart, all sessions
  disappear and things return to normal as if no one was logged on.
  
  This is a very obnoxious bug, as the laptop is used by my entire family
  and is almost unusable due to this bug.
  
  This does NOT in any way depend on whether I run compositing window
  manager.
  
  Searches in Xorg.*.log yield messages in the last session's log (which I
  am not sure have much to do with behavior):
  
  [    8.153714] (II) intel(0): Modeline "640x400"x85.1   31.50  640 672 736 
832  400 401 404 445 -hsync +vsync (37.9 kHz)
  [    8.153743] (II) intel(0): Modeline "640x350"x85.1   31.50  640 672 736 
832  350 382 385 445 +hsync -vsync (37.9 kHz)
  [    8.163164] (II) intel(0): EDID for output TMDS-1
  [    8.165385] (II) intel(0): xf86BindGARTMemory: bind key 7 at 0x0212c000 
(pgoffset 8492)
  [    8.382084] (II) intel(0): xf86UnbindGARTMemory: unbind key 7
  [    8.383335] (II) intel(0): EDID for output TV
  exaCopyDirty: Pending damage region empty!
  [   26.855631] (II) intel(0): xf86UnbindGARTMemory: unbind key 2
  [   26.855658] (II) intel(0): xf86UnbindGARTMemory: unbind key 3
  [   26.855717] (II) intel(0): xf86UnbindGARTMemory: unbind key 4
  [   26.855871] (II) intel(0): xf86UnbindGARTMemory: unbind key 5
  [   26.855880] (II) intel(0): xf86UnbindGARTMemory: unbind key 6
  block already free
  block already free
  block already free
  
  Also, there is nothing of interest in /var/log/messages. I did save
  straces of two gdms that were running, and did not find anything
  exciting there.
  
  potato:root:~ ###apt-cache policy gdm
  gdm:
    Installed: 2.20.10-0ubuntu1
    Candidate: 2.20.10-0ubuntu1
    Version table:
   *** 2.20.10-0ubuntu1 0
          500 http://us.archive.ubuntu.com jaunty/main Packages
          100 /var/lib/dpkg/status
+ 
+ [backtrace]
+ Program received signal SIGABRT, Aborted.
+ 0xb800f430 in __kernel_vsyscall ()
+ (gdb) backtrace full
+ #0  0xb800f430 in __kernel_vsyscall ()
+ #1  0xb7bef6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
+ #2  0xb7bf1098 in abort () from /lib/tls/i686/cmov/libc.so.6
+ #3  0xb7c2d24d in ?? () from /lib/tls/i686/cmov/libc.so.6
+ #4  0xb7c33604 in ?? () from /lib/tls/i686/cmov/libc.so.6
+ #5  0xb7c355b6 in free () from /lib/tls/i686/cmov/libc.so.6
+ #6  0xb7871837 in ?? () from /usr/lib/libdrm_intel.so.1
+ #7  0xb7871bca in ?? () from /usr/lib/libdrm_intel.so.1
+ #8  0xb7871bf4 in ?? () from /usr/lib/libdrm_intel.so.1
+ #9  0xb7871cb2 in ?? () from /usr/lib/libdrm_intel.so.1
+ #10 0xb7870336 in drm_intel_bo_unreference () from /usr/lib/libdrm_intel.so.1
+ #11 0xb78e11dc in gen4_render_state_cleanup (pScrn=0xa026460) at 
../../src/i965_render.c:1727
+       render_state = (struct gen4_render_state *) 0xc
+       i = 0
+ #12 0xb78b465d in I830LeaveVT (scrnIndex=0, flags=0) at 
../../src/i830_driver.c:3624
+       pScrn = (ScrnInfoPtr) 0xa026460
+       pI830 = (I830Ptr) 0xa026a70
+ #13 0x080de20a in ?? ()
+ #14 0x080c82a7 in xf86Wakeup ()
+ #15 0x08091352 in WakeupHandler ()
+ #16 0x0813284b in WaitForSomething ()
+ #17 0x0808d2ee in Dispatch ()
+ #18 0x0807231d in main ()

-- 
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to