mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas Knight" <tegeran@home.com>
To: <linux-kernel@vger.kernel.org>
Subject: Fw: VT82C686A corruption with 2.4.x
Date: Fri, 2 Feb 2001 01:36:37 -0800	[thread overview]
Message-ID: <002101c08cfb$a3e026b0$8d19b018@c779218a> (raw)

oops, I forgot to send this to linux-kernel as well...

----- Original Message -----
From: "Nicholas Knight" <tegeran@home.com>
To: "David D.W. Downey" <pgpkeys@hislinuxbox.com>
Sent: Thursday, February 01, 2001 5:24 AM
Subject: Re: VT82C686A corruption with 2.4.x


> ----- Original Message -----
> From: "David D.W. Downey" <pgpkeys@hislinuxbox.com>
> To: "David Riley" <oscar@the-rileys.net>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Thursday, February 01, 2001 4:51 AM
> Subject: Re: VT82C686A corruption with 2.4.x
>
>
> > Yeah, I'm seriously beginning to think it's a board specific issue. If I
> > drop the RAM count down to 768MB I get far less drops in app deaths
>
> <....>
>
> >Right now I've got the full 1GB in there. What I'm seeing now is
> >application deaths, occational X11 lockups, but SUPRIZE! SUPRIZE! no more
> >drive corruptions since I removed the DMA flag from the drives, disabled
> >DMA use in the BIOS and replaced the ATA66 cable with an ATA33.
>
> (the following is a lot of conjecture and doesn't wholly fit the
information
> avalible to me on this problem, but maybe it'll help bring about other
ideas
> that will lead to a fix for this)
>
> OK, I haven't had a chance to get 2.4 up and running yet, but yesterday I
> was troubleshooting some lockup issues in Win2k and there was a slim
chance
> that it might have had to do with overheating of the chipset that controls
> the RAM on the machine; but it turned out to be something of a driver
issue.
> However this got me thinking more about heat... this *really* is sounding
> more and more like a heat problem to me... esspecialy if it might be board
> specific, since there might be something in the specific designs that
causes
> higher levels of heat.
> I *KNOW* that it seems unlikely since no other OS is exhibiting these
> problems to my knowledge (including linux 2.2.*) but what if? Could there
be
> something in 2.4 making it more sensitive to errors related to heat? Could
> 2.4 somehow be making the HDD controllers run hotter?
> Prehaps we should start collecting average system tempatures of systems
that
> display this problem, esspecialy while running 2.4.x both with and without
> DMA enabled.
>
> <end conjecture spoken by someone without enough information avalible to
> him>
>
> -NK
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2001-02-02  9:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='002101c08cfb$a3e026b0$8d19b018@c779218a' \
    --to=tegeran@home.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®