From: Jarek Poplawski <jarkao2@gmail.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: netdev@vger.kernel.org
Subject: Re: _xmit_ETHER lockdep warning. (-git8)
Date: Fri, 01 Aug 2008 22:06:02 +0200 [thread overview]
Message-ID: <48936CAA.8080504@gmail.com> (raw)
In-Reply-To: <20080801192947.GA26210@codemonkey.org.uk>
Dave Jones wrote, On 08/01/2008 09:29 PM:
> A week or so old, but possibly still valid..
Just fixed in net-2.6:
commit c3f26a269c2421f97f10cf8ed05d5099b573af4d
Author: David S. Miller <davem@davemloft.net>
Date: Thu Jul 31 16:58:50 2008 -0700
netdev: Fix lockdep warnings in multiqueue configurations.
Jarek P.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=456521
>
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.27-0.166.rc0.git8.fc10.x86_64 #1
> ---------------------------------------------
> swapper/0 is trying to acquire lock:
> (_xmit_ETHER){-+..}, at: [<ffffffff812828a3>] dev_watchdog+0x41/0x1a7
>
> but task is already holding lock:
> (_xmit_ETHER){-+..}, at: [<ffffffff812828a3>] dev_watchdog+0x41/0x1a7
>
> other info that might help us debug this:
> 1 lock held by swapper/0:
> #0: (_xmit_ETHER){-+..}, at: [<ffffffff812828a3>] dev_watchdog+0x41/0x1a7
>
> stack backtrace:
> Pid: 0, comm: swapper Not tainted 2.6.27-0.166.rc0.git8.fc10.x86_64 #1
>
> Call Trace:
> <IRQ> [<ffffffff81061b46>] __lock_acquire+0x790/0xaa7
> [<ffffffff81060d80>] ? trace_hardirqs_on+0xd/0xf
> [<ffffffff812828a3>] ? dev_watchdog+0x41/0x1a7
> [<ffffffff81061ef3>] lock_acquire+0x96/0xc3
> [<ffffffff812828a3>] ? dev_watchdog+0x41/0x1a7
> [<ffffffff812f5eb8>] _spin_lock+0x2b/0x58
> [<ffffffff812828a3>] dev_watchdog+0x41/0x1a7
> [<ffffffff81282862>] ? dev_watchdog+0x0/0x1a7
> [<ffffffff81048ba6>] run_timer_softirq+0x17f/0x1f7
> [<ffffffff810450eb>] __do_softirq+0x83/0x110
> [<ffffffff8100dcbc>] call_softirq+0x1c/0x28
> [<ffffffff8100ef81>] do_softirq+0x52/0xb5
> [<ffffffff81044c95>] irq_exit+0x53/0xa0
> [<ffffffff8101d160>] smp_apic_timer_interrupt+0x94/0xad
> [<ffffffff8100d4c8>] apic_timer_interrupt+0x88/0x90
> <EOI> [<ffffffff81022880>] ? native_safe_halt+0x6/0x8
> [<ffffffff81060d80>] ? trace_hardirqs_on+0xd/0xf
> [<ffffffff81013537>] ? default_idle+0x2f/0x51
> [<ffffffff81013661>] ? c1e_idle+0x108/0x10f
> [<ffffffff812f9204>] ? atomic_notifier_call_chain+0x14/0x16
> [<ffffffff8100b2d6>] ? cpu_idle+0x92/0xeb
> [<ffffffff812efbef>] ? start_secondary+0x1a1/0x1a3
>
next prev parent reply other threads:[~2008-08-01 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 19:29 _xmit_ETHER lockdep warning. (-git8) Dave Jones
2008-08-01 20:06 ` Jarek Poplawski [this message]
2008-08-01 23:18 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48936CAA.8080504@gmail.com \
--to=jarkao2@gmail.com \
--cc=davej@codemonkey.org.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.