From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Andrew Friedley <saai@swbell.net>, linux-kernel@vger.kernel.org
Subject: Re: pppoe patch in 2.4.7 results - still problem
Date: Mon, 23 Jul 2001 20:05:49 -0400 [thread overview]
Message-ID: <3B5CBBDD.61365F56@mandrakesoft.com> (raw)
In-Reply-To: <000901c112d6$a1a30000$0200a8c0@loki> <15196.46734.280781.653712@pizda.ninka.net>
"David S. Miller" wrote:
> Andrew Friedley writes:
> > In response to the pppoe patch to try to fix panics with pppoe and smp:
> > When running napster/napigator from a windows machine on my LAN, the router
> > running 2.4.7 still panics. It has not been long enough to tell if the
> > "random" panics have been fixed for sure, but so far, so good - 1 day, 4
> > hour uptime right now. Here is a paste of a napster-induced panic with
> > kernel 2.4.7 followed by the ksymoops output.
> This looks like perhaps a specific problem with the 8139too
> patches to support single-copy checksumming. I could be wrong,
> but it looks nothing like the pppoe OOPS traces.
via-rhine is the only user of skb_copy_and_csum_dev at present; but the
point still stands. (I am holding off on that 8139too patch, for just a
bit, to stabilize the driver WRT bugs)
Jeff
--
Jeff Garzik | "I use Mandrake Linux for the same reason I turn
Building 1024 | the light switch on and off 17 times before leaving
MandrakeSoft | the room.... If I don't my family will die."
| -- slashdot.org comment
next prev parent reply other threads:[~2001-07-24 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 17:49 pppoe patch in 2.4.7 results - still problem Andrew Friedley
2001-07-23 23:43 ` David S. Miller
2001-07-24 0:05 ` Jeff Garzik [this message]
2001-07-24 0:11 ` David S. Miller
2001-07-25 2:22 ` Alexey Kuznetsov
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 8:30 Jörn Nettingsmeier
2001-07-25 2:36 ` Alexey Kuznetsov
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=3B5CBBDD.61365F56@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saai@swbell.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.