From: Jon Smirl <jonsmirl@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: David Gibson <david@gibson.dropbear.id.au>,
akpm@osdl.org, trivial@rustcorp.com.au,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [TRIVIAL] Fix recent bug in fib_semantics.c
Date: Fri, 17 Sep 2004 20:21:51 -0400 [thread overview]
Message-ID: <9e47339104091717215e9be08b@mail.gmail.com> (raw)
In-Reply-To: <20040917112744.190f6f3e.davem@davemloft.net>
I'm still OOPsing at boot in fib_disable_ip+21 from
fib_netdev_event+63. Both e1000 and tg3 are effected. I have current
linus bk as of time of this message.
It only occurs when Redhat goes through the scaning for new hardware
phase during boot. Is RH loading the drivers in some special way
during this phase? If I load the drivers manually after I'm booted
they load ok. I'm running with the drivers as modules, I'll try
switching to compiled in.
The change referenced in this thread is in my kernel:
fib_semantics.c, 604
} else {
memset(new_info_hash, 0, bytes);
memset(new_laddrhash, 0, bytes);
fib_hash_move(new_info_hash, new_laddrhash, new_size);
}
On Fri, 17 Sep 2004 11:27:44 -0700, David S. Miller <davem@davemloft.net> wrote:
>
> Thanks David, I'll push this upstream asap.
>
> I can't believe in all the route testing I did I never
> triggered this on my sparc64 boxes, must have been lucky :(
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-18 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 6:20 [TRIVIAL] Fix recent bug in fib_semantics.c David Gibson
2004-09-17 6:37 ` Jeff Garzik
2004-09-17 18:27 ` David S. Miller
2004-09-18 0:21 ` Jon Smirl [this message]
2004-09-18 0:27 ` Herbert Xu
2004-09-18 0:59 ` Jon Smirl
2004-09-18 1:37 ` Jon Smirl
2004-09-18 4:16 ` Herbert Xu
2004-09-18 5:22 ` Jon Smirl
2004-09-18 6:31 ` David S. Miller
2004-09-18 15:28 ` Jon Smirl
2004-09-18 20:31 ` jamal
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=9e47339104091717215e9be08b@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=trivial@rustcorp.com.au \
/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).