public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Cc: joeja@mindspring.com, Dave Jones <davej@suse.de>
Subject: Re: AMD thunderbird oops
Date: Thu, 28 Jun 2001 13:33:42 -0700	[thread overview]
Message-ID: <3B3B94A6.455C3834@bigfoot.com> (raw)
In-Reply-To: <Springmail.105.993672371.0.48374000@www.springmail.com>

joeja@mindspring.com wrote:
> 
> Well considering the other night the power supply went dead, I think that is part of the problem.  It is brand new, and I am being sent another one (free of course).
> 
> I also had my mb loaded at the time (scsi cd-rw, cdrom, internal zip, floppy, 1 hd, Sound card, video, modem, NIC, scsi card) but my last tyan was fine with that load it may be a kt7a thing.
> 
> Several people said that random (keyword here) oopses are more often a hardware thing.  I wonder if the kt7a is going to be able to perform  fully loaded..
> 
> is anyone running one fully loaded? 4 ide drives, 2 floppy, (5 pci and 1 isa) or 6pci, agp, 512MEG+ RAM?
> 
> Joe

Similar board (KA7) had non-heat related lockups with 133MHz FSB (1756
BogoM).  100MHz FSB + 4 way interleave has been fast and stable (1690
BogoM).

/dev/hda:
 Timing buffer-cache reads:   128 MB in  1.00 seconds =128.00 MB/sec

Abit KA7 (VT82C686a, rev 22), Athlon 850, 2x256MB PC133@CL2, 2 ide,
CR-RW, Colorado Travan, linux 2.2.20p6+ide.2.2.19.04092001, SPI 300W
power, PCI: Firewire, Netgear FA310TX, Turtle Beach Santa Cruz audio,
AGP: 32MB TNT2.

CONFIG_M686=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_1GB=y
CONFIG_MTRR=y

--

  parent reply	other threads:[~2001-06-28 20:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 20:06 Re: AMD thunderbird oops joeja
2001-06-27 20:53 ` Luigi Genoni
2001-06-28 20:33 ` Tim Moore [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-26 14:06 Alex Deucher
2001-06-26 15:07 ` Alan Cox
2001-06-26 15:26   ` Alex Deucher
2001-06-26 15:33     ` Alan Cox
2001-06-26 15:52       ` Dave Jones
2001-06-28 12:55     ` Pierre Etchemaite
2001-06-28 19:57       ` Tim Moore
2001-07-01 11:06         ` Pierre Etchemaite
2001-06-26 13:22 Thomas Foerster
2001-06-26 13:45 ` Alan Cox
2001-06-26  8:26 Thomas Foerster
2001-06-26  9:09 ` Luigi Genoni
2001-06-25 16:24 joeja
2001-06-25 16:35 ` Keith Owens
2001-06-25  3:17 joeja
2001-06-25  6:55 ` Alan Cox
2001-06-25  7:05   ` Alexander V. Bilichenko
2001-06-25 20:33   ` Dan Hollis
2001-06-26  7:39   ` Thomas Kotzian
2001-06-25  9:40 ` Luigi Genoni

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=3B3B94A6.455C3834@bigfoot.com \
    --to=timothymoore@bigfoot.com \
    --cc=davej@suse.de \
    --cc=joeja@mindspring.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