From: Oleg Drokin <green@linuxhacker.ru>
To: Brent Cook <busterb@mail.utexas.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mouse interrupts: the death knell of a VP6
Date: Thu, 11 Apr 2002 00:55:04 +0400 [thread overview]
Message-ID: <20020411005504.A17409@linuxhacker.ru> (raw)
In-Reply-To: <20020410192339.A22777@namesys.com> <20020410112810.L60900-100000@ozma.union.utexas.edu>
Hello!
On Wed, Apr 10, 2002 at 11:43:13AM -0500, Brent Cook wrote:
> > > I have already tried removing memory, adding memory, changing processors,
> > > video cards. The only thing that has remained constant is the VP6
> > > motherboard and the hard drive.
> > My VP6 died on me recently with some funny symptoms:
> > it hangs in X when I start netscape and move mouse, or if I do
> > bk clone on kernel tree, it dies with
> > kernel BUG at /usr/src/linux-2.4.18/include/asm/smplock.h:62!
> Very interesting. I could do the same thing, and have a similar lock with
> a PS/2 mouse. I will start looking in smplock.h if the MPS change does not
> help.
No need to look there.
If you see sch a BUG message in your logs, you seems to have bad hardware.
> > BUG in various places pretty soon.
> > (this BUG is only appears if 2 CPUs are present in motherboard).
> > So if your troubles began only recently, you might want to try another
> > motherboard just to be sure.
> I received the motherboard used, so I do not know if this is a recent
> development. I have tried several other kernels which all show the same
> locking behavior with PS/2 mice (2.4.17, 2.4.18, 2.5.7-dj3.) The previous
> owner ran Windows XP (developer preview) on the board, and it had a
> tendency to lock often, especially under high IO. I attributed this to
> software issues, though now I wonder why the previous owner _really_ gave
> it to me!
Yeah, Windows crashed on me too (win2k, though) when I tried.
Luckily I bought my as a new one 11 months ago and I still have 1 month of
warranty, and the good thing is my board will be replaced tomorrow ;)
> I have used a Tyan Tiger 100 with two processors and an Intel BX chipset,
> with great success and no similar locks, so I am 50% certain that a
> hardware difference is the root cause of the problem. Hopefully, someone
> else will have seen similar problems.
Who knows. May be people in question silently replaced damaged harware with
good one and forgot about it already ;)
Or may be they ustill use windows and blame Microsoft on all the crashes ;)
Bye,
Oleg
next prev parent reply other threads:[~2002-04-10 16:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 3:52 Fix for duplicate /proc entries Brent Cook
2002-02-06 18:11 ` Dave Jones
2002-02-07 21:38 ` Brent Cook
2002-02-07 21:45 ` Dave Jones
2002-02-08 16:13 ` Brent Cook
2002-02-08 17:47 ` Mike Fedyk
2002-02-08 17:54 ` Alexander Viro
2002-02-08 18:12 ` Tommy Reynolds
2002-06-14 22:30 ` File permission problem with NFSv3 and 2.5.20-dj4 Brent Cook
2002-06-15 12:23 ` Dave Jones
2002-06-19 17:45 ` Brent Cook
2002-06-19 17:48 ` Dave Jones
2002-06-19 17:52 ` another sched.c error with athlon Kirk Reiser
2002-06-19 18:27 ` Adrian Bunk
2002-04-10 14:02 ` Mouse interrupts: the death knell of a VP6 Brent Cook
2002-04-10 15:23 ` Oleg Drokin
2002-04-10 16:43 ` Brent Cook
2002-04-10 16:49 ` William Park
2002-04-11 6:39 ` john slee
2002-04-10 20:55 ` Oleg Drokin [this message]
2002-04-10 17:16 ` John Adams
2002-04-10 17:52 ` Brent Cook
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 9:33 Elgar, Jeremy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020411005504.A17409@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=busterb@mail.utexas.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox