linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "LEROY Christophe" <christophe.leroy@c-s.fr>
To: Peter Desnoyers <pdesnoyers@chinook.com>
Cc: linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Kernel Oops when receiving a lot of UDP packets while booting
Date: Fri, 28 Dec 2001 16:39:02 +0100	[thread overview]
Message-ID: <3C2C9215.65A76EB@c-s.fr> (raw)
In-Reply-To: 3C2C8CC1.E2A99B19@chinook.com


What is HHL2.0 ?
I'm using the official 2.4.16 kernel from kernel.org with the ppc ports
patch for 2.4.15.
I'm not using FEC but MC68160A (that is enet.c). But that's probably the
same problem.
Any idea how to solve the problem ?

C.Leroy

Peter Desnoyers a écrit :

> You're using HHL2.0?  There's a bug in fec.c where it will pass packets
> up the stack too early in initialization.  The tcp stack doesn't take
> too kindly to this, as a number of data structures which are assumed to
> exist by the code are actually null pointers at this point in time...
>
> --
> .....................................................................
>  Peter Desnoyers            (781) 457-1165   pdesnoyers@chinook.com
>  Chinook Communications     (617) 661-1979   pjd@fred.cambridge.ma.us
>  100 Hayden Ave, Lexington MA 02421


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-12-28 15:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 14:41 Kernel Oops when receiving a lot of UDP packets while booting LEROY Christophe
2001-12-28 15:16 ` Peter Desnoyers
2001-12-28 15:39   ` LEROY Christophe [this message]
2001-12-28 16:09     ` Peter Desnoyers
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07 12:30 Kári Davíðsson
2002-01-07 15:02 ` Peter Desnoyers
2002-01-07 15:16 Kári Davíðsson

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=3C2C9215.65A76EB@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pdesnoyers@chinook.com \
    /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;
as well as URLs for NNTP newsgroup(s).