From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: NaT consumption faults in current 2.5 BK kernel (FIXED)
Date: Fri, 18 Jul 2003 00:08:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105848702204930@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105840128613012@msgid-missing>
>>>>> "Peter" = Peter Chubb <peter@chubb.wattle.id.au> writes:
Peter> OK, thanks to the latest mod from David, I have the system
Peter> running on the simulator. Hurrah.
Peter> I can see a NaT consumption fault every time I cat
Peter> /proc/net/dev
OK, the problem is in the simulated ethernet driver. Trivial Patch appended:
=== arch/ia64/hp/sim/simeth.c 1.8 vs edited ==--- 1.8/arch/ia64/hp/sim/simeth.c Wed Jun 4 20:38:47 2003
+++ edited/arch/ia64/hp/sim/simeth.c Fri Jul 18 09:36:19 2003
@@ -223,7 +223,7 @@
dev->set_multicast_list = set_multicast_list; /* no yet used */
err = register_netdev(dev);
- if (dev) {
+ if (err) {
kfree(dev);
return err;
}
prev parent reply other threads:[~2003-07-18 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 0:21 NaT consumption faults in current 2.5 BK kernel Peter Chubb
2003-07-18 0:08 ` Peter Chubb [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=marc-linux-ia64-105848702204930@msgid-missing \
--to=peter@chubb.wattle.id.au \
--cc=linux-ia64@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