Date: Mon, 22 May 2000 11:49:50 -0500 From: "Alejandro Ramirez" <ales@megared.net.mx> To: <current@FreeBSD.ORG>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: "Wes Peters" <wes@softweyr.com>, "Kazutaka YOKOTA" <yokota@zodiac.mech.utsunomiya-u.ac.jp>, <frank@exit.com> Subject: Re: Anyone else seeing jumpy mice? Message-ID: <070601bfc40d$bf072a40$d2630a0a@megared.net.mx> References: <3970.958963729@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all,
Im also seeing this messages in FreeBSD 3.4 Release:
> psmintr: out of sync (00c0 != 0000).
> psmintr: out of sync (0040 != 0000).
> psmintr: out of sync (0080 != 0000).
It doesnt even have X installed, nor APM enabled (BIOS & KERNEL) its a smtp,
pop3 & DNS dedicated server, I have just enabled the ps/2 mouse to copy
betwen consoles, the server in question its a IBM Netfinity 5000, the lines
in the rc.conf file looks like this:
moused_enable="YES"
moused_type="auto"
moused_port="/dev/psm0"
moused_flags="-3"
allscreens_flags="-m on"
% uname -a
FreeBSD xxx.xxx.xxx 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Apr 3 10:24:33
GMT 2000 root@xxx.xxx.xxx:/usr/src/sys/compile/kernel i386
% uptime
11:40AM up 45 days, 21:47, 1 user, load averages: 0.21, 0.25, 0.24
% ps ax|grep moused
207 ?? Is 0:00.44 moused -3 -p /dev/psm0 -t auto
P.S. These messages started to happen a month after the installation date,
the mouse hasnt been used since, because this server its in another city,
and the people in there doesnt even have acces to the console.
If you need more info, just let me know.
I Hope this can help you ...
Ales
----- Original Message -----
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
To: <current@FreeBSD.ORG>
Sent: Sunday, May 21, 2000 9:48 PM
Subject: Anyone else seeing jumpy mice?
> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
>
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != 0000).
>
> I've seen it for the last few weeks and can only think that something
> must be stomping on the psm driver now (or the driver is missing
> interrupts for reasons of its own). Anyone else seeing this?
>
> - Jordan
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?070601bfc40d$bf072a40$d2630a0a>