Bug 606029 - xorg-x11-drv-vmmouse segfaults, server aborts
Summary: xorg-x11-drv-vmmouse segfaults, server aborts
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vmmouse
Version: 14
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-20 02:19 UTC by Charlie Moschel
Modified: 2018-04-11 09:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-12 00:49:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log.old (25.66 KB, text/plain)
2010-06-22 00:57 UTC, Charlie Moschel
no flags Details
dmesg from boot (63.86 KB, text/plain)
2010-06-22 00:59 UTC, Charlie Moschel
no flags Details
/var/log/messages from fresh boot (66.22 KB, text/plain)
2010-06-22 01:02 UTC, Charlie Moschel
no flags Details

Description Charlie Moschel 2010-06-20 02:19:02 UTC
Description of problem:
In a rawhide VM, on a F-13 host:
vmmouse driver segfaults at X startup, server aborts and goes back to kdm login screen.  After entering username & pw, X seems to start normally but aborts before completion and goes back to kdm login.

Note: starting Xfce-4 session causes immediate server aborts as above.  If a kde desktop session is selected, itstarts up OK, but same segfault happens on starting any graphical program.

Version-Release number of selected component (if applicable):
Apr 15 21:35:58 Updated: xorg-x11-drv-vmmouse-12.6.9-2.fc14.i686
Jun 17 23:08:59 Updated: xorg-x11-server-Xorg-1.8.0-7.fc14.i686

How reproducible:
Every login with xfce-4 session

Steps to Reproduce:
1.  Install rawhide VM with xfce desktop
2.  Update to 18-Jun or later
3.  Log in with xfce
  
Actual results:
Can't start X, or X starts and aborts soon.

Expected results:
normal login and X startup

Additional info:

yumex update 17-jun-10 installed updates OK, and ran OK after reboot.  yumex update early AM 19-jun picked up  18-jun updates, and that's when the login problem started.  Reverting the kernel does not help (from 2.6.34-43-fc14 to 2.6.34-40 or 2.6.34-38).

Backtrace snippet:
 478.136] (II) VMWARE(0): VMMOUSE DEVICE_INIT
[   478.136] (II) VMWARE(0): VMMOUSE DEVICE_ON
[   478.136] (II) VMWARE(0): vmmouse enabled
[   478.703] (II) VMWARE(0): vmmouse enable absolute mode
[   478.703] (II) VMWARE(0): vmmouse enable absolute mode
[   502.576] 
Backtrace:
[   502.576] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e51bc]
[   502.576] 1: /usr/bin/X (0x8047000+0x5e166) [0x80a5166]
[   502.576] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x73a40c]
[   502.576] 3: /usr/lib/xorg/modules/drivers/vmware_drv.so (0x368000+0x65fb) [0x36e5fb]
[   502.576] 4: /usr/bin/X (0x8047000+0xd4a27) [0x811ba27]
[   502.576] 5: /usr/bin/X (CompositePicture+0x290) [0x810ea50]
[   502.576] 6: /usr/bin/X (miTrapezoids+0x247) [0x81b8d07]
[   502.576] 7: /usr/bin/X (CompositeTrapezoids+0xa0) [0x810e720]
[   502.576] 8: /usr/bin/X (0x8047000+0xd0533) [0x8117533]
[   502.576] 9: /usr/bin/X (0x8047000+0xca804) [0x8111804]
[   502.576] 10: /usr/bin/X (0x8047000+0x26f37) [0x806df37]
[   502.576] 11: /usr/bin/X (0x8047000+0x1b675) [0x8062675]
[   502.576] 12: /lib/libc.so.6 (__libc_start_main+0xe6) [0x442d06]
[   502.576] 13: /usr/bin/X (0x8047000+0x1b261) [0x8062261]
[   502.576] Segmentation fault at address 0x8
[   502.576] 
Fatal server error:
[   502.576] Caught signal 11 (Segmentation fault). Server aborting

Comment 1 Charlie Moschel 2010-06-20 03:11:27 UTC
Reverting to xorg-x11-server-Xorg-1.8.0-6 does not help.

Ah, reverting cairo from 1.9.8 to 1.8.10 does the trick.

Assign to Cairo?

