LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Kernel Panic while building IP or TCP hash tables
Date: Wed, 18 Jun 2003 16:04:44 +0200	[thread overview]
Message-ID: <000001c335a2$9767eb50$5201a8c0@GEG2400> (raw)


Hi,

After many days of tests, I can say that the system does not crash anymore
with the patch installed.

The most difficult thing is to determine the frames which generate the
kernel panic.
I can exclude arp broadcast frames and ip unicast frames.
It seems that the multicast frames are the origin of the system crash but I
can't say
if it is the only case.

The system runs in any case with the patch. Use it !!!

Thanks to Jean-Denis Boyer

Gérard Guével


-----Message d'origine-----
De : Jean-Denis Boyer [mailto:jdboyer@m5t.com]
Envoyé : jeu. 5 juin 2003 14:09
À : Gérard Guével
Cc : linuxppc-embedded@lists.linuxppc.org
Objet : RE: Kernel Panic while building IP or TCP hash tables



I experienced a similar problem with my system, I was not sure if it was
specific to my implementation. Can you try the following patch and tell us
if it helps?

It registers the IPv4 handling functions AFTER initializing the IP routing
stuff. Early packets could enter the stack and crash the system.

--- Kernel.old/net/ipv4/ip_output.c     Thu Jun  5 09:00:39 2003
+++ Kernel/net/ipv4/ip_output.c Thu Jun  5 09:00:28 2003
@@ -1087,11 +1087,11 @@

 void __init ip_init(void)
 {
-       dev_add_pack(&ip_packet_type);
-
        ip_rt_init();
        inet_initpeers();

+       dev_add_pack(&ip_packet_type);
+
 #ifdef CONFIG_IP_MULTICAST
        proc_net_create("igmp", 0, ip_mc_procinfo);
 #endif


Salutations,

--------------------------------------------
 Jean-Denis Boyer, Software Designer
 M5T Centre d'Excellence en Télécom Inc.
 4283 Garlock Street
 Sherbrooke (Québec)
 J1L 2C8  CANADA
 (819)829-3972 x241
--------------------------------------------


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

             reply	other threads:[~2003-06-18 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 14:04 Gérard Guével [this message]
     [not found] <AB5AF73EAF23304EA1B932174137CED702FB9F@m5tmail.m5t.com>
2003-06-18  7:56 ` Kernel Panic while building IP or TCP hash tables Gérard Guével
  -- strict thread matches above, loose matches on Subject: below --
2003-06-05 13:06 Jean-Denis Boyer
2002-11-18 16:36 Problem with FCC under 2.4.18 kernel Gérard Guével
2003-06-05 12:48 ` Kernel Panic while building IP or TCP hash tables Gérard Guével

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='000001c335a2$9767eb50$5201a8c0@GEG2400' \
    --to=gguevel@interfaceconcept.com \
    --cc=linuxppc-embedded@lists.linuxppc.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