All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@osdl.org>,
	arjan@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org, stefanr@s5r6.in-berlin.de
Subject: Re: 2.6.17-rc5-mm3-lockdep -
Date: Tue, 06 Jun 2006 09:00:18 +0159	[thread overview]
Message-ID: <44852819.2080503@gmail.com> (raw)
In-Reply-To: <200606060250.k562oCrA004583@turing-police.cc.vt.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Valdis.Kletnieks@vt.edu napsal(a):
> It's living longer before it throws a complaint - we're making it out of
> rc.sysinit and into rc5.d ;)  This time we were in an 'id' command from this:
> 
> test `id -u` = 0  || exit 4
> 
> in either S11mcstrans or S18auditd.  Looks like the Firewire (which I
> don't actually use for anything) threw an IRQ at an inopportune time?
> 
> (Obviously I stress different code paths than Arjan or Ingo.  But if
> I did the same things they did, it wouldn't be interesting.. ;)
> 
> [  464.687000] (              id-2700 |#0): new 569737200 us user-latency.
> [  464.687000] stopped custom tracer.
> [  464.687000] 
> [  464.687000] ============================
> [  464.687000] [ BUG: illegal lock usage! ]
> [  464.687000] ----------------------------
> [  464.687000] illegal {in-hardirq-W} -> {hardirq-on-W} usage.
> [  464.687000] id/2700 [HC0[0]:SC0[1]:HE1:SE0] takes:
> [  464.687000]  (&list->lock){++..}, at: [<c0351a07>] unix_stream_connect+0x334/0x408
> [  464.687000] {in-hardirq-W} state was registered at:
> [  464.687000]   [<c012dd45>] lockdep_acquire+0x67/0x7f
> [  464.687000]   [<c0383f11>] _spin_lock_irqsave+0x30/0x3f
> [  464.687000]   [<c02fa93f>] skb_dequeue+0x18/0x49
> [  464.687000]   [<f086b7f1>] hpsb_bus_reset+0x5e/0xa2 [ieee1394]
> [  464.687000]   [<f0887007>] ohci_irq_handler+0x370/0x726 [ohci1394]
> [  464.687000]   [<c013f9a8>] handle_IRQ_event+0x1d/0x52
> [  464.687000]   [<c0140bc4>] handle_level_irq+0x97/0xe3
> [  464.687000]   [<c01045d0>] do_IRQ+0x8b/0xaf
> [  464.687000] irq event stamp: 2964
> [  464.687000] hardirqs last  enabled at (2963): [<c0384223>] _spin_unlock_irqrestore+0x3b/0x6d
> [  464.687000] hardirqs last disabled at (2962): [<c0383ef5>] _spin_lock_irqsave+0x14/0x3f
> [  464.687000] softirqs last  enabled at (2956): [<c0119da0>] __do_softirq+0x9d/0xa5
> [  464.687000] softirqs last disabled at (2964): [<c0383f6b>] _spin_lock_bh+0x10/0x3a
> [  464.687000] 
> [  464.687000] other info that might help us debug this:
> [  464.687000] 1 locks held by id/2700:
> [  464.687000]  #0:  (&u->lock){--..}, at: [<c03517bb>] unix_stream_connect+0xe8/0x408
> [  464.687000] 
> [  464.687000] stack backtrace:
> [  464.687000]  [<c01032d6>] show_trace_log_lvl+0x64/0x125
> [  464.687000]  [<c0103865>] show_trace+0x1b/0x20
> [  464.687000]  [<c010391c>] dump_stack+0x1f/0x24
> [  464.687000]  [<c012bfb1>] print_usage_bug+0x1a8/0x1b4
> [  464.687000]  [<c012c6c7>] mark_lock+0x2ba/0x4e5
> [  464.687000]  [<c012d2b8>] __lockdep_acquire+0x476/0xa91
> [  464.687000]  [<c012dd45>] lockdep_acquire+0x67/0x7f
> [  464.687000]  [<c0383f87>] _spin_lock_bh+0x2c/0x3a
> [  464.687000]  [<c0351a07>] unix_stream_connect+0x334/0x408
> [  464.687000]  [<c02f7236>] sys_connect+0x6e/0xa3
> [  464.687000]  [<c02f79da>] sys_socketcall+0x96/0x190
> [  464.687000]  [<c03845e2>] sysenter_past_esp+0x63/0xa1
> 
That one would be corrected now:
http://lkml.org/lkml/2006/6/5/100

regards,
- --
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEhSgZMsxVwznUen4RAqfjAKC8lvknOP66TEqb1oD7y9RaoAaW1gCfWk/m
4GLhay/GeS/wij5E6V9LUOg=
=uN9Z
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-06-06  7:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  2:50 2.6.17-rc5-mm3-lockdep - Valdis.Kletnieks
2006-06-06  7:01 ` Jiri Slaby [this message]
2006-06-06 12:48   ` Stefan Richter
2006-06-06 16:39     ` Stefan Richter
2006-06-07  7:12       ` Herbert Xu
2006-06-07  7:12         ` Herbert Xu
2006-06-12  6:38         ` Ingo Molnar
2006-06-12  6:38           ` Ingo Molnar
2006-06-12  6:41           ` Herbert Xu
2006-06-12  6:41             ` Herbert Xu
2006-06-12  6:57             ` [patch] undo AF_UNIX _bh locking changes and split lock-type instead Ingo Molnar
2006-06-12  6:57               ` Ingo Molnar
2006-06-12  7:03               ` Herbert Xu
2006-06-12  7:03                 ` Herbert Xu
2006-06-12  7:18                 ` David Miller
2006-06-12  7:18                   ` David Miller
2006-06-12  8:49               ` Ingo Molnar
2006-06-12  8:49                 ` Ingo Molnar
2006-06-12 20:08                 ` David Miller
2006-06-12 20:08                   ` David Miller
2006-06-12  6:50           ` 2.6.17-rc5-mm3-lockdep - David Miller
2006-06-06 13:01   ` Valdis.Kletnieks
2006-06-06 13:45     ` Jiri Slaby

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=44852819.2080503@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.