From: "Andy Ward" <andyw@edafio.com>
To: "Steven Walter" <srwalter@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: VIA Southbridge bug (Was: Crash on boot (2.4.5))
Date: Mon, 25 Jun 2001 14:57:39 -0500 [thread overview]
Message-ID: <3BDF3E4668AD0D49A7B0E3003B294282BC96@etmain.edafio.com> (raw)
I'd love to help out with testing (alas, my kernel coding skills aren't
up to fixing this kind of problem). Heck, if it trashes my linux
install, no biggie... I've got it ghosted to an image elsewhere...
Anyone wanting to work on this just drop me an email.
-- andyw
-----Original Message-----
From: Steven Walter [mailto:srwalter@yahoo.com]
Sent: Monday, June 25, 2001 1:33 AM
To: Andy Ward
Cc: linux-kernel@vger.kernel.org
Subject: VIA Southbridge bug (Was: Crash on boot (2.4.5))
Great, glad to here it. Who (if anyone) is still attempting to unravel
the puzzle of the Via southbridge bug? You, Andy, should try and get in
touch with them and help debug this thing, if you're up to it.
On Mon, Jun 25, 2001 at 01:17:57AM -0500, Andy Ward wrote:
> Well, I have tried your suggestion, and it works beautifully... The
> only change I made was to the cpu type (to 686), and everything *just*
> works now... Thanks, all!!!
>
> > From the look of things, you're being bitten by the VIA southbridge
> > problem. As I've gathered, its some sort of interaction with that
chip
> > and the 3DNow! fast copy routines the kernel uses.
> >
> > If you compile the kernel for a 686, does the problem go away? What
> > about 586 or lower? If so, I believe there are some people working
on
> > finding common aspects of the hardware that experience this problem,
> > though I don't remember who. You should get in contact with them,
or
> > they might get into contact with you.
> >
> > Good luck on working this out.
> > --
> > -Steven
> > In a time of universal deceit, telling the truth is a revolutionary
act.
> > -- George Orwell
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
next reply other threads:[~2001-06-25 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 19:57 Andy Ward [this message]
2001-06-25 20:27 ` David Grant
2001-06-26 9:10 ` pazke
-- strict thread matches above, loose matches on Subject: below --
2001-07-10 9:12 David Balazic
2001-06-25 19:55 Andy Ward
2001-06-25 6:17 Crash on boot (2.4.5) Andy Ward
2001-06-25 6:32 ` VIA Southbridge bug (Was: Crash on boot (2.4.5)) Steven Walter
2001-06-25 7:06 ` Alan Cox
2001-06-30 13:58 ` Pavel Machek
2001-07-08 17:37 ` Alan Cox
2001-07-09 16:48 ` Rob Landley
2001-07-10 9:17 ` Ville Herva
2001-07-10 21:24 ` Adam Sampson
2001-07-11 8:32 ` Ville Herva
2001-07-11 9:03 ` Eyal Lebedinsky
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=3BDF3E4668AD0D49A7B0E3003B294282BC96@etmain.edafio.com \
--to=andyw@edafio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srwalter@yahoo.com \
/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®