Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Aug 2015 09:08:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 202645] xorg Mouse driver problem causes infinite loop in err log output
Message-ID:  <bug-202645-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202645

            Bug ID: 202645
           Summary: xorg Mouse driver problem causes infinite loop in err
                    log output
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: nogcjx@fastmail.fm

Created attachment 160336
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160336&action=edit
the head and tail of Xorg log (was 400MB), pciconf, pkg info

System freeze and Xorg log file files to 400+MB after a possible problem
loading a mouse driver -- running in kvm/qemu virtualization. I have had the
problem at least twice since yesterday when I first intalled FreeBSD 11.  I
have been running FreeBSD 10.1 in the same virtualization environment with no
problems.

The main error might have been this:

[    88.415] (II) Mouse: ps2EnableDataReporting: succeeded
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:599 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal
context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or
ErrorFSigSafe().
The offending log format message is:
Mouse autoprobe: Changing protocol to %s


The last two lines of the output below are repeated in the Xorg log file to
400+MB until I killed it.  The system was unresponsive during that time and CPU
was 100%.  Also note that this command:

vidcontrol -i mode

produces no list of valid graphics devices, whereas FreeBSD 10.1 produces a
giant list when running in a virtual machine created with the same options. 
The original mouse problem might have been related to a possible mouse problem
in the host operating system, but either way, the virtual machine should not
freeze and fill the hard drive.

I installed FreeBSD-11.0-CURRENT-amd64-20150722-r285794-disc1.iso then added
xorg from pkg. Note that when I ran
FreeBSD-11.0-CURRENT-amd64-20150722-r285794-bootonly.iso, xorg would not load
at all (after many attempts).








[    87.967] (**) sysmouse: (accel) acceleration profile 0
[    87.967] (**) sysmouse: (accel) acceleration factor: 2.000
[    87.967] (**) sysmouse: (accel) acceleration threshold: 4
[    87.968] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0
[    87.968] (II) sysmouse: SetupAuto: protocol is SysMouse
[    88.003] (II) config/devd: adding input device Mouse (/dev/psm0)
[    88.003] (II) Using input driver 'mouse' for 'Mouse'
[    88.003] (**) Mouse: always reports core events
[    88.003] (**) Option "Device" "/dev/psm0"
[    88.003] (==) Mouse: Protocol: "Auto"
[    88.003] (**) Mouse: always reports core events
[    88.037] (==) Mouse: Emulate3Buttons, Emulate3Timeout: 50
[    88.037] (**) Mouse: ZAxisMapping: buttons 4 and 5
[    88.038] (**) Mouse: Buttons: 5
[    88.038] (**) Option "config_info" "devd:psm0"
[    88.038] (II) XINPUT: Adding extended input device "Mouse" (type: MOUSE, id
8)
[    88.038] (**) Mouse: (accel) keeping acceleration scheme 1
[    88.038] (**) Mouse: (accel) acceleration profile 0
[    88.038] (**) Mouse: (accel) acceleration factor: 2.000
[    88.038] (**) Mouse: (accel) acceleration threshold: 4
[    88.045] (II) Mouse: SetupAuto: hw.iftype is 3, hw.model is 10
[    88.045] (II) Mouse: SetupAuto: protocol is ExplorerPS/2
[    88.415] (II) Mouse: ps2EnableDataReporting: succeeded
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:599 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal
context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or
ErrorFSigSafe().
The offending log format message is:
Mouse autoprobe: Changing protocol to %s

(II) Mouse autoprobe: Changing protocol to ImPS/2
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:599 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal
context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or
ErrorFSigSafe().
The offending log format message is:
Mouse autoprobe: Changing protocol to %s

(II) Mouse autoprobe: Changing protocol to ExplorerPS/2
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:599 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal
context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or
ErrorFSigSafe().
The offending log format message is:
Mouse autoprobe: Changing protocol to %s

(WW) Warned 3 times about sigsafe logging. Will be quiet now.
(II) Mouse autoprobe: Changing protocol to ImPS/2
(II) Mouse autoprobe: Changing protocol to ExplorerPS/2
(II) Mouse autoprobe: Changing protocol to ImPS/2
(II) Mouse autoprobe: Changing protocol to ExplorerPS/2

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202645-13>