Re: Anyone else seeing jumpy mice?

2000-05-29 Thread Nate Williams

 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 != ).
 
 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?

Yep, it was related to having a newer mouse that wasn't supported quite
right under the psm code.  What I'm doing now is plugging in a different
mouse, and then switching mice *after* the probe succeeds which causes
the problem to go away.

I sent email to Kazu, but unfortunately I dropped the ball when he asked
for more feedback.


Nate

ps. It always seems to jump left and up...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-26 Thread Wes Peters

Matthew Dillon wrote:
 
 :  kernels then two weeks old for 4.0, and four weeks old for 5.0).
 :
 : Yes.  This started long before the SMP cleanup MFC.  I'm running 4-stable.
 :
 :Let me second this.  I have been unable to use moused on my laptop
 :(Sony VAIO 505TR with Versapad) since syscons changes went in right
 :after 4.0-RELEASE (it worked under -RELEASE), but broke under -STABLE.
 :I had a discussion with Kazutaka YOKOTA, but nothing was resolved.
 :Cut and paste were OKish on the ttyvN with a very twitchy pointer image,
 :but it was completely unusable under XFree86-3.3.6 that shipped with
 :-RELEASE (not sure if I should rebuild X or not).  I have been running
 :sans moused ever since (so it is not hardware related in my case).
 :
 :S
 :---
 :Sean O'ConnellEmail: [EMAIL PROTECTED]
 
 Ok, at least it wasn't me :-)  That's all I care about, bye! .. heh heh,
 just kidding.  It seems that people are homing in on the problem being
 syscons, that's two so far.  Is there any further corroboration?

Yes, I updated from 3.3 to 4.0-CURRENT about 5 days after the release,
and it started happening for me right then.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-25 Thread Eilko Bos

 FYI:
 
 FreeBSD 4.0-STABLE #0: Wed May 24 13:34:42 GMT 2000
 CPU: Pentium II/Pentium II Xeon/Celeron (265.75-MHz 686-class CPU)
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 
 I have a HP-mouse (2 button) which is actually a logitec.
 
 I tried with both moused and X. Both giving errors:
 
  psmintr: out of sync (0080 != ).
  psmintr: out of sync (00c0 != ).
  psmintr: out of sync (0040 != ).
 
 In /etc/rc.conf, set
 
   moused_enable="YES"
   moused_type="auto"
   moused_port="/dev/psm0"
   moused_flags=""
 
 In the "Pointer" section of /etc/XF86Config, you should have
 
   Protocol "SysMouse" # or "Auto"
   Device "/dev/sysmouse"
 
 Do you still see error messages after setting up the things as above?

It doesn't really matter if I do it from the command line, using moused or
if I set it in rc.conf, right?  And I assume the 'apply' button in the
'mouse'-section of XF86Setup does, end the end, behave like I started X with
the settings as above.
And yes, with settings as above it is giving problems.

Meantime, I am still trying to get it back to 4.0_release, I did that last
night, but after that the mouse was not working AT ALL. Most probably I did
something stupid ;-) I reinstall from CD now. I don't have time to track
down the mistake I made with the downgrade.

---
Eilko.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Kazutaka YOKOTA

 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?

   FWIW, with -current from 5/8, I don't have any of those in
/var/log/messages, going back to 5/1. I have a logitech PS/2 mouse, and
I don't use moused, since I couldn't get it to work with my wheel. 

In what way doesn't the wheel work?

Would you provide the following information?

1. Which mouse model is it?
2. /var/run/dmesg.boot after starting "boot -v" at the loader prompt.
3. Run moused as follows to get debug log and send it to me.
moused -d -f -p /dev/psm0  /tmp/moused.out

Thank you.

Kazu



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Kazutaka YOKOTA


I see those messages, however I do not have any problems mousing afterwards.
I'm using a switchview, which at least resets the mouse when I switch.

Your Logitech 3-button mouse may be generic enough and is not affected
much by power cut when you use the KVM.  Which model is it?

On Sun, May 21, 2000 at 08:41:57PM -0700, Mike Smith wrote:
  Um, if you don't see the above message but see erratic mouse
  behavior, then there may be a configuration problem (for moused or
  X), or a hardware problem.

My configuration works fine, the mouse worked without messages until
I installed 5.0-current.

Do you get the "out-of-sync" messages when you don't use KVM?

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Kazutaka YOKOTA


I stopped using moused sometime during 4.0-current as a result of this.

When was it?

