All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
	"user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Fwd: Re: [uml-user] WARNING: at mm/slab_common.c:376 kmalloc_slab+0x33/0x80()
Date: Sat, 11 May 2013 15:48:21 +0200	[thread overview]
Message-ID: <518E4C25.2080005@gmx.de> (raw)
In-Reply-To: <CAFLxGvzNEcgwDcB2B1Qpo4isppm6u_w60tzLY0Sah5Sj4T_Q4A@mail.gmail.com>

On 05/11/2013 03:26 PM, richard -rw- weinberger wrote:
> Does the attached patch fix the problem?
yes,

but this occurred (probably completely unrelated :)

2013-05-11T15:42:32.829+02:00 trinity kernel: Adding 262140k swap on /dev/mapper/crypt-swap.  Priority:-1 extents:1 across:262140k FS
2013-05-11T15:42:33.000+02:00 trinity haveged: haveged starting up
2013-05-11T15:42:33.000+02:00 trinity haveged: haveged: Completed tot procedure B after 1171996 bytes
2013-05-11T15:42:35.701+02:00 trinity kernel: BUG: spinlock cpu recursion on CPU#0, kworker/0:2/346
2013-05-11T15:42:35.701+02:00 trinity kernel: lock: 0x40c4a6c0, .magic: dead4ead, .owner: <none>/-1, .owner_cpu: 0
2013-05-11T15:42:35.701+02:00 trinity kernel: CPU: 0 PID: 346 Comm: kworker/0:2 Not tainted 3.9.0-12555-g2dbd3ca-dirty #1
2013-05-11T15:42:35.701+02:00 trinity kernel: Workqueue: events cache_reap
2013-05-11T15:42:35.701+02:00 trinity kernel: 40fa7e50 40fa7e80 0835d6cb 083f28e0 40c4a6c0 dead4ead 083f27a9 ffffffff 
2013-05-11T15:42:35.701+02:00 trinity kernel: 00000000 40fa0000 40c4a6c0 083f27ba 40fa7e90 0835d6ed 40c4a6c0 00000000 
2013-05-11T15:42:35.701+02:00 trinity kernel: 40fa7eb0 08281513 00000000 00000003 40fa0000 40c4a6c0 00000000 40c488c0 40fa7e24:  [<08060cff>] show_stack+0xcf/0x100
2013-05-11T15:42:35.701+02:00 trinity kernel: 40fa7e48:  [<0835d5ba>] dump_stack+0x26/0x28
2013-05-11T15:42:35.701+02:00 trinity kernel: 40fa7e58:  [<0835d6cb>] spin_dump+0xa5/0xac
2013-05-11T15:42:35.701+02:00 trinity kernel: 40fa7e84:  [<0835d6ed>] spin_bug+0x1b/0x1f
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7e94:  [<08281513>] do_raw_spin_lock+0x63/0x100
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7eb4:  [<0835fc96>] _raw_spin_lock_irq+0x16/0x20
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7ec0:  [<080fb1e8>] drain_freelist+0x38/0xf0
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7ef0:  [<080fb35c>] cache_reap+0xbc/0x120
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7f14:  [<08093e20>] process_one_work+0x1c0/0x310
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7f58:  [<0809441a>] worker_thread+0x1fa/0x300
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7f84:  [<08099c82>] kthread+0xc2/0xd0
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7fec:  [<0805f87a>] new_thread_handler+0x7a/0xa0
2013-05-11T15:42:35.702+02:00 trinity kernel: 40fa7ffc:  [<00000000>] 0x0
2013-05-11T15:42:35.702+02:00 trinity kernel: 
2013-05-11T15:42:35.000+02:00 trinity haveged: haveged: Completed tot procedure A after 1035716 bytes
2013-05-11T15:42:35.000+02:00 trinity haveged: haveged: version: 1.5; arch: x86; vendor: GenuineIntel; cores: 1/1, buffer: 128
2013-05-11T15:42:35.000+02:00 trinity haveged: haveged: d_cache: 32K (000020), i_cache: 32K (000020), i_index: 19/40, i_size: 32653/60731
2013-05-11T15:42:35.000+02:00 trinity haveged: haveged: tot tests: BA8, continuous tests: B
2013-05-11T15:42:35.000+02:00 trinity haveged: haveged: Completed continuous procedure B after 1171996 bytes
2013-05-11T15:42:35.000+02:00 trinity dhcpcd[770]: version 5.6.4 starting

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

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2013-05-11 13:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 21:52 WARNING: at mm/slab_common.c:376 kmalloc_slab+0x33/0x80() Toralf Förster
2013-05-11  8:19 ` Toralf Förster
2013-05-11  8:20 ` [uml-user] " richard -rw- weinberger
2013-05-11  8:36   ` [uml-devel] Fwd: " Toralf Förster
2013-05-11  8:47     ` richard -rw- weinberger
2013-05-11  9:51       ` Toralf Förster
2013-05-11 11:01         ` Sergei Trofimovich
2013-05-11 11:29           ` richard -rw- weinberger
2013-05-11 13:26             ` Sergei Trofimovich
2013-05-11 12:26           ` richard -rw- weinberger
2013-05-11 12:27             ` richard -rw- weinberger
2013-05-11 13:19               ` Toralf Förster
2013-05-11 13:26                 ` richard -rw- weinberger
2013-05-11 13:37                   ` richard -rw- weinberger
2013-05-11 13:51                     ` Toralf Förster
2013-05-11 13:48                   ` Toralf Förster [this message]

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=518E4C25.2080005@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=davej@redhat.com \
    --cc=richard.weinberger@gmail.com \
    --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 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.