From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Liwei <xieliwei@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: BUG: scheduling while atomic: xenwatch
Date: Tue, 12 Jul 2011 09:50:41 -0400 [thread overview]
Message-ID: <20110712135041.GA7584@dumpdata.com> (raw)
In-Reply-To: <BANLkTi=VTRuGSroJ8Gf9hYPkP4w+HxnGKg@mail.gmail.com>
On Wed, Jun 29, 2011 at 09:24:20PM +0800, Liwei wrote:
> Hello list,
> I've been receiving these bug traces in my kernel logs since
> switching from Debian's kernel/xen packages to compiling my own
> kernel/xen. They don't seem to cause any visible trouble so I didn't
> bother to report them before, but I thought I'd report them today. The
> bug traces do not occur when using Debian packages.
Thanks for reporting it. I've a patch for it ready.
What tree did you pull from?
>
> [ 1423.038710] Pid: 31, comm: xenwatch Not tainted
> 3.0.0-rc4-custom-xen-amd64+ #1
> [ 1423.038713] Call Trace:
> [ 1423.038718] [<ffffffff8131bd1d>] ? __schedule_bug+0x3e/0x52
> [ 1423.038722] [<ffffffff8132153a>] ? schedule+0x90/0x64e
> [ 1423.038727] [<ffffffff81006b4d>] ? xen_force_evtchn_callback+0x9/0xa
> [ 1423.038732] [<ffffffff810071b2>] ? check_events+0x12/0x20
> [ 1423.038737] [<ffffffff811fcfd5>] ? read_reply+0xa4/0x123
> [ 1423.038742] [<ffffffff8106060f>] ? add_wait_queue+0x3c/0x3c
> [ 1423.038747] [<ffffffff811fd0f9>] ? xs_talkv+0xa5/0x167
> [ 1423.038752] [<ffffffff811fd61a>] ? xenbus_write+0x73/0x94
> [ 1423.038756] [<ffffffff811fd6d6>] ? xenbus_printf+0x9b/0xbf
> [ 1423.038761] [<ffffffff811b8927>] ? xen_pcibk_publish_pci_dev+0xa2/0xa2
> [ 1423.038766] [<ffffffff811b8a4a>] ? xen_pcibk_publish_pci_root+0x123/0x180
> [ 1423.038771] [<ffffffff810e5f99>] ? virt_to_head_page+0x6/0x29
> [ 1423.038775] [<ffffffff811fd6e2>] ? xenbus_printf+0xa7/0xbf
> [ 1423.038780] [<ffffffff811ba648>] ? xen_pcibk_publish_pci_roots+0x7f/0xab
> [ 1423.038785] [<ffffffff811b8d56>] ? xen_pcibk_setup_backend+0x1e4/0x252
> [ 1423.038791] [<ffffffff811b9258>] ? xen_pcibk_xenbus_probe+0xde/0xfe
> [ 1423.038795] [<ffffffff811fe2ce>] ? xenbus_dev_probe+0x6f/0xf6
> [ 1423.038800] [<ffffffff81230589>] ? driver_probe_device+0xa8/0x138
> [ 1423.038805] [<ffffffff81230688>] ? __driver_attach+0x6f/0x6f
> [ 1423.038810] [<ffffffff8122f617>] ? bus_for_each_drv+0x47/0x7b
> [ 1423.038814] [<ffffffff812304aa>] ? device_attach+0x6f/0x8f
> [ 1423.038818] [<ffffffff8122fddb>] ? bus_probe_device+0x1f/0x37
> [ 1423.038823] [<ffffffff8122e771>] ? device_add+0x3e7/0x587
> [ 1423.038828] [<ffffffff8103f759>] ? get_parent_ip+0x9/0x1b
> [ 1423.038832] [<ffffffff812371b9>] ? pm_runtime_init+0xb5/0xc9
> [ 1423.038837] [<ffffffff811fe5f8>] ? xenbus_probe_node+0x137/0x1d5
> [ 1423.038842] [<ffffffff811fe81e>] ? xenbus_dev_changed+0x157/0x189
> [ 1423.038847] [<ffffffff8103f759>] ? get_parent_ip+0x9/0x1b
> [ 1423.038852] [<ffffffff811fcf00>] ? xenwatch_thread+0xf5/0x126
> [ 1423.038856] [<ffffffff8106060f>] ? add_wait_queue+0x3c/0x3c
> [ 1423.038861] [<ffffffff811fce0b>] ? xenbus_thread+0x211/0x211
> [ 1423.038865] [<ffffffff8105ff6e>] ? kthread+0x76/0x7e
> [ 1423.038869] [<ffffffff813295a4>] ? kernel_thread_helper+0x4/0x10
> [ 1423.038874] [<ffffffff813286b3>] ? int_ret_from_sys_call+0x7/0x1b
> [ 1423.038879] [<ffffffff813233e5>] ? retint_restore_args+0x5/0x6
> [ 1423.038883] [<ffffffff813295a0>] ? gs_change+0x13/0x13
> [ 1423.039097] BUG: scheduling while atomic: xenwatch/31/0x00000002
> [ 1423.039147] Modules linked in: tun xt_physdev iptable_filter
> ip_tables x_tables parport_pc ppdev lp parport bluetooth rfkill
> cpufreq_userspace cpufreq_pow
> ersave cpufreq_stats cpufreq_conservative mperf binfmt_misc fuse nfsd
> exportfs nfs lockd fscache auth_rpcgss nfs_acl sunrpc bridge stp ext3
> jbd loop firewire
> _sbp2 firewire_core crc_itu_t cxgb3 mdio i2c_i801 i2c_core mxm_wmi
> psmouse evdev pcspkr serio_raw thermal_sys wmi button acpi_processor
> ext4 mbcache jbd2 crc
> 16 dm_mod sg sd_mod sr_mod crc_t10dif cdrom ahci libahci mvsas libsas
> sky2 libata scsi_transport_sas scsi_mod [last unloaded:
> scsi_wait_scan]
>
> Haven't really checked and confirmed, but they seem to occur on
> starting and stopping VMs.
> Xen:
> # hg log|head
> changeset: 23632:33717472f37e
> tag: tip
> user: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> date: Tue Jun 28 18:15:44 2011 +0100
> summary: libxc: Squash xc_e820.h (and delete) into xenctrl.h
>
> Kernel:
> # git log|head
> commit 3dc33d5af47bd3e216f71f47f1f4c7ea4578cca4
> Merge: bd687c5 bccaeaf
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date: Thu Jun 23 17:10:21 2011 -0700
>
> Liwei
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-07-12 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:24 BUG: scheduling while atomic: xenwatch Liwei
2011-07-12 13:50 ` Konrad Rzeszutek Wilk [this message]
2011-07-12 18:57 ` Liwei
2011-07-12 19:04 ` Konrad Rzeszutek Wilk
2011-07-12 19:29 ` Liwei
2011-07-12 19:54 ` Konrad Rzeszutek Wilk
2011-07-14 15:44 ` Liwei
2011-07-14 17:46 ` Konrad Rzeszutek Wilk
2011-07-15 19:23 ` Liwei
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=20110712135041.GA7584@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xieliwei@gmail.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.