From: Andrea Ferraris <andrea_ferraris@libero.it>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: OPS: eth0: NULL pointer encountered in RX ring, skipping
Date: Sat, 26 Jan 2002 16:24:23 +0100 [thread overview]
Message-ID: <02012616242303.03848@af> (raw)
In-Reply-To: <20020125180149.GB45738@compsoc.man.ac.uk> <3C51E36B.6296299D@mandrakesoft.com> <0201261111500C.01074@af>
In-Reply-To: <0201261111500C.01074@af>
Saturday 26 January 2002 11:11, Andrea Ferraris scrisse:
> Friday 25 January 2002 23:59, Jeff Garzik scrisse:
> > Well, the code says "this should never happen" ;-)
> >
> > But anyway, it is probably a temporary memory allocation failure. The
> > code handles this case.
>
> Yes, but I think that isn't normal to have to do a cold reboot to have the
> machine again working on the network. It is, maybe that the code doesn't
> handle so well this case. Do you suggest a kernel upgrade?
Ops ... sorry. It was a 2.2.16 kernel.
Andrea
next prev parent reply other threads:[~2002-01-26 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 17:28 [PATCH] Fix 2.5.3pre reiserfs BUG() at boot time Andi Kleen
2002-01-25 18:01 ` John Levon
2002-01-25 18:08 ` Linus Torvalds
2002-01-25 18:31 ` Andreas Dilger
2002-01-25 18:46 ` Hans Reiser
2002-01-25 19:49 ` Andi Kleen
2002-01-25 20:38 ` Andreas Dilger
2002-01-25 22:15 ` Andi Kleen
2002-01-25 22:32 ` eth0: NULL pointer encountered in RX ring, skipping Andrea Ferraris
2002-01-25 22:59 ` Jeff Garzik
2002-01-26 10:11 ` Andrea Ferraris
2002-01-26 15:24 ` Andrea Ferraris [this message]
2002-01-25 22:41 ` [PATCH] Fix 2.5.3pre reiserfs BUG() at boot time Andreas Dilger
2002-01-26 7:24 ` Kai Henningsen
2002-01-27 23:02 ` Alessandro Suardi
2002-01-28 0:01 ` Andi Kleen
2002-01-28 11:07 ` Jens Axboe
2002-01-28 14:53 ` Andi Kleen
2002-01-28 14:54 ` Jens Axboe
2002-01-29 13:14 ` Alessandro Suardi
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=02012616242303.03848@af \
--to=andrea_ferraris@libero.it \
--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 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.