Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760119AbXEJWQr (ORCPT ); Thu, 10 May 2007 18:16:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762822AbXEJWQX (ORCPT ); Thu, 10 May 2007 18:16:23 -0400 Received: from smtp1.linux-foundation.org ([65.172.181.25]:58756 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762720AbXEJWQU (ORCPT ); Thu, 10 May 2007 18:16:20 -0400 Date: Thu, 10 May 2007 15:14:26 -0700 From: Andrew Morton To: Jeremy Fitzhardinge Cc: Herbert Xu , "David S. Miller" , Christoph Hellwig , Andi Kleen , virtualization@lists.osdl.org, lkml , Chris Wright , Ian Pratt , Christian Limpach , netdev@vger.kernel.org, Jeff Garzik , Stephen Hemminger , Rusty Russell , Valdis.Kletnieks@vt.edu Subject: Re: [1/2] [NET] link_watch: Move link watch list into net_device Message-Id: <20070510151426.d808384f.akpm@linux-foundation.org> In-Reply-To: <464395E5.2090500@goop.org> References: <20070504232051.411946839@goop.org> <20070504232121.492190579@goop.org> <20070505091624.GA8890@infradead.org> <463C56D3.8060609@goop.org> <20070505102305.GA12771@gondor.apana.org.au> <463F95C3.60407@goop.org> <20070508121322.GA21647@gondor.apana.org.au> <464395E5.2090500@goop.org> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.6; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1738 Lines: 42 On Thu, 10 May 2007 15:00:05 -0700 Jeremy Fitzhardinge wrote: > Herbert Xu wrote: > > [NET] link_watch: Move link watch list into net_device > > > > These days the link watch mechanism is an integral part of the > > network subsystem as it manages the carrier status. So it now > > makes sense to allocate some memory for it in net_device rather > > than allocating it on demand. > > I think there's a problem with one of these two patches. I've been > noticing that one of my events/X threads has been going into a spin for > about 5 mins after boot. I added some debugging to > kernel/workqueue.c:run_workqueue, since its that loop which seems to be > spinning due to list corruption. > > When I look to see if that loop has iterated for more than 100 times in > one go (which seems unlikely), I get this: > > BUG: cpu 3, count=101 list screwup on c04babe4, func c03217e8 > func=linkwatch_event+0x0/0x2a > [] show_trace_log_lvl+0x1a/0x30 > [] show_trace+0x12/0x14 > [] dump_stack+0x16/0x18 > [] run_workqueue+0x97/0x18c > [] worker_thread+0xe5/0xf5 > [] kthread+0x3b/0x62 > [] kernel_thread_helper+0x7/0x10 > ======================= > > > I wonder if the problem is that the linkwatch_work is being rescheduled > when its already been scheduled, or something like that? Five minutes after boot is when jiffies wraps. Are you sure it's a list-screwup rather than a jiffy-wrap screwup? - 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/