linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* mouse bug
@ 2007-11-30 14:06 Roel Kluin
  2007-11-30 14:25 ` Andre Haupt
  0 siblings, 1 reply; 3+ messages in thread
From: Roel Kluin @ 2007-11-30 14:06 UTC (permalink / raw)
  To: linux-input

Once in every so often boots I end up in X without a functioning mouse. A
pointer is shown, but glued to the center of the screen. A reboot will fix it,
but I have had this behavior for a few years now and still no clue what the
origin of the problem is - dmesg reports as it does normally:

PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
mice: PS/2 mouse device common for all mice

killing and restarting X and/or gpm doesn't return control over the mouse.

I have been storing dmesgs at failures:
2007-08-29
2007-09-15
2007-11-23
(I boot twice a day on average)

As you can see, I had one recently. This time I also made a copy of my /proc
and /sys directories. (I am guessing /proc was not really needed) maybe any info
can still be extracted?

Where can I look, what can I do to find the source of this problem? Is there
anything that I should do to obtain more info when this occurs nexttime?

Thanks

Roel



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: mouse bug
  2007-11-30 14:06 mouse bug Roel Kluin
@ 2007-11-30 14:25 ` Andre Haupt
  2007-11-30 14:45   ` Roel Kluin
  0 siblings, 1 reply; 3+ messages in thread
From: Andre Haupt @ 2007-11-30 14:25 UTC (permalink / raw)
  To: Roel Kluin; +Cc: linux-input

On Fri, Nov 30, 2007 at 03:06:27PM +0100, Roel Kluin wrote:
> Once in every so often boots I end up in X without a functioning mouse. A
> pointer is shown, but glued to the center of the screen. A reboot will fix it,
> but I have had this behavior for a few years now and still no clue what the
> origin of the problem is - dmesg reports as it does normally:
> 
> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
> mice: PS/2 mouse device common for all mice
> 
> killing and restarting X and/or gpm doesn't return control over the mouse.
> 
> I have been storing dmesgs at failures:
> 2007-08-29
> 2007-09-15
> 2007-11-23
> (I boot twice a day on average)
> 
> As you can see, I had one recently. This time I also made a copy of my /proc
> and /sys directories. (I am guessing /proc was not really needed) maybe any info
> can still be extracted?
> 
> Where can I look, what can I do to find the source of this problem? Is there
> anything that I should do to obtain more info when this occurs nexttime?

does cat /dev/input/mice work (i.e. shows weird characters)?

regards,

Andre

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: mouse bug
  2007-11-30 14:25 ` Andre Haupt
@ 2007-11-30 14:45   ` Roel Kluin
  0 siblings, 0 replies; 3+ messages in thread
From: Roel Kluin @ 2007-11-30 14:45 UTC (permalink / raw)
  To: Andre Haupt; +Cc: linux-input

Andre Haupt wrote:
> On Fri, Nov 30, 2007 at 03:06:27PM +0100, Roel Kluin wrote:
>
> does cat /dev/input/mice work (i.e. shows weird characters)?
> 
> regards,
> 
> Andre

Actually it did. Note that the problem is not here now, but back then I
did a cat /dev/mouse (which is a symlink to /dev/input/mice) and it did
echo strange characters.

Roel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-11-30 14:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-30 14:06 mouse bug Roel Kluin
2007-11-30 14:25 ` Andre Haupt
2007-11-30 14:45   ` Roel Kluin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).