From: Deepak Saxena <dsaxena@plexity.net>
To: Cam <camilo@mesias.co.uk>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.20_mvl31 OOPS ip_route_input called within ip_rt_init
Date: Thu, 22 Jul 2004 11:44:44 -0700 [thread overview]
Message-ID: <20040722184444.GA6270@plexity.net> (raw)
In-Reply-To: <40FFFF10.2000902@mesias.co.uk>
On Jul 22 2004, at 18:53, Cam was caught saying:
> Hi,
>
> I have an embedded ppc linux which sometimes can oops at boot time if it
> receives a packet during ip_rt_init. There is a printk in there in the
> middle of initialisation of rt_hash_table which can introduce a delay
> which makes the problem more likely to happen,
_Please_ do not send questions for vendor-supplied and supported kernels
to this list. If you have this kernel, you are probably a MVista
customer and you should go ask their support folks.
~Deepak
--
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/
"Unlike me, many of you have accepted the situation of your imprisonment and
will die here like rotten cabbages." - Number 6
prev parent reply other threads:[~2004-07-22 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 17:53 linux-2.4.20_mvl31 OOPS ip_route_input called within ip_rt_init Cam
2004-07-22 18:44 ` Deepak Saxena [this message]
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=20040722184444.GA6270@plexity.net \
--to=dsaxena@plexity.net \
--cc=camilo@mesias.co.uk \
--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