From: Abhinav Srivastava <abhinavs_iitkgp@yahoo.co.in>
To: xen-devel@lists.xensource.com
Subject: BUG: soft lockup detected on CPU#0!
Date: Mon, 10 Sep 2007 03:14:04 +0100 (BST) [thread overview]
Message-ID: <87549.77530.qm@web7902.mail.in.yahoo.com> (raw)
Hi there,
I am using Xen 3.0.3 testing and getting following
error in domU while doing large copy:
#time cp -R linux-2.6.18 linux-cp
BUG: soft lockup detected on CPU#0!
Pid: 998, comm: cp
EIP: 0061:[<c0101227>] CPU: 0
EIP is at 0xc0101227
EFLAGS: 00000286 Not tainted (2.6.16.29-xen #52)
EAX: 00000000 EBX: deadbeef ECX: deadbeef EDX:
c056dc40
ESI: 0000055e EDI: bf874000 EBP: c7b6a000 DS: 007b ES:
007b
CR0: 8005003b CR2: 08061494 CR3: 07204000 CR4:
00000640
[<c010693b>] sysxenentrynotifier+0x3b/0x50
[<c0104f8c>] syscall_call+0xa/0x16
sysxenentrynotifier is my function, which i call from
system call handler to intercept system calls. I am
also logging events inside xen and passing it to dom0
using shared memory setup between dom0 and Xen. When I
copy events to dom0, I pause domU for sometime using
function set_bit(VCPUF_blocked) and and then i
un-pause it using clead_bit(VCPUF_blocked).
Copy operation runs fine for sometime but after that
domU gets hung and when I press any key in domU, it
throws above mentioned error.
If I try to perform the same operation but my logging
code disabled, it works fine. Is it the problem
related to my code or some Xen problem, which gets
enabled when I pause or unpause domU.
Any help or pointers in this regard would be very much
appreciated.
Thanks,
Abhinav
Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/
next reply other threads:[~2007-09-10 2:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 2:14 Abhinav Srivastava [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 22:54 BUG: soft lockup detected on CPU#0! Luke S Crawford
2007-07-25 19:41 Christoph Pfister
2007-07-27 19:30 ` Michal Piotrowski
2007-07-27 20:04 ` Christoph Pfister
2007-08-07 8:49 ` Christoph Pfister
2007-07-14 11:19 CIJOML
2007-06-19 14:34 Hannes Dorbath
2007-06-20 3:29 ` David Chinner
2007-05-09 12:41 Ralf Hildebrandt
2006-06-06 13:06 robee
2006-06-02 1:02 Marc Koschewski
2006-06-02 1:04 ` Marc Koschewski
2006-06-02 1:54 ` Andrew Morton
2006-05-11 17:33 Linux 2.6.16.16 Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-04-05 2:39 Christopher S. Aker
2006-04-05 2:45 ` Itamar Reis Peixoto
2006-04-05 10:16 ` Keir Fraser
2006-04-05 18:32 ` Christopher S. Aker
2006-04-06 6:56 ` Keir Fraser
2006-04-06 9:23 ` Keir Fraser
2006-03-05 12:26 Norbert Wegener
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=87549.77530.qm@web7902.mail.in.yahoo.com \
--to=abhinavs_iitkgp@yahoo.co.in \
--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.