It ocasionally froze, moved randomly around the screen, clicked without
being touched, and yes, got extreamly jumpy.  The hardware's rock solid,
and once I ditched moused and read the device directly, life went back to
normal.

Umm...

The "out-of-sync" message comes from the psm driver and is generated
when the driver finds mouse data stream odd.  It doesn't matter
if it is moused or the X server that is reading from the psm driver.

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Jordan K. Hubbard

 Umm...
 
 The "out-of-sync" message comes from the psm driver and is generated
 when the driver finds mouse data stream odd.  It doesn't matter
 if it is moused or the X server that is reading from the psm driver.

It could be some weird interaction with the driver that only moused
exhibits, however.  I will try things without moused and use the PS/2
mouse directly from X to see if anything changes.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Eilko Bos

Kazutaka YOKOTA wrote:

 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?

Yes. Just today, I was installing a Digital PC with 4.0-release. Before
start using it, I upgraded to 4.0 Stable. Then I starded configuring X.

FYI:

FreeBSD 4.0-STABLE #0: Wed May 24 13:34:42 GMT 2000
CPU: Pentium II/Pentium II Xeon/Celeron (265.75-MHz 686-class CPU)
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0

I have a HP-mouse (2 button) which is actually a logitec.

  FWIW, with -current from 5/8, I don't have any of those in
/var/log/messages, going back to 5/1. I have a logitech PS/2 mouse, and
I don't use moused, since I couldn't get it to work with my wheel. 

I tried with both moused and X. Both giving errors:

psmintr: out of sync (0080 != ).
psmintr: out of sync (00c0 != ).
psmintr: out of sync (0040 != ).

I tried several mousesystems, like 'ps/2', 'sysmouse', 'logitec'. They all
go crappy. In XF86Setup, it reacts slow on movements, and when it moves, it 
is in 'burstmode' ;-): It will jump to the opposite part of the screen. 
2-buttons emulation SEEMS to work. Since the rest didn't, I could not really
test. On console, with moused, the mouse moves in the same (unpredictable)
way, and now I see that 2-buttons emulation does not work.

I tried the

options PSM_HOOKRESUME
options PSM_RESETAFTERSUSPEND

in the kernel, to no avail. After that, I tried the patch on 'apic_vector.s'
provided by Bruce, also to no avail.
In the end I downgraded to 4.0-release again. I will test that tomorrow.

On my other machine, which is a Dell optiplex gx1, with 
FreeBSD 5.0-CURRENT #9: Tue May  2 13:17:27 CEST 2000
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
and a 3-button Digital mouse, I don't have the problem. But I really need
to upgrade to the next current ;-)) I am curious if I have the same problems
then on that machine.

--
Eilko Bos.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-24 Thread Kazutaka YOKOTA


Yes. Just today, I was installing a Digital PC with 4.0-release. Before
start using it, I upgraded to 4.0 Stable. Then I starded configuring X.

FYI:

FreeBSD 4.0-STABLE #0: Wed May 24 13:34:42 GMT 2000
CPU: Pentium II/Pentium II Xeon/Celeron (265.75-MHz 686-class CPU)
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0

I have a HP-mouse (2 button) which is actually a logitec.

 FWIW, with -current from 5/8, I don't have any of those in
/var/log/messages, going back to 5/1. I have a logitech PS/2 mouse, and
I don't use moused, since I couldn't get it to work with my wheel. 

I tried with both moused and X. Both giving errors:

   psmintr: out of sync (0080 != ).
   psmintr: out of sync (00c0 != ).
   psmintr: out of sync (0040 != ).

I tried several mousesystems, like 'ps/2', 'sysmouse', 'logitec'. They all
go crappy. 

It's no use trying one protocol type after another like this...
You should configure moused and X as follows.

In /etc/rc.conf, set

moused_enable="YES"
moused_type="auto"
moused_port="/dev/psm0"
moused_flags=""

In the "Pointer" section of /etc/XF86Config, you should have

Protocol "SysMouse" # or "Auto"
Device "/dev/sysmouse"

Do you still see error messages after setting up the things as above?

Kazu

On my other machine, which is a Dell optiplex gx1, with 
   FreeBSD 5.0-CURRENT #9: Tue May  2 13:17:27 CEST 2000
   psm0: PS/2 Mouse irq 12 on atkbdc0
   psm0: model Generic PS/2 mouse, device ID 0
and a 3-button Digital mouse, I don't have the problem. But I really need
to upgrade to the next current ;-)) I am curious if I have the same problems
then on that machine.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Boris Popov

