public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Bonin <kernel@bonin.ca>
To: Chris Fuller <cfuller@broadjump.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tyan S2464 (K7 SMP) + EMU10K1 hardlocks
Date: Fri, 07 Jun 2002 13:44:39 -0400	[thread overview]
Message-ID: <3D00F107.8070402@bonin.ca> (raw)
In-Reply-To: <97B71B827DFB2B448A73EC00E5DA0EE605E04A@logos.inhouse.broadjump.com>

Chris Fuller wrote:
> I've established by now that the problem is definitely not with the
> Linux kernel, but there was a discussion here about this very issue last
> August, and I haven't found a reference to it anywhere else, so please
> help if you can. :)
> 
> I'm seeing hardlocks in various 2.4 kernels (10, 18, 19-pre8, all SMP):
>   mobo=Tyan S2464 (K7 Thunderbird) SMP
>   NVidia GeForce4 AGP
>   SBLive! Platinum 5.1
>   Two 40G IDE hard drives

Creative Labs warns that it's sblive series of cards aren't compatible 
with SMP systems.  Though i've had the S2460 motherboard and the only 
trouble i have had was that EAX didn't work properly.  A friend of mine 
has an sblive with a dual celeron and he also has had this problem of 
deadlocks with the SBLive.  The audigy however is fully compatible.


Also, make sure you have an adequate power supply.

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 




  parent reply	other threads:[~2002-06-07 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 17:10 Tyan S2464 (K7 SMP) + EMU10K1 hardlocks Chris Fuller
2002-06-07 17:37 ` Adam Trilling
2002-06-07 17:44 ` Andre Bonin [this message]
2002-06-07 18:52   ` Alan Cox
2002-06-07 19:16     ` Andre Bonin

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=3D00F107.8070402@bonin.ca \
    --to=kernel@bonin.ca \
    --cc=cfuller@broadjump.com \
    --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