Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757935AbXJZR4r (ORCPT ); Fri, 26 Oct 2007 13:56:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752944AbXJZR4f (ORCPT ); Fri, 26 Oct 2007 13:56:35 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:36756 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752516AbXJZR4e (ORCPT ); Fri, 26 Oct 2007 13:56:34 -0400 Date: Fri, 26 Oct 2007 19:56:13 +0200 From: Ingo Molnar To: Stephen Hemminger Cc: Francois Romieu , Romano Giannetti , Peter Zijlstra , Linux Kernel Mailing List , "David S. Miller" , netdev@vger.kernel.org, Edward Hsu , Jeff Garzik , Andrew Morton Subject: Re: 2.6.24-rc1 fails with lockup - /sbin/ifconfig / inet_ioctl() / dev_close() / rtl8169_down() Message-ID: <20071026175613.GA18770@elte.hu> References: <1193232344.32208.0.camel@localhost> <20071024142759.GA13657@elte.hu> <1193241191.14314.8.camel@localhost> <20071024155521.GA16690@elte.hu> <1193242267.6914.6.camel@twins> <1193378269.17910.4.camel@localhost> <20071026063733.GA12426@elte.hu> <20071026094833.539a69aa@freepuppy.rosehill> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071026094833.539a69aa@freepuppy.rosehill> User-Agent: Mutt/1.5.14 (2007-02-12) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.1.7-deb -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 948 Lines: 30 * Stephen Hemminger wrote: > > hm, from your log it appears that lockdep did not find anything, > > still the hang does trigger. > > > > it's /sbin/ifconfig and inet_ioctl() / dev_close() / rtl8169_down() > > that seems to be hanging. I've extracted the relevant backtrace > > below. I've Cc:-ed people who might have a better idea about what's > > going on. > > Are you building with NAPI enabled or not. Looks like the following > might help the non-napi case. the config from: http://www.dea.icai.upcomillas.es/romano/linux/info/2624rc1_1/ suggests that NAPI was disabled: CONFIG_R8169=m # CONFIG_R8169_NAPI is not set CONFIG_R8169_VLAN=y Ingo - 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/