|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] 4.0-rc9-pre/xen-next: BUG: scheduling while atomic: xenwatch
Hi,
I've got a machine running 4.0-rc9-pre with xen-next kernel. During boot-up i
see the following message repeated several times, is this harmful? Can i do
anything about it?
If you like more info, just let me know.
Regards,
Mark.
BUG: scheduling while atomic: xenwatch/23/0x00000003
INFO: lockdep is turned off.
Modules linked in: radeon ttm drm_kms_helper drm joydev hidp rfcomm sco bnep
l2cap tun xt_physdev vboxnetadp vboxnetflt vboxdrv dummy bridge stp llc cx8800
cx88xx bttv ir_common lirc_i2c lirc_dev autofs4 ipv6 nfsd exportfs nfs
tda18271 tda10048 lockd fscache nfs_acl auth_rpcgss wm8775 tea5767
tuner_simple tuner_types tda9887 tda8290 snd_hda_codec_atihdmi tuner
snd_hda_codec_via cx25840 snd_hda_intel msp3400 snd_hda_codec cx23885 saa7127
snd_pcm_oss sunrpc snd_mixer_oss videobuf_dma_sg snd_hwdep videobuf_dvb
snd_seq_dummy snd_pcm saa7115 snd_seq_oss dvb_core snd_seq_midi ivtv
snd_rawmidi i2c_algo_bit cx2341x snd_seq_midi_event v4l2_common snd_seq
videobuf_core videodev snd_timer v4l1_compat btcx_risc snd_seq_device btusb
v4l2_compat_ioctl32 8250_pnp snd tveeprom asix soundcore asus_atk0110
bluetooth snd_page_alloc i2c_core usbnet 8250 hwmon shpchp serial_core raid10
raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy
async_tx multipath linear fuse raid0 raid1 ata_generic pata_acpi r8169 mii
pata_jmicron
Pid: 23, comm: xenwatch Tainted: G W 2.6.32mh23 #3
Call Trace:
[<ffffffff8104ee00>] __schedule_bug+0x77/0x7c
[<ffffffff8147a611>] schedule+0xd5/0x849
[<ffffffff8100ea71>] ? xen_force_evtchn_callback+0xd/0xf
[<ffffffff8100f362>] ? check_events+0x12/0x20
[<ffffffff8107c3a8>] ? prepare_to_wait+0x58/0x61
[<ffffffff8147d448>] ? _spin_unlock_irqrestore+0x70/0x7e
[<ffffffff812c33fa>] read_reply+0xa1/0x11e
[<ffffffff8107c13e>] ? autoremove_wake_function+0x0/0x39
[<ffffffff812c35ef>] xs_talkv+0xb2/0x174
[<ffffffff8124b375>] ? kasprintf+0x38/0x3b
[<ffffffff812c37f6>] xs_single+0x3a/0x3c
[<ffffffff812c3ea5>] xenbus_read+0x42/0x5b
[<ffffffff812c3ffd>] xenbus_scanf+0x22/0x75
[<ffffffff81249790>] ? snprintf+0x34/0x36
[<ffffffff812ca444>] pciback_publish_pci_root+0xe6/0x242
[<ffffffff8108fc10>] ? lock_acquired+0x255/0x264
[<ffffffff812ccc02>] ? pciback_publish_pci_roots+0x2c/0xc3
[<ffffffff812c0202>] ? xen_evtchn_do_upcall+0x11a/0x1ec
[<ffffffff812ca35e>] ? pciback_publish_pci_root+0x0/0x242
[<ffffffff812ccc68>] pciback_publish_pci_roots+0x92/0xc3
[<ffffffff812ca97c>] pciback_setup_backend+0x239/0x2e6
[<ffffffff812c3f91>] ? xenbus_gather+0xd3/0x11d
[<ffffffff812caa55>] pciback_be_watch+0x2c/0x30
[<ffffffff812cb2f8>] pciback_xenbus_probe+0x1ae/0x1fa
[<ffffffff812c49ee>] xenbus_dev_probe+0xb8/0x17c
[<ffffffff813099f8>] driver_probe_device+0xde/0x1fe
[<ffffffff81309bd3>] __device_attach+0x3a/0x3f
[<ffffffff81309b99>] ? __device_attach+0x0/0x3f
[<ffffffff81308b97>] bus_for_each_drv+0x59/0x90
[<ffffffff81309c6d>] device_attach+0x66/0x7d
[<ffffffff813089ab>] bus_probe_device+0x27/0x3e
[<ffffffff81307025>] device_add+0x3b4/0x55f
[<ffffffff8124d9fd>] ? __spin_lock_init+0x31/0x54
[<ffffffff813071ee>] device_register+0x1e/0x22
[<ffffffff812c4ea7>] xenbus_probe_node+0x129/0x1cf
[<ffffffff812c50a8>] xenbus_dev_changed+0x15b/0x18b
[<ffffffff8100f34f>] ? xen_restore_fl_direct_end+0x0/0x1
[<ffffffff8109002d>] ? lock_release+0x1ac/0x1b9
[<ffffffff8124d84f>] ? _raw_spin_unlock+0x8f/0x98
[<ffffffff812c5177>] backend_changed+0x3b/0x5b
[<ffffffff812c331e>] xenwatch_thread+0x111/0x14c
[<ffffffff8107c13e>] ? autoremove_wake_function+0x0/0x39
[<ffffffff812c320d>] ? xenwatch_thread+0x0/0x14c
[<ffffffff8107be20>] kthread+0x7f/0x87
[<ffffffff81013e9a>] child_rip+0xa/0x20
[<ffffffff810137d4>] ? restore_args+0x0/0x30
[<ffffffff8100f362>] ? check_events+0x12/0x20
[<ffffffff8100f362>] ? check_events+0x12/0x20
[<ffffffff81013e90>] ? child_rip+0x0/0x20
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] 4.0-rc9-pre/xen-next: BUG: scheduling while atomic: xenwatch,
Mark Hurenkamp <=
|
|
|
|
|