linux-mips
[Top] [All Lists]

Re: No mouse support for Indy in 2.5.75 ?

To: =?iso-8859-1?Q? Frank=20F=F6rstemann ?= <foerstemann@web.de>
Subject: Re: No mouse support for Indy in 2.5.75 ?
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 30 Jul 2003 13:23:07 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <200307300554.h6U5sOQ11794@mailgate5.cinetic.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <200307300554.h6U5sOQ11794@mailgate5.cinetic.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Wed, Jul 30, 2003 at 07:54:25AM +0200, =?iso-8859-1?Q? Frank=20F=F6rstemann 
?= wrote:

> Is there any additional information I can collect on these issues ?

Well, as for the PS/2 issues, you'll have to read through the code yourself,
nobody's digged into that so far.

> > mount: Exception at [<88113a38>] (88113bf0)
> > mount: Exception at [<88113a38>] (88113bf0)
> > mount: Exception at [<88113a38>] (88113bf0)

The kernel messages otoh are not sign of a kernel but an application bug.
It seems mount did pass bad addresses to the kernel through some syscall;
these messages are the sign of the normal mechanism to intercept bad
address arguments to syscall kicking in.  You won't get those messages
anymore in 2.6 btw.  The kernel only print's them if the second digit of
the version number is odd, see development_version in arch/mips/mm/fault.c.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>