On Tue, 23 May 2000, Bruce Evans wrote:

 The patch seems to have completely broken fast interrupts.
 GET_FAST_INTR_LOCK is neither necessary nor sufficient as far as I can see.
 The necessary and sufficient locking is done by COM_LOCK() in individual
 drivers.  The patch changed GET_FAST_INTR_LOCK from s_lock(fast_intr_lock),
 which does nothing very well, to `sti(); get_mplock(); cli();', which
 essentially de-prioritizes "fast" interrupts from "higher than the highest"
 (higher than clock interrupts which are nominally highest) to "lower than
 the lowest" (lower than all normal interrupts, all software interrupts,
 and all MP-unsafe syscalls).

Yes, this explains problems with sio.

 Untested fix:

Thank you. It works and no crashes experienced yet.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Matthew Dillon

:The patch seems to have completely broken fast interrupts.
:GET_FAST_INTR_LOCK is neither necessary nor sufficient as far as I can see.
:The necessary and sufficient locking is done by COM_LOCK() in individual
:drivers.  The patch changed GET_FAST_INTR_LOCK from s_lock(fast_intr_lock),
:which does nothing very well, to `sti(); get_mplock(); cli();', which
:essentially de-prioritizes "fast" interrupts from "higher than the highest"
:(higher than clock interrupts which are nominally highest) to "lower than
:the lowest" (lower than all normal interrupts, all software interrupts,
:and all MP-unsafe syscalls).

It isn't quite that bad.  Remember that interrupts are vectored to
the cpu already running in supervisor mode, and the MP lock is recursive.
So GET_FAST_INTR_LOCK will generally not block against MP-unsafe
syscalls or anything else.  It will still operate as a high-priority
interrupt.

I understand the point about COM_LOCK, and agree - but I also never 
trusted the MP-safeness of the fast-interrupt code hack so lets not
commit this until we have a chance to audit the entire fast-interrupt
path.  Frankly, I would much rather see MP-safe NIC interrupt code 
then MP-safe serial interrupt code.

-Matt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Manfred Antar

Not to change the subject ,but
mptable causes a panic on my machine running current.
If I revert back to a kernel compiled on the 13th of May everything works
fine. I think there were some changes made to the SMP code on the 14th or 15th
also the binutils were upgraded and I'm not sure what caused it.
With a current kernel I get this when booting:

Programming 24 pins in IOAPIC #0
AP #1  (PHY# 12) failed!
panic y/n [y] panic: bye-bye
mp_lock = 0001; cpuid = 0; lapic.id = 
Uptime: 0s

I'm going to check out a sys tree from the 14th and try rebuilding a kernel and see 
if that works.
The kernel I have  Sun May 14 15:39:19 PDT 2000
works fine
Manfred

==
||  [EMAIL PROTECTED]  ||
||  Ph. (415) 681-6235  ||
==



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Vallo Kallaste

On Tue, May 23, 2000 at 11:06:38AM -0700, Manfred Antar [EMAIL PROTECTED] wrote:

 Not to change the subject ,but
 mptable causes a panic on my machine running current.
 If I revert back to a kernel compiled on the 13th of May everything works
 fine. I think there were some changes made to the SMP code on the 14th or 15th
 also the binutils were upgraded and I'm not sure what caused it.
 With a current kernel I get this when booting:
 
 Programming 24 pins in IOAPIC #0
 AP #1  (PHY# 12) failed!
 panic y/n [y] panic: bye-bye
 mp_lock = 0001; cpuid = 0; lapic.id = 
 Uptime: 0s

I've just completed world and compiled new kernel and found that my
system reboots right after showing about seven lines of usual boot
messages. I've found that UP GENERIC works and UP custom kernel works
but SMP is broken. It has to do something with last three days of
commits, because my last working SMP kernel is from Friday 19'th.
Running mptable on the UP kernel doesn't cause crash for my system.
Reboot is totally silent so I don't have any other info, sorry, I've
only thought it happens about same time as the APIC probe.
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Manfred Antar

At 09:00 PM 5/23/2000 +0200, Vallo Kallaste wrote:
On Tue, May 23, 2000 at 11:06:38AM -0700, Manfred Antar [EMAIL PROTECTED] wrote:

 Not to change the subject ,but
 mptable causes a panic on my machine running current.
 If I revert back to a kernel compiled on the 13th of May everything works
 fine. I think there were some changes made to the SMP code on the 14th or 15th
 also the binutils were upgraded and I'm not sure what caused it.
 With a current kernel I get this when booting:
 
 Programming 24 pins in IOAPIC #0
 AP #1  (PHY# 12) failed!
 panic y/n [y] panic: bye-bye
 mp_lock = 0001; cpuid = 0; lapic.id = 
 Uptime: 0s

