From: Valtteri Kiviniemi <mailinglists@dataproof.fi>
To: xen-devel@lists.xensource.com
Subject: Xen 3.4.2 kernel / lvcreate crash
Date: Thu, 01 Apr 2010 03:11:14 +0300 [thread overview]
Message-ID: <4BB3E4A2.7000500@dataproof.fi> (raw)
Hi,
I am using Xen 3.4.2 with kernel 2.6.18.8 and Debian Lenny. I am having
some problems with LVM-snapshots. I have crontab which makes once a
night a snapshot from domU's LV.
The problem is that maybe once in a month the lvcreate command stucks
and after that I have to reboot the machine to solve the problem.
So is this a problem on the Xen kernel or with Debian?
dmesg shows the following:
Unable to handle kernel NULL pointer dereference at 0000000000000030 RIP:
[<ffffffff804218a2>] __map_bio+0x45/0x9b
PGD 38057067 PUD 10657067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Pid: 17350, comm: lvcreate Not tainted 2.6.18.8-dom0 #1
RIP: e030:[<ffffffff804218a2>] [<ffffffff804218a2>] __map_bio+0x45/0x9b
RSP: e02b:ffff880028693d68 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001
RDX: ffff8800311bfaf0 RSI: ffff8800219c38c0 RDI: ffffc200000f30d8
RBP: ffff8800311bfae0 R08: 0000000000000001 R09: 001322b628693ce8
R10: 0000000000000001 R11: 00000000006cc4a0 R12: ffff8800219c38c0
R13: fffffffff3800008 R14: ffff88003c56c5d8 R15: ffff8800311bfae0
FS: 00002b35f3f7ac20(0000) GS:ffffffff805ca000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process lvcreate (pid: 17350, threadinfo ffff880028692000, task
ffff88003cc510c0)
Stack: ffff88003f5a0440 0000000000000001 ffff88003c56c5c0 ffff88003c565400
fffffffff3800008 ffffffff804221b5 ffff88003c56c5d8 ffff88003f5a0440
ffff88003c56c5c0 ffff88003c565400 ffff8800252b1f10 ffffffff8025e099
Call Trace:
[<ffffffff804221b5>] __split_bio+0x1a9/0x3f7
[<ffffffff8025e099>] __down_write_nested+0x12/0xf1
[<ffffffff8022fe0e>] __up_write+0x1d/0x115
[<ffffffff804225b9>] dm_resume+0xa1/0x137
[<ffffffff80425158>] dev_suspend+0x0/0x171
[<ffffffff804252a3>] dev_suspend+0x14b/0x171
[<ffffffff80425bb6>] ctl_ioctl+0x1c6/0x20e
[<ffffffff8024012a>] do_ioctl+0x56/0x6c
[<ffffffff8022fddb>] vfs_ioctl+0x23a/0x250
[<ffffffff8024a42f>] sys_ioctl+0x3d/0x5c
[<ffffffff8025a21c>] system_call+0x68/0x6d
[<ffffffff8025a1b4>] system_call+0x0/0x6d
Code: ff 50 30 41 89 c5 83 f8 00 7e 10 4c 89 e7 41 59 5b 5d 41 5c
RIP [<ffffffff804218a2>] __map_bio+0x45/0x9b
RSP <ffff880028693d68>
CR2: 0000000000000030
next reply other threads:[~2010-04-01 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 0:11 Valtteri Kiviniemi [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-01 0:34 Xen 3.4.2 kernel / lvcreate crash Valtteri Kiviniemi
2010-04-01 1:25 ` Jeremy Fitzhardinge
2010-04-01 7:33 ` Valtteri Kiviniemi
2010-04-01 7:46 ` Pasi Kärkkäinen
2010-04-01 18:50 ` Jeremy Fitzhardinge
2010-04-02 21:26 ` Valtteri Kiviniemi
2010-04-02 21:36 ` Jeremy Fitzhardinge
2010-05-15 13:47 ` Valtteri Kiviniemi
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=4BB3E4A2.7000500@dataproof.fi \
--to=mailinglists@dataproof.fi \
--cc=valtteri.kiviniemi@dataproof.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).