From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753557Ab0CHMw4 (ORCPT ); Mon, 8 Mar 2010 07:52:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:29896 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752331Ab0CHMww (ORCPT ); Mon, 8 Mar 2010 07:52:52 -0500 Date: Mon, 8 Mar 2010 13:51:22 +0100 From: Oleg Nesterov To: Ingo Molnar , Sergey Senozhatsky , Francois Romieu Cc: Peter Zijlstra , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, David Miller Subject: Re: inconsistent lock state Message-ID: <20100308125122.GA11242@redhat.com> References: <20100307192305.GA598@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100307192305.GA598@elte.hu> 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 Sergey Senozhatsky wrote: > > Hello, > > Hardly reproducible. > /* > * 2.6.33. x86. ASUS f3jc > */ > > [329645.010697] ================================= > [329645.010699] [ INFO: inconsistent lock state ] > [329645.010703] 2.6.33-33-0-dbg #31 > [329645.010705] --------------------------------- > [329645.010708] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. > > ... > > [329645.011083] [] netif_receive_skb+0x340/0x360 > [329645.011093] [] rtl8169_rx_interrupt+0x2bf/0x37e [r8169] > [329645.011100] [] rtl8169_reset_task+0x38/0xcd [r8169] > [329645.011105] [] worker_thread+0x1ac/0x27c I don't understand this code, but at first glance drivers/net/r8169.c is obviously buggy. The work->func, rtl8169_reset_task(), calls rtl8169_rx_interrupt() -> netif_receive_skb(), and the last one may only be called from softirq. Oleg.