I've just completed world and compiled new kernel and found that my
system reboots right after showing about seven lines of usual boot
messages. I've found that UP GENERIC works and UP custom kernel works
but SMP is broken. It has to do something with last three days of
commits, because my last working SMP kernel is from Friday 19'th.
Running mptable on the UP kernel doesn't cause crash for my system.
Reboot is totally silent so I don't have any other info, sorry, I've
only thought it happens about same time as the APIC probe.
-- 

I'm backing out to kernel sources as of the 13th and am building a kernel now.
I'm running SMP. It's funny I had a kernel from Sunday  5/21 and it boot's fine and 
works in the 
SMP mode but mptable causes a panic.
I just booted one from sources from the 13th same thing. I think this has something to 
do 
with the new binutils as a kernel built on the 14th and restored via tape works fine 
but if i
check out the sys tree from the 14th and build a kernel it panics at the APIC probe.
Or maybe I need to rebuild some library too from the 14th, I'm not sure if the kernel 
links
to any library.
I guess a good test would be to make world from before the binutil change and try a 
kernel
built from that
Manfred


==
||  [EMAIL PROTECTED]  ||
||  Ph. (415) 681-6235  ||
==



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Wes Peters

Kazutaka YOKOTA wrote:
 
  FWIW, those are all the symptoms of this problem too.  The mouse
  doesn't just jump, it goes nuts with simulated button events. :)
 
 This can really suck with certain email clients, too.
 
 My hardware: Sony VAIO PCG-F160 w/integrated trackpad:
 
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
 
 Don't the following kernel options work for this machine?
 
 options PSM_HOOKRESUME
 options PSM_RESETAFTERSUSPEND

They compile and boot fine.  I'll let you know in a day or two if this
stops the crazy mouse syndrome.  For what it's worth, I've seen this
both before and after a suspend/resume.

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jonathan Hanna


On 22-May-00 Kazutaka YOKOTA wrote:
 
 Please, if you can avoid it, don't unplug and replug the mouse while
 the power is on.  The PS/2 mouse interface is generally not capable
 of hot plugging/unplugging.
 
 As for sleep/wake-up problem on the laptop computers, you may
 be able to resolve the problem by adding the following kernel options.
 
 options PSM_HOOKRESUME
 options PSM_RESETAFTERSUSPEND

Is it possible to do a reset after seeing the "psmintr: out of sync (00c0 != )"?

Jonathan Hanna [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Doug Barton

"Jordan K. Hubbard" wrote:
 
 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 != ).
 
 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?

FWIW, with -current from 5/8, I don't have any of those in
/var/log/messages, going back to 5/1. I have a logitech PS/2 mouse, and
I don't use moused, since I couldn't get it to work with my wheel. 

HTH,

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jordan K. Hubbard

 Jonathan Hanna wrote:
  Yes, recently on 4.0-stable, though provoked by unplugging and
  replugging in the mouse. It did not recover. This I thought
  sounded like a PR on the mouse being dead after a wakeup
  from sleep mode.
 
 Come to think of it, I do use a KVM switch, but this usually happens after
 I've been hacking away a while, having not touched the switch in hours or
 days.  Still, it could be related, I guess.

Well, in my case it happens without any such things going on.  More to
the point, it *never* works entirely right, from the moment I boot the
machine to the moment I turn it off.  The mouse is always jumpy now,
and it's the same mouse I've been using for years so it's not a
physical mouse problem of any kind.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jordan K. Hubbard

Nope!

 May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
 
 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?
 
 Do you, by any chance, use a KVM?
 
 Kazu



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jordan K. Hubbard

  options PSM_HOOKRESUME
  options PSM_RESETAFTERSUSPEND
 
 They compile and boot fine.  I'll let you know in a day or two if this
 stops the crazy mouse syndrome.  For what it's worth, I've seen this
 both before and after a suspend/resume.

I doubt that this will help me since the PS/2 mouse in my situation
is hooked to a desktop machine with APM entirely disabled.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Stijn Hoop

Just one more "problem" report:

I see those messages, however I do not have any problems mousing afterwards.
I'm using a switchview, which at least resets the mouse when I switch.

On Sun, May 21, 2000 at 08:41:57PM -0700, Mike Smith wrote:
  Um, if you don't see the above message but see erratic mouse
  behavior, then there may be a configuration problem (for moused or
  X), or a hardware problem.

