public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy <heffner@darkness.net>
To: "Christian Bornträger" <linux-kernel@borntraeger.net>
Cc: kernel@llamas.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Latest on Athlon Via KT133A chipset solution?
Date: Fri, 11 May 2001 14:08:43 -0600	[thread overview]
Message-ID: <20010511140842.E26029@bletchley.darkness.net> (raw)
In-Reply-To: <E14yHQW-0001Sg-00@the-village.bc.nu> <007d01c0da4e$6f37b540$d539e195@boeblingen.de.ibm.com>
In-Reply-To: <007d01c0da4e$6f37b540$d539e195@boeblingen.de.ibm.com>; from linux-kernel@borntraeger.net on Fri, May 11, 2001 at 09:12:30PM +0200

Just tested the -ac7 with K7 optimizations on.  I see the same behavior of
oopsing right after boot:

[...]
Freeing unused kernel memory: 216k freed
Unable to handle kernel NULL pointer dereference at virtual address
00000000
[...]

Just fine when I go back down to k6-3, et al, optimizations.

Tyan S2380B VIA KT133A, amd 1.33ghz, regular stepping, no OC or anything.

If you want more info, lemme know.

Also had some USB weirdness, but I'm going to debug that a bit before I
report on it.

thx,
-jeremy

Christian Bornträger enlightened recipients with the following on 11May2001:
> > Give the current -ac a spin and tell me if it works/doesnt and if not how
> > it fails
> 
> I will test it on Sunday evening, when I get back access to my Athlon.
> 
> Again I am not sure if I had the same problem related to the
> compiler-optimizations. My problems (system freeze) started with 2.4.3-ac7.
> So the problem might related to the VIA-bug-workaround.
> 
> Is there a possibility to get debugging messages or register dumps without a
> second PC? Or is there a possibility to an unbuffered log write? e.g. write
> kernel logs to a floppy disc unbuffered. Otherwise I am not sure, if I am
> able to help you finding the problem.
> Unfortunately I have only a VIA-based Athlon system and not a S/390



  parent reply	other threads:[~2001-05-11 20:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 18:00 Latest on Athlon Via KT133A chipset solution? kernel
2001-05-11 18:14 ` Alan Cox
2001-05-11 19:12   ` Christian Bornträger
2001-05-11 19:14     ` Alan Cox
2001-05-11 20:08     ` Jeremy [this message]
2001-05-13 19:04   ` Christian Bornträger
2001-05-14 14:15   ` kernel
  -- strict thread matches above, loose matches on Subject: below --
2001-05-14  6:28 Seth Goldberg

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=20010511140842.E26029@bletchley.darkness.net \
    --to=heffner@darkness.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel@llamas.org \
    --cc=linux-kernel@borntraeger.net \
    --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