All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Wright <timw@splhi.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mainboard with Serverworks HE Chipset
Date: Thu, 18 Jan 2001 14:50:01 -0800	[thread overview]
Message-ID: <20010118145001.B7612@scutter.sequent.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0101170020001.811-100000@citd.owl.de>
In-Reply-To: <Pine.LNX.4.20.0101170020001.811-100000@citd.owl.de>; from ms@citd.de on Wed, Jan 17, 2001 at 12:33:09AM +0100

On Wed, Jan 17, 2001 at 12:33:09AM +0100, Matthias Schniedermeyer wrote:
> #include <hallo.h>
> 
> 
> 
> I got a "Tyan Thunder HE-SL"-Mainboard today, which has a "Severworks
> ServerSet III HE"-Chipset. (2xPIII 933, 2x512MB PC133 ECC-Registered
> SDRAM)
> 
> And i have one problem and one question.
> 
> First the question. I have an uptime of phenomenal 29minutes and "cat
> /proc/interrupts" tells me this
> 
> NMI:     175819     175819
> LOC:     175829     175828
> 
> Should i be worried? Or can i ignore it. With my former Mainboard NMI was
> (AFAIR) always 0.
> 
> Now my problem.
> 
> The Graphic-Card is a Geforce 2, Xfree is 4.02 (compiled under 2.2.17).
> 
> When i start X, everything is fine. When i go back to text-console and
> wait "some time" and then switch back to X the computer locks solid and i
> have to press the Big-Red Button. (Switching back to X after a "short"
> periode of time, at the text-console, works "normaly")
> 
> If anyone needs more information, i will happily provide them.
> 

You could try booting with 'nmi_watchdog=0' and see what happens.
What you describe sounds like the problem I have seen on a few boxes, and
disabling the NMI watchdog makes the huge numbers of NMIs and the system
hang go away. Still unclear why this is happening.

Tim

-- 
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-18 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16 23:33 Mainboard with Serverworks HE Chipset Matthias Schniedermeyer
2001-01-17  8:14 ` Matti Aarnio
2001-01-17 21:49   ` Matthias Schniedermeyer
2001-01-18 22:50 ` Tim Wright [this message]
2001-01-20 11:26   ` Matthias Schniedermeyer
2001-01-22 19:54     ` Tim Wright

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=20010118145001.B7612@scutter.sequent.com \
    --to=timw@splhi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@citd.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.