My configuration works fine, the mouse worked without messages until
I installed 5.0-current.

 You can also get this if you have moused running but have configured X to 
 point to the physical mouse device rather than /dev/sysmouse.

I do have /dev/psm0 in my XF86Config. You're saying it is better to
use /dev/sysmouse, Protocol moused?

BTW, it's a standard Logitech PS/2 3-button mouse.

--Stijn

-- 
  FreeBSD:  | Antonym, n.:  The opposite of the word you're trying to  
 The power to serve | think of.
  www.freebsd.org   |  


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Matthew Thyer

Try flags 0x04 on device psm.

This undocumented option fixed my PS/2 IntelliMouse clone that has a
wheel (which is also the center button).

Bug Kazu as to why this isn't documented in LINT.

"Jordan K. Hubbard" wrote:
 
 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 != ).
 
 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 [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Christian Weisgerber

Stijn Hoop [EMAIL PROTECTED] wrote:

 I do have /dev/psm0 in my XF86Config. You're saying it is better to
 use /dev/sysmouse, Protocol moused?

If you have moused running, set XF86Config to /dev/sysmouse, protocol
"MouseSystems".

-- 
Christian "naddy" Weisgerber  [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Kazutaka YOKOTA

Try flags 0x04 on device psm.

This undocumented option fixed my PS/2 IntelliMouse clone that has a
wheel (which is also the center button).

As you have not given details on your problem and mouse,
I don't understand why this flag solved your problem... 
That flag simply sets the mouse's resolution to "high".

Bug Kazu as to why this isn't documented in LINT.

This flag IS documented in the man page for psm(4) :-)
As Bruce says, LINT is not the place for documenting driver flags.
They should be explained fully in the drivers' manual pages.

Kazu



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread David Scheidt

On Mon, 22 May 2000, Jordan K. Hubbard wrote:

 Well, in my case it happens without any such things going on.  More to
 the point, it *never* works entirely right, from the moment I boot the
 machine to the moment I turn it off.  The mouse is always jumpy now,
 and it's the same mouse I've been using for years so it's not a
 physical mouse problem of any kind.
 

Unless your mouse died of old age.  The PS/2 mouse I had been using for
quite some time started to behave exactly like yours at some point last
year.  I avoided replacing it for a long time, since I couldn't find another
mouse with a long enough cord.


David



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Alejandro Ramirez

Hi all,

Im also seeing this messages in FreeBSD 3.4 Release:

 psmintr: out of sync (00c0 != ).
 psmintr: out of sync (0040 != ).
 psmintr: out of sync (0080 != ).

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 [EMAIL PROTECTED]:/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" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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 != ).

 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 [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Matthew Dillon


:
: 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 != ).
:
:I saw this happen once, during a period heavy disk and serial
:activity.
:
:-GAWollman

I got an email from Boris Popov in regards to getting more silo
overflows after the SMP cleanup patch then before.

One thing the patch removed was the hack that allowed certain interrupts
(tty interrupts) to run in parallel with the supervisor.

Now, I must say, that there is no way we are going to add that hack back
in ... it was a real mess and is simply not worth it, and when we 
move to the interrupt threading model we can truely make the serial 
interrupt SMP-safe and do away with the issue once and for all.

I don't know if the mouse problems are related or not, did anyone have
jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
kernels then two weeks old for 4.0, and four weeks old for 5.0).

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Frank Mayhar

Matthew Dillon wrote:
 I don't know if the mouse problems are related or not, did anyone have
 jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
 kernels then two weeks old for 4.0, and four weeks old for 5.0).

Yes.  This started long before the SMP cleanup MFC.  I'm running 4-stable.
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Sean O'Connell

Frank Mayhar stated:
 Matthew Dillon wrote:
  I don't know if the mouse problems are related or not, did anyone have
  jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
  kernels then two weeks old for 4.0, and four weeks old for 5.0).
 
 Yes.  This started long before the SMP cleanup MFC.  I'm running 4-stable.

Let me second this.  I have been unable to use moused on my laptop 
(Sony VAIO 505TR with Versapad) since syscons changes went in right
after 4.0-RELEASE (it worked under -RELEASE), but broke under -STABLE.
I had a discussion with Kazutaka YOKOTA, but nothing was resolved.  
Cut and paste were OKish on the ttyvN with a very twitchy pointer image,
but it was completely unusable under XFree86-3.3.6 that shipped with 
-RELEASE (not sure if I should rebuild X or not).  I have been running
sans moused ever since (so it is not hardware related in my case).

