Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262652AbTIJP5k (ORCPT ); Wed, 10 Sep 2003 11:57:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265083AbTIJP5k (ORCPT ); Wed, 10 Sep 2003 11:57:40 -0400 Received: from halon.barra.com ([144.203.11.1]:56045 "EHLO halon.barra.com") by vger.kernel.org with ESMTP id S262652AbTIJP5f (ORCPT ); Wed, 10 Sep 2003 11:57:35 -0400 From: Fedor Karpelevitch To: Jeff Garzik , Sven-Haegar Koch Subject: Re: [PATCH] Re: ifconfig up/down problem Date: Wed, 10 Sep 2003 09:00:01 -0700 User-Agent: KMail/1.5.3 Cc: netdev@oss.sgi.com, "David S. Miller" , Andrew Morton , LKML References: <200309092308.48099.fedor@karpelevitch.net> <200309100752.19594.fedor@karpelevitch.net> In-Reply-To: <200309100752.19594.fedor@karpelevitch.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309100900.01865.fedor@karpelevitch.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1783 Lines: 48 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. - 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/