public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <dis@sigkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Moses Mcknight <moses@texoma.net>, linux-kernel@vger.kernel.org
Subject: Re: Problem with k7 optimizations in 2.4.x?
Date: Fri, 13 Apr 2001 11:39:52 -0400	[thread overview]
Message-ID: <20010413113952.F21462@sigkill.net> (raw)
In-Reply-To: <3AD706C4.8020705@texoma.net> <E14o5Wc-000336-00@the-village.bc.nu>
In-Reply-To: <E14o5Wc-000336-00@the-village.bc.nu>

On the iwill mobo? (I haven't heard of this problem on other
motherboards.)

I'll grab the latest -ac today and give it a try this evening. 

(Just for reference, the system is the Iwill kk266, 1.2G tbird, 512M
pc133, ata66 drive - everything has AMD-approved stickers and nothing is
overclocked.)

On Fri, 13 Apr 2001, Alan Cox did have cause to say:

> > settings or what, but whenever I try to run a 2.4.x kernel on my machine 
> > with k7 optimizations the computer will never fully boot and seems to 
> > give random errors about being "unable to handle kernel NULL pointer 
> > dereference at virtual address xxxxxxxx" and other errors.
> 
> I run the K7 optimisations in 2.4.x-ac built with gcc 2.96-69 or later with no
> problems. I've not tested them with egcs-1.1.2. The earlier 2.4.* had problems
> on later Athlons which have both fxsave and movntq/sfence. That was fixed a 
> while back tho
> 
> -
> 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/
---
   _.-=<Disconnect>=-._
|     dis@sigkill.net    | And Remember...
\  shawn@healthcite.com  / He who controls Purple controls the Universe..
 PGP Key given on Request  Or at least the Purple parts!

-----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-13 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 14:01 Problem with k7 optimizations in 2.4.x? Moses Mcknight
2001-04-13 14:27 ` Disconnect
2001-04-13 15:30 ` Alan Cox
2001-04-13 15:39   ` Disconnect [this message]
2001-04-13 16:10     ` Alan Cox
2001-04-15  3:48       ` Disconnect

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=20010413113952.F21462@sigkill.net \
    --to=dis@sigkill.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moses@texoma.net \
    /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