linux-um archives
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: "user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] BUG: spinlock recursion on CPU#0, rngd/1062
Date: Thu, 30 May 2013 12:33:15 +0200	[thread overview]
Message-ID: <51A72AEB.1000602@gmx.de> (raw)

While fuzzying an UML I do often observes it at a 32 bit stable Gentoo Linux (host and guest have kernel 3.10-rc3) :

Because I do not fuzzying the host kernel - just an UML (or a chrooted image),
I'm unsure if this is a kernel issue or just specific to UML.


2013-05-30T12:26:56.962+02:00 trinity kernel: BUG: spinlock recursion on CPU#0, rngd/1062
2013-05-30T12:26:56.962+02:00 trinity kernel: lock: 0x85b94ac, .magic: dead4ead, .owner: rngd/1062, .owner_cpu: 0
2013-05-30T12:26:56.962+02:00 trinity kernel: CPU: 0 PID: 1062 Comm: rngd Not tainted 3.10.0-rc3-00003-g3316c72 #1
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b76d0 085b7700 0841489f 084ddfc4 085b94ac dead4ead 485c25b0 00000426 
2013-05-30T12:26:56.962+02:00 trinity kernel: 00000000 085b0000 085b94ac 084ddea4 085b7710 084148c1 085b94ac 00000008 
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b7730 082a354e 085b7724 08070a8e 085b0000 00000000 00000008 00000000 085b76a4:  [<0805f98f>] show_stack+0xcf/0x100
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b76c8:  [<0841478e>] dump_stack+0x26/0x28
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b76d8:  [<0841489f>] spin_dump+0xa5/0xac
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b7704:  [<084148c1>] spin_bug+0x1b/0x1f
2013-05-30T12:26:56.962+02:00 trinity kernel: 085b7714:  [<082a354e>] do_raw_spin_lock+0x4e/0x100
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7734:  [<08417ec1>] _raw_spin_lock+0x11/0x20
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7740:  [<0805f4b2>] sigio_lock+0x12/0x20
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b774c:  [<08070164>] add_sigio_fd+0x14/0x100
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7774:  [<0805da0a>] reactivate_fd+0x6a/0x80
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7790:  [<0805f427>] sigio_interrupt+0x37/0x40
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b77a8:  [<080c732f>] handle_irq_event_percpu+0x2f/0x150
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b77d8:  [<080c748a>] handle_irq_event+0x3a/0x60
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b77f4:  [<080c98a0>] handle_edge_irq+0xe0/0x110
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7808:  [<080c6cdb>] generic_handle_irq+0x2b/0x30
2013-05-30T12:26:56.963+02:00 trinity kernel: 085b7818:  [<0805db05>] do_IRQ+0x25/0x40
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b7828:  [<0805db85>] sigio_handler+0x65/0x80
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b7840:  [<080709e8>] sig_handler_common+0xb8/0xe0
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b7ac4:  [<08070b2d>] sig_handler+0x3d/0x50
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b7ad4:  [<0807067b>] hard_handler+0x6b/0xa0
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b7afc:  [<b778740c>] 0xb778740c
2013-05-30T12:26:56.965+02:00 trinity kernel: 
2013-05-30T12:26:56.965+02:00 trinity kernel: BUG: spinlock lockup suspected on CPU#0, rngd/1062
2013-05-30T12:26:56.965+02:00 trinity kernel: lock: 0x85b94ac, .magic: dead4ead, .owner: rngd/1062, .owner_cpu: 0
2013-05-30T12:26:56.965+02:00 trinity kernel: CPU: 0 PID: 1062 Comm: rngd Not tainted 3.10.0-rc3-00003-g3316c72 #1
2013-05-30T12:26:56.965+02:00 trinity kernel: 085b76e0 085b7710 0841489f 084ddfc4 085b94ac dead4ead 485c25b0 00000426 
2013-05-30T12:26:56.968+02:00 trinity kernel: 00000000 085b0000 085b94ac 50528000 085b7730 082a35c9 00000001 50528000 
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b0000 00000000 00000008 00000000 085b773c 08417ec1 085b94ac 085b7748 085b76b4:  [<0805f98f>] show_stack+0xcf/0x100
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b76d8:  [<0841478e>] dump_stack+0x26/0x28
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b76e8:  [<0841489f>] spin_dump+0xa5/0xac
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b7714:  [<082a35c9>] do_raw_spin_lock+0xc9/0x100
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b7734:  [<08417ec1>] _raw_spin_lock+0x11/0x20
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b7740:  [<0805f4b2>] sigio_lock+0x12/0x20
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b774c:  [<08070164>] add_sigio_fd+0x14/0x100
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b7774:  [<0805da0a>] reactivate_fd+0x6a/0x80
2013-05-30T12:26:56.968+02:00 trinity kernel: 085b7790:  [<0805f427>] sigio_interrupt+0x37/0x40
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b77a8:  [<080c732f>] handle_irq_event_percpu+0x2f/0x150
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b77d8:  [<080c748a>] handle_irq_event+0x3a/0x60
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b77f4:  [<080c98a0>] handle_edge_irq+0xe0/0x110
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7808:  [<080c6cdb>] generic_handle_irq+0x2b/0x30
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7818:  [<0805db05>] do_IRQ+0x25/0x40
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7828:  [<0805db85>] sigio_handler+0x65/0x80
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7840:  [<080709e8>] sig_handler_common+0xb8/0xe0
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7ac4:  [<08070b2d>] sig_handler+0x3d/0x50
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7ad4:  [<0807067b>] hard_handler+0x6b/0xa0
2013-05-30T12:26:56.969+02:00 trinity kernel: 085b7afc:  [<b778740c>] 0xb778740c
2013-05-30T12:26:57.007+02:00 trinity kernel: 

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

                 reply	other threads:[~2013-05-30 10:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51A72AEB.1000602@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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