S
---
Sean O'ConnellEmail: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University   Fax:   (919) 684-8594


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Trevor Johnson

Matthew Dillon wrote:

 : May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).

 Now, I must say, that there is no way we are going to add that hack back
 in ... it was a real mess and is simply not worth it, and when we 
 move to the interrupt threading model we can truely make the serial 
 interrupt SMP-safe and do away with the issue once and for all.

Looking at the old driver (src/sys/i386/isa/Attic/psm.c,v) I see a note
that the hardware offers a polling mode (not implemented in that driver),
where the mouse only sends packets after getting requests for them.  If
there are intractable problems with handling interrupts, perhaps that mode
could be used instead (maybe if no one had used the mouse recently,
polling could be done less often, to conserve CPU time).

 I don't know if the mouse problems are related or not, did anyone have
 jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
 kernels then two weeks old for 4.0, and four weeks old for 5.0).

I'm running 4.0-STABLE from May 5 23:39 PDT and I found one of those
messages (just like Jordan's except for the hostname and time). I think I
was at the computer when it happened, but I don't remember any erratic
movement of the mouse pointer, nor have I ever noticed any under FreeBSD.  
I have XFree86 3.3.6 running from xdm, using /dev/sysmouse as the mouse
device.  I have moused running too, and was probably in text mode when the
tragedy^H^H^H^H^H^H^H error message happened. My computer has a Digital
Equipment Corp. PC7XS-CA three-button mouse, a Winbond W83977TF-AW I/O
chip, and Intel 440 BX chip set.

I saw this problem a long time ago, most memorably on an IBM PS/2 55SX
with an IBM mouse, under Windows 3.0.  Sometimes the mouse pointer would
move suddenly all around the screen, and programs would behave as though
someone were pressing the mouse buttons. Searching the Web, I see that the
Linux folks have had the problem too:

http://www.tux.org/hypermail/linux-kernel/1999week01/0953.html
http://gwyn.tux.org/hypermail/linux-kernel/1999week03/0435.html

One wanted to program the remote (polling) mode:
http://www.linuxhq.com/guides/KHG/HyperNews/get/khg/333.html
.
--
Trevor Johnson
http://jpj.net/~trevor/gpgkey.txt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Matthew Dillon


:  kernels then two weeks old for 4.0, and four weeks old for 5.0).
: 
: Yes.  This started long before the SMP cleanup MFC.  I'm running 4-stable.
:
:Let me second this.  I have been unable to use moused on my laptop 
:(Sony VAIO 505TR with Versapad) since syscons changes went in right
:after 4.0-RELEASE (it worked under -RELEASE), but broke under -STABLE.
:I had a discussion with Kazutaka YOKOTA, but nothing was resolved.  
:Cut and paste were OKish on the ttyvN with a very twitchy pointer image,
:but it was completely unusable under XFree86-3.3.6 that shipped with 
:-RELEASE (not sure if I should rebuild X or not).  I have been running
:sans moused ever since (so it is not hardware related in my case).
:
:S
:---
:Sean O'ConnellEmail: [EMAIL PROTECTED]

Ok, at least it wasn't me :-)  That's all I care about, bye! .. heh heh,
just kidding.  It seems that people are homing in on the problem being
syscons, that's two so far.  Is there any further corroboration?

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread VINSON WAYNE HOWARD

I stopped using moused sometime during 4.0-current as a result of this.
It ocasionally froze, moved randomly around the screen, clicked without
being touched, and yes, got extreamly jumpy.  The hardware's rock solid,
and once I ditched moused and read the device directly, life went back to
normal.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Kenneth Wayne Culver

I saw it once or twice in the last couple of weeks, when I'm kicking the
hell out of the CPU (ie compiling something)


=
| Kenneth Culver  | FreeBSD: The best OS around.|
| Unix Systems Administrator  | ICQ #: 24767726 |
| and student at The  | AIM: muythaibxr |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.   | http://www.wam.umd.edu/~culverk/|
=

On Sun, 21 May 2000, Jordan K. Hubbard wrote:

 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 != ).
 
 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 [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jordan K. Hubbard

 Unless your mouse died of old age.  The PS/2 mouse I had been using for
 quite some time started to behave exactly like yours at some point last
 year.  I avoided replacing it for a long time, since I couldn't find another
 mouse with a long enough cord.

I tried several other mice.  It's a software problem. :)

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread Jordan K. Hubbard

 I don't know if the mouse problems are related or not, did anyone have
 jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
 kernels then two weeks old for 4.0, and four weeks old for 5.0).

