From: "Gábor Lénárt" <lgb@lgb.hu>
To: linux-kernel@vger.kernel.org
Subject: Re: Re[2]: [PATCH] Athlon bug stomper. Pls apply.
Date: Fri, 21 Sep 2001 17:49:55 +0200 [thread overview]
Message-ID: <20010921174955.D16173@vega.digitel2002.hu> (raw)
In-Reply-To: <3E975341CB7@vcnet.vc.cvut.cz>
In-Reply-To: <3E975341CB7@vcnet.vc.cvut.cz>
BTW ...
When I switched to Duron with a new (well, it was my friend's) motherboard
(according to lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)),
I can't boot Linux anymore since it stucked around partiotion checking (sorry
I don't remember, but I can check on the next week). It was kernel 2.2.19.
2.4.x works without any problem, the last kernel I've checked (and using now)
is 2.4.9. Is it the same problem?
On Wed, Sep 19, 2001 at 04:59:09PM +0000, Petr Vandrovec wrote:
> On 19 Sep 01 at 17:31, Liakakis Kostas wrote:
> >
> > It seems to fix the stability problem. We don;t know why, but
> > experimetation shows that those _with_ the problem are relieved. This is
> > fine! We are happy with it.
> >
> > We write to a register marked as "don't write" by Via. This is potentialy
> > dangerous in ways we don't know yet.
>
> Just small question - you are saying that your KT133A works fine with
> 0x89... Two questions then - Do you have more than 256MB in your box?
> And second one: Do you have one, two, or three memory modules installed
> on the board?
>
> If your answer is <=256MB, one module, no surprise then, as AFAIK nobody
> with such config suffers from the problem. But checking also number of
> memory modules looks more like black magic that anything else.
> Hopefully VIA will answer...
> Thanks,
> Petr Vandrovec
> vandrove@vc.cvut.cz
>
> -
> 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/
--
--[ Gábor Lénárt ]---[ Vivendi Telecom Hungary ]---------[ lgb@lgb.hu ]--
U have 8 bit comp or chip of them and it's unused or to be sold? Call me!
-------[ +36 30 2270823 ]------> LGB <-----[ Linux/UNIX/8bit 4ever ]-----
next prev parent reply other threads:[~2001-09-21 15:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 16:59 Petr Vandrovec
2001-09-19 15:03 ` Liakakis Kostas
2001-09-19 15:14 ` Gergely Tamas
2001-09-19 23:08 ` Luigi Genoni
2001-09-19 23:07 ` Luigi Genoni
2001-09-20 6:57 ` john slee
2001-09-21 15:49 ` Gábor Lénárt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-19 20:57 Petr Vandrovec
2001-09-18 21:39 Liakakis Kostas
2001-09-19 13:08 ` Re[2]: " VDA
2001-09-19 13:41 ` Liakakis Kostas
2001-09-19 13:47 ` Thomas Langås
2001-09-19 14:31 ` Liakakis Kostas
2001-09-19 14:55 ` Jan Niehusmann
2001-09-19 14:57 ` Liakakis Kostas
2001-09-19 18:12 ` Alan Cox
2001-09-19 16:00 ` Linus Torvalds
2001-09-19 17:15 ` safemode
2001-09-19 23:41 ` Nicholas Knight
2001-09-20 15:10 ` Marek Mentel
2001-09-19 18:43 ` Dan Hollis
2001-09-19 18:58 ` Roberto Jung Drebes
2001-09-21 0:46 ` Pavel Machek
2001-09-20 0:19 ` Nicholas Knight
2001-09-20 9:54 ` Liakakis Kostas
2001-09-19 23:04 ` Luigi Genoni
2001-09-19 14:05 ` Tom Diehl
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=20010921174955.D16173@vega.digitel2002.hu \
--to=lgb@lgb.hu \
--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®