Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 2003 21:14:56 -0000
From:      "Cameron Murdoch" <cmurdoch@bprarchitects.com>
To:        <freebsd-current@freebsd.org>
Subject:   psmintr: out of sync
Message-ID:  <98D8849D7BBCEF44B063404DCD267EC61C58@zulu.bprarchitects.com>

next in thread | raw e-mail | index | archive | help

Hi,

Not sure what happened to the original message, sorry for the noise!

I am running a recent current:

FreeBSD opal.macaroon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 26 16:18:16 GMT 2003 root@opal.macaroon.net:/usr/obj/usr/src/sys/GENERIC i386

The machine is a Dell Inspiron 4000 laptop. It is running XFree86-4.3.0 It has both a trackpad and a pointing stick (?what is the real name for this, I always call them nipples?), and it is seems to be the mouse I am having a problem.

Every now and again, but with great regularity the screen will freeze up, so that nothing works, not even the caps lock light. However, it isn't a crash as leaving the machine alone for a random amount of time will normally fix it. Sometimes this delay is a matter of seconds, other times I have left if for about 20+mins. Interestingly enough, pinging the laptop from another computer will always unfreeze it immediately.

As this occurs the following is printed to the console:

Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != 0000).
Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1).

The above appears for each freeze, and every now and again this appears:

Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != 0000).
Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1).
Mar 27 11:23:58 opal kernel: psmintr: out of sync (0040 != 0000).
Mar 27 11:23:58 opal kernel: psmintr: discard a byte (2).
Mar 27 11:23:58 opal kernel: psmintr: out of sync (00c0 != 0000).
Mar 27 11:23:58 opal kernel: psmintr: re-enable the mouse.

When the re-enable the mouse message happens then the pointing stick stops working and only the trackpad functions.

This started happening with 5-RELEASE though not when -RELEASE was first installed. I am not sure what has caused it.

Probably completely unrelated but the below appears on boot up, (GENERIC kernel - ie, WITNESS and INVARIANTS)
  

pci0: <bridge, PCI-unknown> at device 7.3 (no driver attached)
pcm0: <ESS Technology Maestro3> port 0xc800-0xc8ff mem 0xf9ffe000-0xf9ffffff irq 5 at device 8.0 on pci0
pcm0: <SigmaTel STAC9721/23 AC97 Codec>
malloc() of "64" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "64" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
malloc() of "16" with the following non-sleepablelocks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322
pcib2: <PCI-PCI bridge> at device 16.0 on pci0

Thanks a lot!
-- 
Cameron Murdoch <cmurdoch@bprarchitects.com> 


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