From: Brendan Cully <brendan@cs.ubc.ca>
To: Lily Huang <ushuanglily@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: help on debugging kernel module in Xen
Date: Fri, 12 Jan 2007 13:41:18 -0800 [thread overview]
Message-ID: <20070112214118.GF4982@ventoux.cs.ubc.ca> (raw)
In-Reply-To: <4d616cca0701121332p5787be2erc1a003d4e6e4e55c@mail.gmail.com>
On Friday, 12 January 2007 at 16:32, Lily Huang wrote:
> Hi Brendan,
>
> You are right. After I lift the breakpoint a little bit (to sys_open), the
> breakpoint works.
>
> But now the domU kept complaining after I did "target remote 127.0.0.1:9999"
> and then "br sys_open":
>
> /************************************************?
> BUG: soft lockup detected on CPU#0!
>
> Pid: 0, comm: swapper
> EIP: 0061:[<c01013a7>] CPU: 0
> EIP is at 0xc01013a7
> EFLAGS: 00000346 Not tainted (2.6.16.33-xenU #12)
> EAX: 00000000 EBX: 00000001 ECX: 00000000 EDX: 00000000
> ESI: 00000001 EDI: c0354000 EBP: c0355f84 DS: 007b ES: 007b
> CR0: 8005003b CR2: b7f77000 CR3: 1d633000 CR4: 00000640
> [<c0105bb3>] show_trace+0x13/0x20
> [<c0103390>] show_regs+0x190/0x1e0
> [<c013cf48>] softlockup_tick+0x88/0xa0
> [<c0126d45>] do_timer+0x215/0x440
> [<c010858c>] timer_interrupt+0x1bc/0x6a0
> [<c013d09f>] handle_IRQ_event+0x3f/0xd0
> [<c013d1be>] __do_IRQ+0x8e/0xf0
> [<c0106efd>] do_IRQ+0x1d/0x30
> [<c025d2d1>] evtchn_do_upcall+0xa1/0xe0
> [<c0105309>] hypervisor_callback+0x3d/0x48
> [<c01039df>] xen_idle+0x2f/0x60
> [<c0103a82>] cpu_idle+0x72/0xc0
> [<c0102035>] rest_init+0x35/0x40
> [<c035656a>] start_kernel+0x2ea/0x3a0
> [<c010006f>] 0xc010006f
>
> /********************************************************/
>
> What's wrong? Looks like I am really doomed to run into so many weird
> problems. :(
soft lockup gets triggered when the kernel hasn't gotten a timer
interrupt in a while. This tends to happen frequently when the kernel
is being debugged. I think there's a kernel config option to turn this
off, or you can just live with the messages.
next prev parent reply other threads:[~2007-01-12 21:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 18:41 help on debugging kernel module in Xen Lily Huang
2007-01-12 19:20 ` Brendan Cully
2007-01-12 20:25 ` Lily Huang
2007-01-12 20:35 ` Lily Huang
2007-01-12 20:53 ` Brendan Cully
2007-01-12 21:07 ` Lily Huang
2007-01-12 21:10 ` Lily Huang
2007-01-12 21:26 ` Brendan Cully
2007-01-12 21:32 ` Lily Huang
2007-01-12 21:41 ` Brendan Cully [this message]
2007-01-12 23:04 ` Lily Huang
2007-01-12 23:20 ` Lily Huang
2007-01-12 23:21 ` Brendan Cully
2007-01-12 21:14 ` Brendan Cully
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=20070112214118.GF4982@ventoux.cs.ubc.ca \
--to=brendan@cs.ubc.ca \
--cc=ushuanglily@gmail.com \
--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.