I did not have jumpy-mouse problems on my SMP system (probably should
have mentioned it was an SMP desktop box) before those patches, now
that you mention it!  Thanks for helping to narrow it down.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-22 Thread VINSON WAYNE HOWARD

While it's nice to supposedly have narowed this down to the SMP cleanup,
that doesn't make those of us who are running single processor machines
very cofident that the bug's been found.  Here's my guess: there may be
something interupt driven related to the SMP stuff, but there's also
something wrong with moused, as at least two people (one being myself)
have said that going to direct reading of the device eliminted their
problem.  I just didn't want the legitimate bug reports from single
processor users to be lost in the search for a SMP cause.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Frank Mayhar

Jordan K. Hubbard wrote:
 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 != ).
 
 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?

I haven't seen this message, but I _have_ been seeing an off-and-on problem
where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
causes clicks, wild pointer motion, all sorts of stuff.  I usually have to
log in from another box and kill and restart moused; that fixes things.
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Jordan K. Hubbard

 I haven't seen this message, but I _have_ been seeing an off-and-on problem
 where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
 causes clicks, wild pointer motion, all sorts of stuff.  I usually have to

FWIW, those are all the symptoms of this problem too.  The mouse
doesn't just jump, it goes nuts with simulated button events. :)

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Warner Losh

In message 3970.958963729@localhost "Jordan K. Hubbard" writes:
: 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 != ).
: 
: 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?

I see this from time to time on whacked out mice that come into my
posession.  Sadly, I see it most on my laptop.  It seems to happen
less offten when I have
PSM_HOOKRESUME
PSM_RESETAFTERSUSPEND
defined in my kernel config file.

I've also seen this when I've tried to hot plug mice.  This includes
when power is lost to my KVM switch.  When that happens, I gotta
reboot all the machines that are attached to it since something is
whacko at that point, I get those messages, or worse no mice and no
message at all.

I know one isn't supposed to hot plug mice, but there are times when
one is using a KVM switch when it sure would be nice to reset the
driver.  Hmmm, there's a psmdetach.  Is there anyway to force a device
to be detached?  I know unloading the driver will do it, but one can't
unload the driver compiled into the kernel, can one?  And even if you
could, I'd run the risk of loading a driver that doesn't match my
kernel.

Hmmm, time for a good ioctl interface to newbus :-)

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: Anyone else seeing jumpy mice?

2000-05-21 Thread Jonathan Hanna


On 22-May-00 Jordan K. Hubbard wrote:
 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 != ).
 
 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?
 

Yes, recently on 4.0-stable, though provoked by unplugging and
replugging in the mouse. It did not recover. This I thought
sounded like a PR on the mouse being dead after a wakeup
from sleep mode.

Jonathan Hanna [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Frank Mayhar

Jonathan Hanna wrote:
 Yes, recently on 4.0-stable, though provoked by unplugging and
 replugging in the mouse. It did not recover. This I thought
 sounded like a PR on the mouse being dead after a wakeup
 from sleep mode.

Come to think of it, I do use a KVM switch, but this usually happens after
I've been hacking away a while, having not touched the switch in hours or
days.  Still, it could be related, I guess.
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Brian Hechinger

Jonathan Hanna drunkenly mumbled...
 
  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?
 
 Yes, recently on 4.0-stable, though provoked by unplugging and
 replugging in the mouse. It did not recover. This I thought
 sounded like a PR on the mouse being dead after a wakeup
 from sleep mode.

sometimes the people who clean our office move my computer to vacuum the floor
and somehow they always manage to knock the mouse plug out.  i try everything
i can think of, but the only way to make the mouse start working again is to
reboot.  this is 4.0-stable, and it used to happen with 3.4-stable before i
upgraded as well so i don't think this is version specific, it is something in
the psm driver than hasn't changed in a while.

-brian


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA


May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).

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?

Do you, by any chance, use a KVM?

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA


: May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
: 
: 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?

I see this from time to time on whacked out mice that come into my
posession.  Sadly, I see it most on my laptop.  It seems to happen
less offten when I have
   PSM_HOOKRESUME
   PSM_RESETAFTERSUSPEND
defined in my kernel config file.

I've also seen this when I've tried to hot plug mice.  This includes
when power is lost to my KVM switch.  When that happens, I gotta
reboot all the machines that are attached to it since something is
whacko at that point, I get those messages, or worse no mice and no
message at all.

