public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Holger Lubitz <h.lubitz@internet-factory.de>
To: linux-kernel@vger.kernel.org
Subject: Re: VIA KT133A Northbridge bug reported
Date: Tue, 29 May 2001 15:56:15 +0200	[thread overview]
Message-ID: <3B13AA7F.F9C0454@internet-factory.de> (raw)
In-Reply-To: <Pine.SOL.3.96.1010528204546.23787A-100000@virgo.cus.cam.ac.uk>

"Dr S.M. Huen" proclaimed:

> I saw a report on AMDZone of another VIA chipset bug.  The original source
> is:-
> http://www.chip.de/news_stories/news_stories_163106.html
> 
> The claim from AMDZone's translation is that:-
> " According to the report KT133A boards with chipset codes of 1EA0 and
> 1EA4 can have the bug which causes your computer to restart."

This seems like a translation error. The german original reads
"Eigentlich für C-Athlons ausgelegt, produziert die Northbridge VT8363A
Restart-Probleme mit genau dieser CPU." which roughly translates to
"Originally intended for C-Athlons, the Northbridge VT8363A causes
restart problems with exactly this CPU."

The original article goes on with "Wie Stephan Schwolow von MSI
Deutschland gegenüber CHIP Online mitteilte, lässt sich das Problem mit
der VIA-Northbridge anhand eines Warmstarts aus dem DOS-Modus oder einem
Windows-Neustart identifizieren: Bleibt der Bildschirm schwarz, hat der
Chip einen Fehler."

Translation: "As Stephan Schwolow from MSI Germany told Chip Online, the
problem with the VIA northbridge can be identified by a warm start from
DOS or a Windows reboot: If the screen stays black, the chip has an
error."

As far as I understand it, the problem is only affecting "warm reboots".
And I couldn't care less about warm reboots - my machines usually run
24/7 :) 

Holger

  reply	other threads:[~2001-05-29 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28 19:49 VIA KT133A Northbridge bug reported Dr S.M. Huen
2001-05-29 13:56 ` Holger Lubitz [this message]
2001-05-29 19:57   ` Joseph Carter
2001-05-29 21:13     ` {OT?]Re: " Dr S.M. Huen

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=3B13AA7F.F9C0454@internet-factory.de \
    --to=h.lubitz@internet-factory.de \
    --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