Description of problem: During boot to multi-user mode, udev complains twice that vmmouse_detect terminates abnormally with status 0x000b. A SIGSEGV is reproducible when run from bash in Gnome terminal. Version-Release number of selected component (if applicable): xorg-x11-drv-vmmouse-12.6.9-1.fc13.x86_64 How reproducible: every time Steps to Reproduce: 1. /usr/bin/vmmouse_detect 2. 3. Actual results: uncaught SIGSEGV Expected results: no SIGSEGV Additional info: # gdb /usr/bin/vmmouse_detect # running in super-user mode [[snip]] Reading symbols from /usr/bin/vmmouse_detect...Reading symbols from /usr/lib/debug/usr/bin/vmmouse_detect.debug...done. done. (gdb) run Starting program: /usr/bin/vmmouse_detect Program received signal SIGSEGV, Segmentation fault. 0x0000000000400748 in VMMouseProtoInOut (cmd=0x0) at vmmouse_proto.c:62 62 __asm__ __volatile__( (gdb) bt #0 0x0000000000400748 in VMMouseProtoInOut (cmd=0x0) at vmmouse_proto.c:62 #1 VMMouseProto_SendCmd (cmd=0x0) at vmmouse_proto.c:146 #2 0x0000000000000000 in ?? () (gdb) info reg rax 0x564d5868 1447909480 rbx 0xa9b2a797 2847057815 rcx 0xa 10 rdx 0x5658 22104 rsi 0x0 0 rdi 0x0 0 rbp 0x0 0x0 rsp 0x7fffffffe1c8 0x7fffffffe1c8 r8 0x7fffffffe100 140737488347392 r9 0x7ffff7deb370 140737351955312 r10 0x8 8 r11 0x206 518 r12 0x400420 4195360 r13 0x7fffffffe330 140737488347952 r14 0x0 0 r15 0x0 0 rip 0x400748 0x400748 <VMMouseProto_SendCmd+40> eflags 0x10202 [ IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (gdb) x/5i $pc => 0x400748 <VMMouseProto_SendCmd+40>: in (%dx),%eax 0x400749 <VMMouseProto_SendCmd+41>: xchg %rax,(%rsp) 0x40074d <VMMouseProto_SendCmd+45>: mov %rdi,0x28(%rax) 0x400751 <VMMouseProto_SendCmd+49>: mov %rsi,0x20(%rax) 0x400755 <VMMouseProto_SendCmd+53>: mov %rdx,0x18(%rax) (gdb) x/12i $pc-0x20 0x400728 <VMMouseProto_SendCmd+8>: rex.WRB push %r14 0x40072a <VMMouseProto_SendCmd+10>: movw $0x5658,0x18(%rdi) 0x400730 <VMMouseProto_SendCmd+16>: push %rax 0x400731 <VMMouseProto_SendCmd+17>: mov 0x28(%rax),%rdi 0x400735 <VMMouseProto_SendCmd+21>: mov 0x20(%rax),%rsi 0x400739 <VMMouseProto_SendCmd+25>: mov 0x18(%rax),%rdx 0x40073d <VMMouseProto_SendCmd+29>: mov 0x10(%rax),%rcx 0x400741 <VMMouseProto_SendCmd+33>: mov 0x8(%rax),%rbx 0x400745 <VMMouseProto_SendCmd+37>: mov (%rax),%rax => 0x400748 <VMMouseProto_SendCmd+40>: in (%dx),%eax 0x400749 <VMMouseProto_SendCmd+41>: xchg %rax,(%rsp) 0x40074d <VMMouseProto_SendCmd+45>: mov %rdi,0x28(%rax) (gdb) l 57 VMMouseProtoInOut(VMMouseProtoCmd *cmd) // IN/OUT 58 { 59 #ifdef __x86_64__ 60 uint64_t dummy; 61 62 __asm__ __volatile__( 63 "pushq %%rax" "\n\t" 64 "movq 40(%%rax), %%rdi" "\n\t" 65 "movq 32(%%rax), %%rsi" "\n\t" 66 "movq 24(%%rax), %%rdx" "\n\t" (gdb) continue Continuing. Program exited with code 01. ### SIGSEGV not caught (gdb)
i have the same problem with f13 rc3 Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: udevd-work[586]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power/level} for writing: No such file or directory udevd-work[611]: '/usr/bin/vmmouse_detect' unexpected exit with status 0x000b udevd-work[599]: '/usr/bin/vmmouse_detect' unexpected exit with status 0x000b How reproducible: every time i boot fedora.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * output of the dmesg command, * system log (/var/log/messages), and * X server log file (/var/log/Xorg.*.log) 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.
Created attachment 417625 [details] output from 'dmesg' There is no file /etc/X11/xorg.conf .
Created attachment 417628 [details] today's /var/log/messages
Created attachment 417629 [details] today's /var/log/Xorg.0.log
The complaint udevd-work[611]: '/usr/bin/vmmouse_detect' unexpected exit with status 0x000b no longer appears from udev at boot, however running /usr/bin/vmmouse_detect directly (as in original Description) still gets SIGSEGV.
I'm seeing this too but only during boot running Fedora 13 as a KVM guest but I don't see this in the host (F13 too).
(In reply to comment #7) > I'm seeing this too but only during boot running Fedora 13 as a KVM guest but I > don't see this in the host (F13 too). If it happens with a KVM guest, then it is not this bug ... we don't use vmmouse for KVM guests. Please file a separate bug attaching information as per comment 2. Thank you
I was investigating the same bug on openSUSE and discovered that reverting the following upstream commit seems to resolve the problem: http://cgit.freedesktop.org/xorg/driver/xf86-input-vmmouse/commit/?id=bcdec3d0cd4434770cd841c33c030e0d7203881f
Comment 6 seems to indicate that the OP only gets the error now when running from the command line. I get this same error showing in boot messages on every boot in release version of F13. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
See this one two, printed twice, on every boot of a laptop, which I reboot frequently to switch from WinXpPro (work) and F13 (home). May happen too on my three other F13 systems, but those only reboot on kernel updates.
Since I have migrated to F13 I also have twice this error at boot time, but not on command line. PS: The F13 is running under a VirtualBox System is uptodate with yum upgrade.
Duplicate of bug 604660.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.