When power to the mouse is, either accidentally or intentionally, cut,
the internal setting of the mouse is naturally lost, and the mouse may
behave in a different way than the way the psm driver assumes...

Hmmm, time for a good ioctl interface to newbus :-)

Or, an ioctl to reset the mouse...  I have long rejected this idea
because it will only encourage people to detach and attach the PS/2
mouse, which is generally not capable of hot plug/unplug.

But, there now are so many dumb KVMs which screw us, and we may have
to accept that...

Kazu




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA


 May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
 
 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?

I haven't seen this message, but I _have_ been seeing an off-and-on problem
where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
causes clicks, wild pointer motion, all sorts of stuff.  I usually have to
log in from another box and kill and restart moused; that fixes things.

Um, if you don't see the above message but see erratic mouse
behavior, then there may be a configuration problem (for moused or
X), or a hardware problem.

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA

 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?

Yes, recently on 4.0-stable, though provoked by unplugging and
replugging in the mouse. It did not recover. This I thought
sounded like a PR on the mouse being dead after a wakeup
from sleep mode.

Please, if you can avoid it, don't unplug and replug the mouse while
the power is on.  The PS/2 mouse interface is generally not capable
of hot plugging/unplugging.

As for sleep/wake-up problem on the laptop computers, you may
be able to resolve the problem by adding the following kernel options.

options PSM_HOOKRESUME
options PSM_RESETAFTERSUSPEND

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Mike Smith

 I haven't seen this message, but I _have_ been seeing an off-and-on problem
 where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
 causes clicks, wild pointer motion, all sorts of stuff.  I usually have to
 log in from another box and kill and restart moused; that fixes things.
 
 Um, if you don't see the above message but see erratic mouse
 behavior, then there may be a configuration problem (for moused or
 X), or a hardware problem.

You can also get this if you have moused running but have configured X to 
point to the physical mouse device rather than /dev/sysmouse.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Warner Losh

In message [EMAIL PROTECTED] Kazutaka YOKOTA 
writes:
: But, there now are so many dumb KVMs which screw us, and we may have
: to accept that...

Yes.  I've been cursed to use some of the dumb KVMs at work.  It got
so bad that I've connected my mouse directly to the main machine and
not run X on the other machines.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Frank Mayhar

Mike Smith wrote:
  I haven't seen this message, but I _have_ been seeing an off-and-on problem
  where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
  causes clicks, wild pointer motion, all sorts of stuff.  I usually have to
  log in from another box and kill and restart moused; that fixes things.
  
  Um, if you don't see the above message but see erratic mouse
  behavior, then there may be a configuration problem (for moused or
  X), or a hardware problem.

Well, the mouse is fairly new (less than 6 months) and otherwise works like
a charm.  I never saw this before 4.0, but that was also about the time
I added the KVM.

 You can also get this if you have moused running but have configured X to 
 point to the physical mouse device rather than /dev/sysmouse.

Nope.
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Wes Peters

"Jordan K. Hubbard" wrote:
 
  I haven't seen this message, but I _have_ been seeing an off-and-on problem
  where my PS/2 (Logitech Firstmouse) mouse will go insane.  Just moving it
  causes clicks, wild pointer motion, all sorts of stuff.  I usually have to
 
 FWIW, those are all the symptoms of this problem too.  The mouse
 doesn't just jump, it goes nuts with simulated button events. :)

This can really suck with certain email clients, too.

My hardware: Sony VAIO PCG-F160 w/integrated trackpad:

psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA

  Um, if you don't see the above message but see erratic mouse
  behavior, then there may be a configuration problem (for moused or
  X), or a hardware problem.

Well, the mouse is fairly new (less than 6 months) and otherwise works like
a charm.  I never saw this before 4.0, but that was also about the time
I added the KVM.

Oh, I see. You also use a KVM.  The psm driver in FreeBSD versions
before 4.0 is also screwed when a less-than-compatible KVM is used.

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-21 Thread Kazutaka YOKOTA


 FWIW, those are all the symptoms of this problem too.  The mouse
 doesn't just jump, it goes nuts with simulated button events. :)

This can really suck with certain email clients, too.

My hardware: Sony VAIO PCG-F160 w/integrated trackpad:

   psm0: PS/2 Mouse irq 12 on atkbdc0
   psm0: model GlidePoint, device ID 0

Don't the following kernel options work for this machine?

options PSM_HOOKRESUME
options PSM_RESETAFTERSUSPEND

Kazu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message