public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6-mm1
Date: Wed, 7 Jun 2006 23:54:41 +0200	[thread overview]
Message-ID: <200606072354.41443.rjw@sisk.pl> (raw)
In-Reply-To: <20060607104724.c5d3d730.akpm@osdl.org>

On Wednesday 07 June 2006 19:47, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm1/
> 
> - Many more lockdep updates

Well, I've got this one (Asus L5D, x86_64 kernel):

============================
[ BUG: illegal lock usage! ]
----------------------------
illegal {in-hardirq-W} -> {hardirq-on-W} usage.
hwinfo/3398 [HC0[0]:SC0[1]:HE1:SE0] takes:
 (&list->lock){++..}, at: [<ffffffff8046d301>] unix_stream_connect+0x371/0x440
{in-hardirq-W} state was registered at:
  [<ffffffff8024bdaa>] lock_acquire+0x8a/0xc0
  [<ffffffff8047347f>] _spin_lock_irqsave+0x3f/0x60
  [<ffffffff80406e72>] skb_dequeue+0x22/0x70
  [<ffffffff881c97b1>] hpsb_bus_reset+0x61/0xb0 [ieee1394]
  [<ffffffff8822e986>] ohci_irq_handler+0x416/0x830 [ohci1394]
  [<ffffffff8026208b>] handle_IRQ_event+0x2b/0x70
  [<ffffffff80263a03>] handle_level_irq+0xb3/0x120
  [<ffffffff8020c6ec>] do_IRQ+0x5c/0x80
  [<ffffffff80209d60>] common_interrupt+0x64/0x65
irq event stamp: 29916
hardirqs last  enabled at (29915): [<ffffffff802893f5>] kmem_cache_free+0xb5/0xd0
hardirqs last disabled at (29914): [<ffffffff802893d0>] kmem_cache_free+0x90/0xd0
softirqs last  enabled at (29912): [<ffffffff802342fe>] __do_softirq+0xbe/0xd0
softirqs last disabled at (29916): [<ffffffff80472ac1>] _spin_lock_bh+0x11/0x50

other info that might help us debug this:
1 lock held by hwinfo/3398:
 #0:  (&u->lock){--..}, at: [<ffffffff8046d093>] unix_stream_connect+0x103/0x440

stack backtrace:

Call Trace:
 [<ffffffff8020abd6>] show_trace+0xa6/0x220
 [<ffffffff8020af85>] dump_stack+0x15/0x20
 [<ffffffff8024a64c>] print_usage_bug+0x23c/0x250
 [<ffffffff8024a94f>] mark_lock+0x2ef/0x6a0
 [<ffffffff8024b1e6>] __lock_acquire+0x4e6/0xc80
 [<ffffffff8024bdab>] lock_acquire+0x8b/0xc0
 [<ffffffff80472ae4>] _spin_lock_bh+0x34/0x50
 [<ffffffff8046d301>] unix_stream_connect+0x371/0x440
 [<ffffffff80402077>] sys_connect+0x87/0xc0
 [<ffffffff8020982a>] system_call+0x7e/0x83
 [<00002ab066fc6472>]


Greetings,
Rafael

  parent reply	other threads:[~2006-06-07 21:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36     ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54     ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  0:31       ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08  6:30         ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  7:26       ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` Rafael J. Wysocki [this message]
2006-06-07 22:11   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08  3:19     ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13       ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06     ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Duncan Sands
2006-06-12 14:35       ` Ingo Molnar
2006-06-08 12:54     ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23     ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08  0:04       ` Randy.Dunlap
2006-06-08  2:11       ` Jeff Dike
2006-06-08  2:32         ` Randy.Dunlap
2006-06-08  4:21           ` Jeff Dike
2006-06-08  4:29             ` Randy.Dunlap
2006-06-08 15:44               ` Randy.Dunlap
2006-06-08 18:35         ` Sam Ravnborg
2006-06-11 23:25           ` Jeff Dike
2006-06-12  0:17             ` Randy.Dunlap
2006-06-12  2:29               ` Jeff Dike
2006-06-12  2:52                 ` Randy.Dunlap
2006-06-08  2:25     ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  2:46       ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08  5:43         ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  6:46       ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08  1:09     ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08  5:00 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-20 17:42   ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24     ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21  6:23     ` 2.6.17-rc6-mm1 Dave Jones
2006-06-21  8:15       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42         ` 2.6.17-rc6-mm1 Dave Jones

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=200606072354.41443.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox