From: Ben Ford <bford@talontech.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: David Ford <david@linux.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.1-test10
Date: Tue, 23 Jan 2001 02:42:51 -0800 [thread overview]
Message-ID: <3A6D602B.E0A3BD22@talontech.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101221711560.1309-100000@penguin.transmeta.com> <3A6CF5B7.57DEDA11@linux.com> <3A6D2D54.619AFA7E@mandrakesoft.com>
Jeff Garzik wrote:
> David Ford wrote:
> >
> > Linus Torvalds wrote:
> >
> > > The ChangeLog may not be 100% complete. The physically big things are the
> > > PPC and ACPI updates, even if most people won't notice.
> > >
> > > Linus
> > >
> > > ----
> > >
> > > pre10:
> > > - got a few too-new R128 #defines in the Radeon merge. Fix.
> > > - tulip driver update from Jeff Garzik
> > > - more cpq and DAC elevator fixes from Jens. Looks good.
> > > - Petr Vandrovec: nicer ncpfs behaviour
> > > - Andy Grover: APCI update
> > > - Cort Dougan: PPC update
> > > - David Miller: sparc updates
> > > - David Miller: networking updates
> > > - Neil Brown: RAID5 fixes
> >
> > Do the tulip driver updates address the increasingly common NETDEV timeout
> > repots?
>
> In general you can answer this yourself by reading
> drivers/net/tulip/ChangeLog.
>
> I don't see increasingly common timeout reports.. with which hardware?
> They are likely on the newer LinkSys 4.1 cards, and there are still
> problesm with PNIC. Outside of that, other cards should be ok.
>
I have this problem also.
I have several machines that are almost unuseable due to the network device. I
need to do an ifconfig down/up to get connectivity back again. That doesn't
work so handy for a headless router . . . .
My desktop machine (2.3.9x - present) has dropped the network 4 or 5 times a day
for months.
-b
>
> Jeff
>
> --
> Jeff Garzik | "You see, in this world there's two kinds of
> Building 1024 | people, my friend: Those with loaded guns
> MandrakeSoft | and those who dig. You dig." --Blondie
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-23 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 1:13 2.4.1-test10 Linus Torvalds
2001-01-23 3:08 ` 2.4.1-test10 David Ford
2001-01-23 5:04 ` 2.4.1-test10 Derek Wildstar
2001-01-23 7:05 ` 2.4.1-test10 Jeff Garzik
2001-01-23 10:42 ` Ben Ford [this message]
2001-01-23 10:48 ` NETDEV timeout on tulips [was: Re: 2.4.1-test10] David Ford
2001-01-23 10:56 ` Matti Aarnio
2001-01-23 11:13 ` David Ford
2001-01-23 12:25 ` Matti Aarnio
2001-01-23 12:36 ` David Ford
2001-01-23 17:57 ` Jeff Garzik
2001-01-23 4:37 ` 2.4.1-test10 Marcelo Tosatti
2001-01-23 19:03 ` 2.4.1-test10 Linus Torvalds
2001-01-23 19:27 ` 2.4.1-test10 Andre Hedrick
2001-01-23 17:48 ` 2.4.1-test10 Marcelo Tosatti
2001-01-23 19:38 ` Under 2.4.0 I can mount same partition twice Dan Graham
2001-01-23 20:13 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 15:14 2.4.1-test10 Jonathan Earle
2001-01-23 15:27 ` 2.4.1-test10 Jeff Garzik
2001-01-23 22:20 2.4.1-test10 Ed Tomlinson
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=3A6D602B.E0A3BD22@talontech.com \
--to=bford@talontech.com \
--cc=david@linux.com \
--cc=jgarzik@mandrakesoft.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