mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jorge Carminati <jcarminati@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel freezing....
Date: Thu, 6 Dec 2001 05:11:38 -0800 (PST)	[thread overview]
Message-ID: <20011206131138.81573.qmail@web13905.mail.yahoo.com> (raw)
In-Reply-To: <3C0EDAEE.6080608@wanadoo.fr>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1487 bytes --]

François Wrote:

> okay, I kinda see the problem now. Would you consider using a
> 2.4.16 kernel, optimized for i386, and compiled with gcc 2.95.3 ?
> If that solves the problem, you might want
> to compile your kernel for i586 ; if that works
> again, you might want to try optimizing for K6.
> Don't go higher than that though ; optimizing for i686 or
> Athlon will break.
> And please don't use another gcc ; 2.95.3 is the most reliable
> right now, eventhough "some" 2.96 seem to work fine, but I suspect
> they might not, in your case.


Ok François, I´ll try it tonight, first attempt compiled for i386.
Tomorrow I´ll post the results.


> 
> the key is :
> 
> (duron or athlon) and via and (PSU sloppiness or "not so high grade"
> RAM),
> 
> which is the case in too many notebooks.
> 

Ok, you spend U$ 1800 (that´s the price here) for a "not so high grade"
Compaq memory... sounds lamentable

>PS : please, please keep me informed, I think I'm uncovering an
unknown

Sure I´ll do.

>bug at the hardware level, but I'm not sure *yet*. FYI it's not a
>blocking problem, at least when running Linux, it only keeps you
>from using the Athlon/Duron at full speed (i.e. full kernel/compiler
>optimizations).


Anyway, I installed a fresh Red Hat 7.2 copy, which doesn´t comes
optimized for AMD, but the freeze is there...

Regards,
Jorge Carminati.

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

       reply	other threads:[~2001-12-06 13:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C0EDAEE.6080608@wanadoo.fr>
2001-12-06 13:11 ` Jorge Carminati [this message]
     [not found] <3C11096E.9040102@wanadoo.fr>
2001-12-07 19:23 ` Jorge Carminati
2001-12-07 13:30 Jorge Carminati
2001-12-07 13:51 ` Alan Cox
2001-12-07 15:03   ` Jorge Carminati
  -- strict thread matches above, loose matches on Subject: below --
2001-12-06 14:16 Jorge Carminati
2001-12-06 14:35 ` Alan Cox
2001-12-06 14:45   ` Jorge Carminati
2001-12-06 14:04 Jorge Carminati
     [not found] <E16Buao-00010V-00@the-village.bc.nu>
2001-12-06 13:17 ` Jorge Carminati
2001-12-06  2:20 Jorge Carminati
2001-12-06  6:49 ` Jaswinder Singh
2001-12-06 13:13   ` Jorge Carminati
2001-12-06  8:12 ` jcassidy
2001-12-06 12:57   ` Jorge Carminati
2001-12-07 17:34   ` Pavel Machek
2001-12-08 21:12     ` Mike Castle
2001-12-08 23:21     ` jcassidy

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=20011206131138.81573.qmail@web13905.mail.yahoo.com \
    --to=jcarminati@yahoo.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

all inboxes | Powered by JetHome®