public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon problem report summary
Date: Fri, 20 Apr 2001 20:22:35 -0400	[thread overview]
Message-ID: <20010420202235.B20176@sigkill.net> (raw)
In-Reply-To: <20010420195253.A20176@sigkill.net> <E14ql2L-0002YR-00@the-village.bc.nu>
In-Reply-To: <E14ql2L-0002YR-00@the-village.bc.nu>

On Sat, 21 Apr 2001, Alan Cox did have cause to say:

> > Addendum to 1. So far everyone (at least on LKML) who has had the
> > crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or
> > kk266r, IIRC) mobo.
> 
> Not quite all. Many have but I have other reports.

Oddness. Is it all on that same via chipset? (I have seen some reports of
the same chipset working on other mobos.)

> As far as I can tell its hardware problems. The fact not a single AMD chipset
> user sees it makes me very suspicious indeed.

Fair enough - I think so as well (although slightly less so since it's
not just the iwill mobo.)

On a (possibly?) unrelated note, memtest-mmx fails immediately (prints the
version, hardlocks).  But I've seen that on a stock PIII as well, so I
don't know what that's worth.  The oops I managed to decode was in
mmx_copy_page.

Is there a way to enable everything-K7-except-MMX? (Or, for that matter,
an easy way to see what K7 does that K6 doesn't.)

---
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++ 
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5--- 
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------

  reply	other threads:[~2001-04-21  0:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fkfenov.14jqeov@ifi.uio.no>
2001-04-16 12:30 ` Athlon problem report summary Alan Cox
2001-04-16 12:33   ` Alan Cox
2001-04-16 13:17   ` Kurt Roeckx
2001-04-20 23:52   ` Disconnect
2001-04-21  0:14     ` Alan Cox
2001-04-21  0:22       ` Disconnect [this message]
2001-04-21  0:28         ` Alan Cox
2001-04-21  0:30           ` Disconnect
2001-04-21  0:34             ` Alan Cox
2001-04-21  9:27               ` Arjan van de Ven
2001-04-21 15:07               ` Disconnect
     [not found]   ` <fa.fn57bnv.nno4p4@ifi.uio.no>
2001-04-21  2:54     ` Jeff Lightfoot

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=20010420202235.B20176@sigkill.net \
    --to=lkml@sigkill.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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