netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fedor Karpelevitch <fedor@karpelevitch.net>
To: Jeff Garzik <jgarzik@pobox.com>, Sven-Haegar Koch <haegar@sdinet.de>
Cc: netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>,
	Andrew Morton <akpm@digeo.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: ifconfig up/down problem
Date: Wed, 10 Sep 2003 09:00:01 -0700	[thread overview]
Message-ID: <200309100900.01865.fedor@karpelevitch.net> (raw)
In-Reply-To: <200309100752.19594.fedor@karpelevitch.net>

Fedor Karpelevitch wrote:
> Fedor Karpelevitch wrote:
> > Fedor Karpelevitch wrote:
> > > Jeff Garzik wrote:
> > > > Sven-Haegar Koch wrote:
> > > > > Kernel 2.4.20-pre2-ac3 is ok (my last kernel, running for
> > > > > month')
> > > >
> > > > Does the attached patch fix it?
> > > >
> > > > 	Jeff
> > >
> > > does not help me (assuming I have the same problem). I have a
> > > total lockup a few seconds after setting up the interface (not
> > > immidiately).
> > >
> > > Fedor.
> >
> > actually it seemed to have helped with 2.6.0-test5 where I was
> > apparently having the same issue. Not with 2.4.23-pre3 however...
> >
> > Fedor.
>
> I am really sorry for giving all this misleading information but
> now it works fine for me with 2.4.23-pre3 as well, but I bet it did
> lock up the first time I tried it. So there may be something wrong
> with me or it is some other random problem I am seeing...
>
> Fedor

shit, it DOES happen. somehow, when network cable is unplugged it 
seems to never happen, when I am plugged in at home I believe I could 
have gotten that lockup once or twice, but when I am plugged in to 
the network at my office it seems to happen 100% of the time. I use 
DHCP in either case. I wonder if it could be related to the noise 
traffic on the network or what. I get it with both 2.4.23-pre3 and 
2.6.0-test5 with your patch. It does not seem to occur at any 
particular time - just some time (seconds to minute or two) after the 
boot up.

Could you suggest any way to at least trace this problem down?

Fedor.

      reply	other threads:[~2003-09-10 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 22:08 ifconfig up/down problem Sven-Haegar Koch
2003-09-08 22:15 ` [PATCH] " Jeff Garzik
2003-09-08 22:40   ` Sven-Haegar Koch
2003-09-09 23:35   ` Fedor Karpelevitch
2003-09-10  6:08     ` Fedor Karpelevitch
2003-09-10 14:52       ` Fedor Karpelevitch
2003-09-10 16:00         ` Fedor Karpelevitch [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=200309100900.01865.fedor@karpelevitch.net \
    --to=fedor@karpelevitch.net \
    --cc=akpm@digeo.com \
    --cc=davem@redhat.com \
    --cc=haegar@sdinet.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).