All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moses Mcknight <moses@texoma.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Athlon runtime problems
Date: Sat, 14 Apr 2001 22:25:05 -0500	[thread overview]
Message-ID: <3AD91491.1050906@texoma.net> (raw)
In-Reply-To: <E14oRie-000556-00@the-village.bc.nu>

Alan Cox wrote:

> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
> 
> -	CPU model/stepping

AMD Athlon Thunderbird 850Mhz
Stepping - 2


> -	Chipset

VIA KT133A chipset, Iwill KK266 MB.
According to a couple other people this problem may only occur on this 
motherboard.


> -	Amount of RAM

256 MB Corsair PC150


> -	/proc/mtrr output

reg: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
reg: base=0xd5000000 (3408MB), size=  16MB: write-combining, count=1


> -	compiler used

2.95.3 - Debian unstable package.


> 
> Alan

When these errors occur, I never get to a shell prompt.  Is there a way 
to save the errors or have them saved somewhere so I don't have to write 
all that stuff down?  Also, how can I set the console buffer (what is it 
called, where you can view previous screens with SHIFT + PgUP/DOWN?) to 
hold more so I don't lose some of the errors?

Thanks,
Moses



  parent reply	other threads:[~2001-04-15  3:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 15:12 Athlon runtime problems Alan Cox
2001-04-14 15:43 ` Tim lawless
2001-04-14 17:47 ` Kurt Roeckx
2001-04-14 20:14 ` Jeff Lightfoot
2001-04-15  3:25 ` Moses Mcknight [this message]
2001-04-15  3:55 ` Disconnect
2001-04-16 23:52 ` Gary White (Network Administrator)
  -- strict thread matches above, loose matches on Subject: below --
2001-04-16  8:17 David Smith
2001-04-17  5:59 Ray Shaw

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=3AD91491.1050906@texoma.net \
    --to=moses@texoma.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 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.