mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: mshiju@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with DHCP when using tokenring on 2.4.x
Date: Wed, 25 Apr 2001 09:50:32 +0200	[thread overview]
Message-ID: <20010425095032.A19553@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <CA256A38.0060F2DE.00@d73mta05.au.ibm.com>
In-Reply-To: <CA256A38.0060F2DE.00@d73mta05.au.ibm.com>; from mshiju@in.ibm.com on Tue, Apr 24, 2001 at 06:30:59PM +0530

On Tue, Apr 24, 2001 at 06:30:59PM +0530, mshiju@in.ibm.com wrote:
>            I have a problem with DHCP when using tokenring card on 2.4.x
> kernel . When I am using IBM tokenring adapter( all) and trying to hook on
> to the lan n/w using DHCP ,I get an error message "operation failed " from
> the dhcp client . The dhcp server is getting the broadcast message when the
> dhcp client  is run. I am using pump that comes with 6.2 redhat
> distribution .

Try at least stracing pump and find out _which_ operation fails.

Then find out where in the source there are messages "operation
failed" and whatever messages are around that message and compare
these positions with the call trace you get from strace and an
static analysis of the code paths leading to this message.

As a last resort try to run a debugger over pump (you have to
rebuild it without optimization and with debugging symbols).

This sounds like an user space problem until now, but once you
tried all this, we can decide whether it is a kernel bug or a bug
in pump, which got triggered by more correct behavior of the
lastest kernels.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<     been there and had much fun   >>>>>>>>>>>>

  reply	other threads:[~2001-04-25  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 13:00 mshiju
2001-04-25  7:50 ` Ingo Oeser [this message]
2001-04-24 15:14 mshiju
2001-04-25  9:57 Mulder, Tjeerd

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=20010425095032.A19553@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mshiju@in.ibm.com \
    /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

all inboxes | Powered by JetHome®