From: Wade Hampton <whampton@staffnet.com>
To: Carsten Langgaard <carstenl@mips.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pcnet32 (maybe more) hosed in 2.4.3
Date: Wed, 04 Apr 2001 11:24:21 -0400 [thread overview]
Message-ID: <3ACB3CA5.D978EF41@staffnet.com> (raw)
In-Reply-To: <20010330190137.A426@indiana.edu> <Pine.LNX.4.30.0103311541300.406-100000@fs131-224.f-secure.com> <20010403202127.A316@bacchus.dhis.org> <3ACB2323.C1653236@mips.com>
Carsten Langgaard wrote:
>
> I'm not sure what the problem is, but the whole deal about checking whether the
> controller runs in 16 bit or 32 bit mode, is a little bit tricky.
>[snip]
Without the changes listed in this thread, 2.4.3 crashed vmware 2.0.3
Linux. It did not OOPS the kernel, it caused vmware to go down in
flames.... Changing the code per the previous mail fixed it and
my VM now works fine. THANKS!
Is this list non-causal? The answer was posted to the list as I
was getting ready to build 2.4.3 on my VM, before I found the
problem or even had to ask the question!
Cheers,
--
W. Wade, Hampton <whampton@staffnet.com>
If Microsoft Built Cars: Every time they repainted the
lines on the road, you'd have to buy a new car.
Occasionally your car would just die for no reason, and
you'd have to restart it, but you'd just accept this.
next prev parent reply other threads:[~2001-04-04 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 0:01 pcnet32 (maybe more) hosed in 2.4.3 Scott G. Miller
2001-03-31 0:36 ` Jeff Garzik
2001-03-31 13:58 ` Szabolcs Szakacsits
2001-04-03 18:21 ` Ralf Baechle
2001-04-04 13:35 ` Carsten Langgaard
2001-04-04 15:24 ` Wade Hampton [this message]
2001-04-04 20:14 ` Petr Vandrovec
2001-04-04 21:51 ` Thomas Bogendoerfer
2001-04-04 23:22 ` Petr Vandrovec
2001-04-05 7:26 ` Carsten Langgaard
2001-04-05 7:15 ` Carsten Langgaard
[not found] ` <2001040423 <3ACC1E35.4D2F7506@mips.com>
2001-04-05 18:27 ` Petr Vandrovec
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=3ACB3CA5.D978EF41@staffnet.com \
--to=whampton@staffnet.com \
--cc=carstenl@mips.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