From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755220AbZEHKqs (ORCPT ); Fri, 8 May 2009 06:46:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751926AbZEHKqh (ORCPT ); Fri, 8 May 2009 06:46:37 -0400 Received: from rv-out-0506.google.com ([209.85.198.231]:18160 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751831AbZEHKqg (ORCPT ); Fri, 8 May 2009 06:46:36 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sD6JpTu6J8klkddSkkxCRdJATrZlnUuq980uJUjpLgVNRYrU8Ut9gtu8/z8bfceXwB KZA4e7/eT4a2ubSY06WWPRMaBIfkn8H0cxu9GG3JOOlrplXApX5ALWdNiCFiNQDTp8RS 4rI+siu3heA6dSz8N09y7LaRPQqZnjCyaVRdU= Date: Fri, 8 May 2009 10:46:28 +0000 From: Jarek Poplawski To: "Alexander V. Lukyanov" Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: 2.6.29.1: unregister_netdevice problem Message-ID: <20090508104628.GA6287@ff.dom.local> References: <20090422055735.GA4334@night.netis.ru> <20090427054103.GA27529@night.netis.ru> <20090428125755.GA5242@night.netis.ru> <49F76BF6.4040709@gmail.com> <20090429054510.GA8267@night.netis.ru> <20090429090809.GA2995@ami.dom.local> <20090508062640.GA4555@night.netis.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090508062640.GA4555@night.netis.ru> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 08, 2009 at 10:26:40AM +0400, Alexander V. Lukyanov wrote: > On Wed, Apr 29, 2009 at 11:08:09AM +0200, Jarek Poplawski wrote: > > So looks like a regression. Alas this thing could be hard to debug and > > still more data is needed. For the beginning maybe: .config, dmesg, > > and a few SysRq logs while this happens e.g. Alt-PrtScr with t, d, w, q > > (gzipped or as attachments to a bugzilla report). (If it's not a big > > problem trying 2.6.28.9 could be helpful too.) > > It happened again with 2.6.29.2. Here is the requested info. I can't see anything suspicious for now, except these UDP and TCP warnings. Did you see similar messages with 2.6.27? Btw., could this eth0.987 be "connected" with any of this traffic? (IP# ?) Thanks, Jarek P.