From: Tim Timmerman <Tim.Timmerman@asml.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG with 2.4.5
Date: Fri, 29 Jun 2001 07:29:06 +0200 [thread overview]
Message-ID: <15164.4642.621532.532854@asml.nl> (raw)
In-Reply-To: <3B397659.816CF0A3@uow.edu.au>
In-Reply-To: <Pine.LNX.4.21.0106261924220.10865-100000@schoen3.schoen.nl> <15161.28095.801407.427346@asml.nl> <3B397659.816CF0A3@uow.edu.au>
>>>>> "Andrew" == Andrew Morton <andrewm@uow.edu.au> writes:
Andrew> Tim Timmerman wrote:
>>
>> >>>>> "kees" == kees <kees@schoen.nl> writes:
>>
kees> Hi,
>>
kees> I tried 2.4.5 but after a couple of hours I lost all network
kees> connectivety. The log shows:
>> <snip>
>> Can I just add a me too here ?
>>
>> System: Abit BP6, Dual Celeron, Ne2k-pci, usb ohci and
>> scanner; 128 Mb Ram, Nvidia TNT2 graphics. Kernel 2.4.5
<snip>
Andrew> Probable fixes include booting with the `noapic' option,
Andrew> running -ac kernels or applying Maciej's APIC workaround
Andrew> patch. There's a copy at http://www.uow.edu.au/~andrewm/linux/apic.txt
Andrew> -
Didn't check the patch, but went straight for 2.4.5-ac20... No hangs,
and better performance than before.
TimT.
--
tim.timmerman@asml.nl 040-2683613
timt@timt.org Voodoo Programmer/Keeper of the Rubber Chicken
Whatever happened to preparations A through G?
next prev parent reply other threads:[~2001-06-29 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 17:28 NETDEV WATCHDOG with 2.4.5 kees
2001-06-27 5:23 ` Tim Timmerman
2001-06-27 5:59 ` Andrew Morton
2001-06-27 15:44 ` kees
2001-06-27 15:57 ` Andrew Morton
2001-06-28 5:26 ` Tim Timmerman
2001-06-29 5:29 ` Tim Timmerman [this message]
2001-06-28 12:52 ` rc
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 4:58 G. Hugh Song
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=15164.4642.621532.532854@asml.nl \
--to=tim.timmerman@asml.com \
--cc=andrewm@uow.edu.au \
--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