public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@dds.nl>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] netconsole - log kernel messages over the network. 2.4.10.
Date: Thu, 27 Sep 2001 20:30:53 +0200	[thread overview]
Message-ID: <20010927203053.J774@humilis> (raw)
In-Reply-To: <20010927171818.H774@humilis> <3BB36A6A.B0736CA2@zip.com.au>
In-Reply-To: <3BB36A6A.B0736CA2@zip.com.au>

Hi Andrew,

> > Ingo was not aware of the sourceforge project, and suggested me to
> > resend my reply to lkml. Does the patch work for you guys? Do I do
> > something wrong? That would be more than possible. :-)
> > 
> > ...
> > cuddle:~# uname -a
> > Linux cuddle 2.4.9-ac15 #1 Thu Sep 27 13:54:51 CEST 2001 i686 unknown
> > cuddle:~# insmod netconsole dev=eth0 target_ip=0x0a604875 source_port=6666 target_port=5555
> > Using /lib/modules/2.4.9-ac15/kernel/drivers/net/netconsole.o
> > /lib/modules/2.4.9-ac15/kernel/drivers/net/netconsole.o: init_module: Operation not permitted
> > Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
> 
> If you're not using the eepro100 driver, then an insmod of the
> netconsole driver will fail:
> 
> 
> +       if (!ndev->poll_controller) {
> +               printk(KERN_ERR "netconsole: %s's network driver does not implement netlogging yet, aborting.\n", dev);
> +               return -1;
> +       }
> 
> Maybe that message is in your logs somewhere?

Have to check that, can't reach the machine atm. But I don't use the
eepro100 driver for sure in that machine, so the insmod failure makes
sense. :-)

> Take a look at the poll_controller() implementation in the eepro100
> part of Ingo's patch - it's dead simple.

I believe you ;-)  but I'm affraid I'm just a user, no programmer at
all :-(

> What we need is for a bunch of people to implement poll_controller()
> for *their* ethernet driver and contribute the tested diffs back to
> Ingo.

Would love to contribute.. Anyway, thank you for your answer!

	Ookhoi

  reply	other threads:[~2001-09-27 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 15:18 [patch] netconsole - log kernel messages over the network. 2.4.10 Ookhoi
2001-09-27 18:05 ` Andrew Morton
2001-09-27 18:30   ` Ookhoi [this message]
2001-09-28  2:53   ` Albert Cranford
2001-09-28  7:45     ` [patch] netconsole-2.4.10-C2 Ingo Molnar
2002-03-09 17:17       ` netconsole patch for 2.5? Barton, Christopher
  -- strict thread matches above, loose matches on Subject: below --
2001-09-26 20:04 [patch] netconsole - log kernel messages over the network. 2.4.10 Ingo Molnar
2001-09-26 19:36 ` Marcelo Tosatti
2001-09-26 21:15   ` jamal
2001-09-27  5:45     ` Ingo Molnar
2001-09-26 21:29   ` Andreas Dilger
2001-09-26 23:46     ` Andreas Dilger
2001-09-27  5:28       ` Ingo Molnar

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=20010927203053.J774@humilis \
    --to=ookhoi@dds.nl \
    --cc=akpm@zip.com.au \
    --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