From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: xen-devel@lists.xensource.com
Subject: Re: kernel BUG at arch/x86/xen/mmu.c:1860!
Date: Wed, 09 Mar 2011 01:06:39 +0100 [thread overview]
Message-ID: <4D76C48F.2050006@leuphana.de> (raw)
In-Reply-To: <1299617407852-3414620.post@n5.nabble.com>
[-- Attachment #1.1: Type: text/plain, Size: 5206 bytes --]
Well, this is too bad.
I encountered this bug when xen 4.0 was released, around the time
development on 2.6.31 was halted.
That is why i stuck with 2.6.31 when everyone else went with 2.6.32,
because i determined 2.6.32 was not fit for duty and im guessing it
still isnt today.
The bug occures on 2.6.32 xen kernels ( maybe even newer ones) and is
distribution unrelated, i was running debian 5.0 then, i am running 6.0
testing now and even have tried compiling all the userland stuff myself.
This is error can be encountered during a number of different actions:
1.) any action with lvm (start, stop, create, delete)
2.) while starting multipathd (restarting too, of course)
Sometimes the box only hangs there and no further device mapper
interactions are possible. This is where i got my syslog entry from.
Back in 2010 i had to serial console the server and stuff like that to
see the whole error.
my guess is everything one does with the device mapper can and will
trigger this sooner or later.
Does anybody have any kind of insight on what the problem may be?
------------
Here is my syslog part when i ran "/etc/init.d/multipath-tools restart":
Mar 9 00:24:10 memoryana multipathd: mpatha: stop event checker thread
(140606587918080)
Mar 9 00:24:10 memoryana multipathd: mpathb: stop event checker thread
(140606587885312)
Mar 9 00:24:10 memoryana multipathd: mpathc: stop event checker thread
(140606587852544)
Mar 9 00:24:10 memoryana kernel: ------------[ cut here ]------------
Mar 9 00:24:10 memoryana kernel: kernel BUG at arch/x86/xen/mmu.c:1872!
Mar 9 00:24:10 memoryana kernel: invalid opcode: 0000 [#1] SMP
Mar 9 00:24:10 memoryana kernel: last sysfs file:
/sys/devices/pci0000:00/0000:00:07.0/0000:04:00.1/host3/rport-3:0-2/target3:0:2/3:0:2:0/state
Mar 9 00:24:10 memoryana kernel: CPU 1
Mar 9 00:24:10 memoryana kernel: Modules linked in: dm_round_robin
dm_multipath qla2xxx
Mar 9 00:24:10 memoryana kernel: Pid: 10662, comm: multipath-tools Not
tainted 2.6.32.28-xen0 #4 PowerEdge R610
Mar 9 00:24:10 memoryana kernel: RIP: e030:[<ffffffff8100d471>]
[<ffffffff8100d471>] pin_pagetable_pfn+0x31/0x60
Mar 9 00:24:10 memoryana kernel: RSP: e02b:ffff8800c3101df8 EFLAGS:
00010282
Mar 9 00:24:10 memoryana kernel: RAX: 00000000ffffffea RBX:
ffff8800cc4c3400 RCX: 0000000000000003
Mar 9 00:24:10 memoryana kernel: RDX: 0000000000000000 RSI:
0000000000000001 RDI: ffff8800c3101df8
Mar 9 00:24:10 memoryana kernel: RBP: ffff8800c3135b60 R08:
00003ffffffff000 R09: ffff880000000000
Mar 9 00:24:10 memoryana kernel: R10: 0000000000007ff0 R11:
0000000000000246 R12: 00000000000cc302
Mar 9 00:24:10 memoryana kernel: R13: 0000000000000000 R14:
ffff8800c374cc60 R15: ffff8800c374cc60
Mar 9 00:24:10 memoryana kernel: FS: 00007f60add15700(0000)
GS:ffff880028055000(0000) knlGS:0000000000000000
Mar 9 00:24:10 memoryana kernel: CS: e033 DS: 0000 ES: 0000 CR0:
000000008005003b
Mar 9 00:24:10 memoryana kernel: CR2: 00007f60ad841876 CR3:
00000000cef79000 CR4: 0000000000002660
Mar 9 00:24:10 memoryana kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Mar 9 00:24:10 memoryana kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Mar 9 00:24:10 memoryana kernel: Process multipath-tools (pid: 10662,
threadinfo ffff8800c3100000, task ffff8800cc01cbc0)
Mar 9 00:24:10 memoryana kernel: Stack:
Mar 9 00:24:10 memoryana kernel: 0000000000000000 00000000008e8302
ffff8800cc4c3400 ffff8800c3135b60
Mar 9 00:24:10 memoryana kernel: <0> 00000000000cc302 ffffffff810b0382
00007f60ad841876 ffff8800c30b4c10
Mar 9 00:24:10 memoryana kernel: <0> 00000000000100e0 0000000000000000
ffff8800c374cc60 ffffffff810b3595
Mar 9 00:24:10 memoryana kernel: Call Trace:
Mar 9 00:24:10 memoryana kernel: [<ffffffff810b0382>] ?
__pte_alloc+0xf2/0x120
Mar 9 00:24:10 memoryana kernel: [<ffffffff810b3595>] ?
handle_mm_fault+0xa45/0xab0
Mar 9 00:24:10 memoryana kernel: [<ffffffff8153cfe5>] ?
page_fault+0x25/0x30
Mar 9 00:24:10 memoryana kernel: [<ffffffff8153d21a>] ?
error_exit+0x2a/0x60
Mar 9 00:24:10 memoryana kernel: [<ffffffff8101481d>] ?
retint_restore_args+0x5/0x6
Mar 9 00:24:10 memoryana kernel: [<ffffffff81038631>] ?
do_page_fault+0x121/0x3c0
Mar 9 00:24:10 memoryana kernel: [<ffffffff812a2e0d>] ?
__put_user_4+0x1d/0x30
Mar 9 00:24:10 memoryana kernel: [<ffffffff8153cfe5>] ?
page_fault+0x25/0x30
Mar 9 00:24:10 memoryana kernel: Code: 57 c7 75 00 00 48 89 f0 89 3c 24
74 27 48 89 44 24 08 48 89 e7 be 01 00 00 00 31 d2 41 ba f0 7f 00 00 e8
d3 be ff ff 85 c0 74 04 <0f> 0b eb fe 48 83 c4 28 c3 48 89 f7 e8 6e f7
ff ff 48 83 f8 ff
Mar 9 00:24:10 memoryana kernel: RIP [<ffffffff8100d471>]
pin_pagetable_pfn+0x31/0x60
Mar 9 00:24:10 memoryana kernel: RSP <ffff8800c3101df8>
Mar 9 00:24:10 memoryana kernel: ---[ end trace f4eae184c1a9f532 ]---
Mar 9 00:24:11 memoryana multipathd: --------shut down-------
--
Andreas Olsowski
Leuphana Universität Lüneburg
Rechen- und Medienzentrum
Scharnhorststraße 1, C7.015
21335 Lüneburg
Tel: ++49 4131 677 1309
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-09 0:06 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 8:16 kernel BUG at arch/x86/xen/mmu.c:1860! Teck Choon Giam
2010-12-27 15:53 ` Konrad Rzeszutek Wilk
2010-12-27 22:14 ` Teck Choon Giam
2010-12-28 10:42 ` Pasi Kärkkäinen
2010-12-28 18:01 ` Teck Choon Giam
2010-12-29 4:25 ` Teck Choon Giam
2010-12-29 4:58 ` Teck Choon Giam
2011-01-14 15:20 ` Konrad Rzeszutek Wilk
2011-01-14 19:25 ` Teck Choon Giam
2011-01-14 19:44 ` Konrad Rzeszutek Wilk
2011-01-14 20:09 ` Teck Choon Giam
2011-01-14 20:32 ` Teck Choon Giam
2011-01-24 1:42 ` Teck Choon Giam
2011-01-24 14:36 ` Konrad Rzeszutek Wilk
2011-01-24 15:56 ` Teck Choon Giam
2011-01-25 14:48 ` Konrad Rzeszutek Wilk
2011-01-26 14:31 ` Konrad Rzeszutek Wilk
2011-01-27 17:17 ` Teck Choon Giam
2011-01-27 20:32 ` Konrad Rzeszutek Wilk
2011-01-27 22:20 ` Teck Choon Giam
2011-02-26 12:03 ` Teck Choon Giam
2011-02-28 16:20 ` Konrad Rzeszutek Wilk
2011-03-01 9:59 ` Teck Choon Giam
2011-03-03 22:16 ` Konrad Rzeszutek Wilk
2011-03-04 5:30 ` Teck Choon Giam
2011-03-04 6:15 ` Fajar A. Nugraha
2011-03-04 6:33 ` Teck Choon Giam
2011-03-08 19:29 ` Konrad Rzeszutek Wilk
2011-03-08 20:10 ` Konrad Rzeszutek Wilk
2011-03-08 20:20 ` Teck Choon Giam
2011-03-08 20:45 ` Guido Hecken
2011-03-08 20:50 ` [SPAM] " tjaouen
2011-03-09 0:06 ` Andreas Olsowski [this message]
2011-03-11 18:38 ` benco
2011-03-11 19:59 ` Sander Eikelenboom
2011-03-11 20:29 ` Teck Choon Giam
2011-03-11 20:45 ` Teck Choon Giam
2011-03-11 21:02 ` Sander Eikelenboom
2011-03-11 21:15 ` Teck Choon Giam
2011-03-09 0:43 ` [SPAM] " Konrad Rzeszutek Wilk
2011-03-09 6:58 ` Andreas Olsowski
2011-03-09 15:00 ` Konrad Rzeszutek Wilk
2011-03-09 19:59 ` Andreas Olsowski
2011-03-10 7:20 ` Andreas Olsowski
2011-03-10 13:45 ` Andreas Olsowski
2011-03-11 18:05 ` Konrad Rzeszutek Wilk
2011-03-14 10:25 ` Ian Campbell
2011-03-14 10:36 ` Teck Choon Giam
2011-03-16 15:52 ` [SPAM] Re: kernel BUG at arch/x86/xen/mmu.c:1860! - ideas Konrad Rzeszutek Wilk
2011-03-16 16:26 ` Teck Choon Giam
2011-03-16 16:40 ` Konrad Rzeszutek Wilk
2011-03-24 11:57 ` Konrad Rzeszutek Wilk
2011-03-24 21:28 ` Teck Choon Giam
2011-03-25 3:57 ` Teck Choon Giam
2011-03-27 10:16 ` Teck Choon Giam
2011-03-28 11:37 ` Andreas Olsowski
2011-03-28 12:29 ` Teck Choon Giam
2011-04-05 22:01 ` Dave Hunter
2011-04-05 22:15 ` Teck Choon Giam
2011-04-05 23:20 ` Dave Hunter
2011-04-06 7:53 ` Ian Campbell
2011-04-06 21:52 ` Jeremy Fitzhardinge
2011-04-07 13:16 ` Teck Choon Giam
2011-03-09 0:41 ` kernel BUG at arch/x86/xen/mmu.c:1860! Konrad Rzeszutek Wilk
2011-01-04 15:10 ` Christophe Saout
2011-01-04 15:19 ` Christophe Saout
2011-01-04 15:37 ` benco
2011-01-04 18:40 ` Christophe Saout
2011-01-04 19:32 ` Teck Choon Giam
2011-01-04 19:56 ` benco
2011-01-14 15:22 ` Konrad Rzeszutek Wilk
2011-01-14 15:33 ` Christophe Saout
2011-01-04 23:10 ` Christophe Saout
2011-01-05 10:51 ` Pasi Kärkkäinen
2011-01-05 14:56 ` Teck Choon Giam
2011-01-14 15:24 ` Konrad Rzeszutek Wilk
2011-01-14 19:31 ` Teck Choon Giam
2011-01-04 13:48 ` Ian Campbell
2011-01-04 19:24 ` Teck Choon Giam
2011-01-05 15:30 ` Teck Choon Giam
2011-01-13 14:28 ` tjaouen
2011-01-14 14:47 ` Konrad Rzeszutek Wilk
[not found] <COL0-MC1-F14hmBzxHs00230882@col0-mc1-f14.Col0.hotmail.com>
2011-04-08 11:24 ` MaoXiaoyun
2011-04-08 11:46 ` MaoXiaoyun
-- strict thread matches above, loose matches on Subject: below --
2011-04-15 7:37 Joerg Stephan
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=4D76C48F.2050006@leuphana.de \
--to=andreas.olsowski@leuphana.de \
--cc=xen-devel@lists.xensource.com \
/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.