Xen Dom0 Mouse Gets Stuck on Left Side of Screen, 2.6.22-11-xen

Bug #140963 reported by Fastguy
2
Affects Status Importance Assigned to Milestone
xen-3.1 (Ubuntu)
Fix Released
Undecided
Chuck Short

Bug Description

Binary package hint: linux-source-2.6.22

Hi,

I'm trying to setup XP on my Gutsy system with Xen 3.1 and 2.6.22-11 xen kernel, on a HVM DomU, viewing through an SDL or VNC window. PV linux domains (domU) work nicely. The system is updated daily with apt-get. The problem still exists as of 19/9/2007.

Description of Problem:
With Normal Mouse Driver in xorg.conf:
A few minutes (or seconds) after I start the HVM and go through the setup instructions, the mouse cursor in Dom0 suddenly goes to top left corner of the screen and is stuck there. No movement, no up down, no left right. No matter what I do, can't move it. Only the buttons continue to work. Some other symptoms:

- I can switch to my second X server by CTRL-ALT-F8 (running on vt8) and use the mouse, but after few seconds (minutes), it gets stuck also and even locks up the system.
- I can kill the X server by CTRL-ALT-BACKSPACE and restart it, mouse comes back working on GDM/KDM screen.
- I can logout using the keyboard. Then mouse comes back working on GDM/KDM logon screen.
- If I start the HVM DomU, or if it's still running in the background, the mouse locks up again after some time.
- I'm using xorg nv driver, tried vesa driver but no change.
- Tried doing dpkg-reconfigure xserver-xorg and made all defaults, no change.

With evdev mouse driver in xorg.conf:
If I use "evdev" driver instead of the standard mouse driver in Xorg.conf, then the mouse is still stuck on the left of the screen, but I can move the cursor up and down on 1 axis only.
- I can move the cursor right towards screen area, only if I'm very very careful to move very very slowly, 1 millimeter at a time. If I do any sudden movement or move 2 mm instead of 1 mm at a time, the mouse goes back to the left side of the screen. Start from the beginning.

With this bug, the HVM DomU's are not usable, unless you want to sacrifice your mouse control.

Would this problem be because of xorg or something about xen?

Thanks for any insight,

Best regards,

Emre

Related branches

Revision history for this message
Fastguy (erenoglu) wrote :

Thought Chuck would be interested in this...

Changed in linux-source-2.6.22:
assignee: nobody → zulcss
Revision history for this message
Chuck Short (zulcss) wrote :

Please try disabling mouse acceleration if possible.

Thanks
chuck

Changed in xen-3.1:
status: New → Incomplete
Revision history for this message
Fastguy (erenoglu) wrote :

Hi Chuck,

Thanks for the comment. I disabled mouse accelaration by "xset m 0" and rerun my hvm domu. Result:
- The mouse is not stuck (with evdev driver), but xorg freezez altogether, can't even do CTRL-ALT-BACKSPACE
- With normal mouse driver, mouse goes to top left and stuck there, then xorg locks up after some time...
- Seems like a memory leak?

Emre

Revision history for this message
Fastguy (erenoglu) wrote :

In Fedora 8 Test 2, the mouse doesn't lock with Xen 3.1 and 2.6.21 dom0 kernel...

What kind of debugging information can I provide to get it working in Ubuntu Gutsy?

Emre

Revision history for this message
Fastguy (erenoglu) wrote :

What further information can I give? Shall I reinstall Ubuntu completely (tried purging all xen related packages, still same problem persists)?

What shall I do to provide further info?

Emre

Revision history for this message
Todd Deshane (deshantm) wrote :

You could look through and/or provide anything that seems relevant in:

/var/log/Xorg.*

/var/log/xen/*

# xm log

During boot up and running of the XP domU watch the log files suggested above.

Revision history for this message
Fastguy (erenoglu) wrote :

Hi Todd,

I did tail -f to all the log files, nothing happens to the logs when the mouse jumps to the top left corner. However, I tried to use the system with keyboard, went inside and outside of HVM domU window, then X crashed with the following log:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xf57fe420]
2: /usr/lib/xorg/modules/input//mouse_drv.so [0xb7bfb408]
3: /usr/bin/X [0x80c96fa]
4: /usr/bin/X [0x80b3981]
5: [0xf57fe420]
6: /usr/bin/X(Dispatch+0x8d) [0x808f35d]
7: /usr/bin/X(main+0x495) [0x8076f05]
8: /lib/tls/i686/nosegneg/libc.so.6(__libc_start_main+0xe0) [0xb7db7050]
9: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 8. Server aborting

Looks like it's mouse_drv.so but of course people may now better.

Maybe reinstalling the system will fix it?

Emre

Revision history for this message
Chuck Short (zulcss) wrote :

Fixed in next upload

Changed in xen-3.1:
status: Incomplete → Fix Committed
Revision history for this message
Chuck Short (zulcss) wrote :

xen-3.1 (3.1.0-0ubuntu17) gutsy; urgency=low

  * Fix network bridge due to ifplugd changes (LP: #144711)
  * Fix HVM so that mouse doesnt get stuck on the left side of the screen.
    (LP: #140963)

 -- Chuck Short <email address hidden> Sat, 06 Oct 2007 13:18:06 -0400

Changed in xen-3.1:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.