Comment 2 Matěj Cepl 2010-06-21 07:15:33 UTC
(In reply to comment #1)
> Reverting to xorg-x11-server-Xorg-1.8.0-6 does not help.
> 
> Ah, reverting cairo from 1.9.8 to 1.8.10 does the trick.
> 
> Assign to Cairo?    

No, whatever cairo & co. it should not crash Xorg.

Please attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 Charlie Moschel 2010-06-22 00:57:14 UTC
Created attachment 425783 [details]
Xorg.0.log.old

At 17.359, kdm running waiting for input.
At 348.554, login

Comment 4 Charlie Moschel 2010-06-22 00:59:13 UTC
Created attachment 425784 [details]
dmesg from boot

dmesg from boot, through kdm, and segfault / Xorg restart

Comment 5 Charlie Moschel 2010-06-22 01:02:27 UTC
Created attachment 425785 [details]
/var/log/messages from fresh boot

/var/log/messages from fresh boot

Comment 6 Charlie Moschel 2010-06-22 01:11:20 UTC
(In reply to comment #2)

> Please attach
> 
> * your X server config file (/etc/X11/xorg.conf, if available),

No /etc/X11/xorg.conf file is being used.  Other files are attached above.

Comment 7 Charlie Moschel 2010-07-05 23:50:08 UTC
No change with:
Jul 05 18:20:00 Updated: xorg-x11-drv-vmmouse-12.6.9-5.fc14.i686
Jul 05 18:18:14 Updated: xorg-x11-server-Xorg-1.8.99.904-1.20100702.fc14.i686

No change with:
Jul 05 19:29:36 Updated: cairo-1.9.10-3.fc14.i686
Jul 05 19:29:47 Updated: cairo-devel-1.9.10-3.fc14.i686

As before, reverting to cairo-1.8.10-1.fc14.i686 works around the vmmouse segfault.

Comment 8 Matěj Cepl 2010-07-12 23:46:12 UTC
Hmm, it is actually not xorg-x11-drv-vmmouse (or at least not in the first place):

Backtrace:
[   379.669] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e51bc]
[   379.669] 1: /usr/bin/X (0x8048000+0x5d166) [0x80a5166]
[   379.669] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x20640c]
[   379.669] 3: /usr/lib/xorg/modules/drivers/vmware_drv.so (0x57f000+0x65fb) [0x5855fb]
[   379.669] 4: /usr/bin/X (0x8048000+0xd3a27) [0x811ba27]
[   379.670] 5: /usr/bin/X (CompositePicture+0x290) [0x810ea50]
[   379.670] 6: /usr/bin/X (miTrapezoids+0x247) [0x81b8d07]
[   379.670] 7: /usr/bin/X (CompositeTrapezoids+0xa0) [0x810e720]
[   379.670] 8: /usr/bin/X (0x8048000+0xcf533) [0x8117533]
[   379.670] 9: /usr/bin/X (0x8048000+0xc9804) [0x8111804]
[   379.670] 10: /usr/bin/X (0x8048000+0x25f37) [0x806df37]
[   379.671] 11: /usr/bin/X (0x8048000+0x1a675) [0x8062675]
[   379.671] 12: /lib/libc.so.6 (__libc_start_main+0xe6) [0x66cd06]
[   379.671] 13: /usr/bin/X (0x8048000+0x1a261) [0x8062261]
[   379.671] Segmentation fault at address 0x8
[   379.671] 
Fatal server error:
[   379.671] Caught signal 11 (Segmentation fault). Server aborting

Comment 9 Othman Madjoudj 2010-07-16 16:20:01 UTC
It possible to switch to standard mouse driver and see what it gives

Comment 10 Bug Zapper 2010-07-30 12:10:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Othman Madjoudj 2010-07-31 18:47:17 UTC
Removing both of VMware SVGA driver and VMmouse driver doesn't help

# yum remove xorg-x11-drv-vmmouse xorg-x11-drv-vmware

Comment 12 Othman Madjoudj 2010-07-31 18:57:14 UTC
There's no error in Xorg.log, X load VESA etc, but the screen remain blank.

I have tried with both:

# gdm
# startx

Comment 13 Othman Madjoudj 2010-08-10 22:43:01 UTC
This bug is fixed with the following update:

https://admin.fedoraproject.org/updates/xorg-x11-drv-vmware-11.0.1-1.fc14

Comment 14 Charlie Moschel 2010-08-12 00:49:13 UTC
(In reply to comment #13)
> This bug is fixed with the following update:
> 
> https://admin.fedoraproject.org/updates/xorg-x11-drv-vmware-11.0.1-1.fc14    

I can confirm; my mistake assigning to vmmouse.  Closing ...


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