ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 8716 bytes --]

Hello DEVs, can anyone help me?

Ian Campbell pointed me that maybe you could help me, here is the link to
the last e-mail line that started this problem fixing:
http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html

A brief summary of my current problems after XEN installation:

First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:

"
xc: error: Could not obtain handle on privileged command interface (2 = No
such file or directory): Internal error
libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle: No
such file or directory
cannot init xl context
"

Second Problem:
My boot.log is showing:

"
[ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
See "systemctl status systemd-modules-load.service" for details.
"

Third Problem:
Today doing an apt-get update and apt-get dist-upgrade to see if there was
any major fix on stuff... and probably I am with a Regression in hands:

"
Error found when loading /etc/profile:
/etc/profile.d/cedilla-brazil.sh: linha 21: [: n?mero excessivo de
argumentos

As a result the session will not be configured correctly
You should fix the problem as soon as feasible.
"

Also trying to run "sudo su -" on terminal I get a message saying I have
too much arguments for (su) but since it appears related to this problem
above, I consider both the same.

***I have already sent an e-mail to the Ubuntu mailing list about this
problem...

Fourth Problem:
I am receiving KERNEL OOPS messages saying my #4 processor is pausing:
"
NMI watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [irq/19-b43:1082]
"
that is a strip from syslog, showing that message:
"
Apr  1 15:01:34 carlos kernel: [ 1829.176231]  [<ffffffff817c5cf5>]
__mutex_lock_slowpath+0x95/0x100
Apr  1 15:01:34 carlos kernel: [ 1829.176233]  [<ffffffff817c5d83>]
mutex_lock+0x23/0x40
Apr  1 15:01:34 carlos kernel: [ 1829.176235]  [<ffffffffc0df47f3>]
b43_periodic_work_handler+0x33/0x190 [b43]
Apr  1 15:01:34 carlos kernel: [ 1829.176237]  [<ffffffff8108eb48>]
process_one_work+0x158/0x430
Apr  1 15:01:34 carlos kernel: [ 1829.176238]  [<ffffffff8108f5db>]
worker_thread+0x5b/0x530
Apr  1 15:01:34 carlos kernel: [ 1829.176239]  [<ffffffff8108f580>] ?
rescuer_thread+0x3a0/0x3a0
Apr  1 15:01:34 carlos kernel: [ 1829.176241]  [<ffffffff81094679>]
kthread+0xc9/0xe0
Apr  1 15:01:34 carlos kernel: [ 1829.176243]  [<ffffffff810945b0>] ?
kthread_create_on_node+0x1c0/0x1c0
Apr  1 15:01:34 carlos kernel: [ 1829.176244]  [<ffffffff817c8198>]
ret_from_fork+0x58/0x90
Apr  1 15:01:34 carlos kernel: [ 1829.176246]  [<ffffffff810945b0>] ?
kthread_create_on_node+0x1c0/0x1c0
Apr  1 15:01:36 carlos thermald[910]: Dropped below poll threshold
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
5:Processor
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
13:intel_powerclamp
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
14:rapl_controller
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
5:Processor
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
13:intel_powerclamp
Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
14:rapl_controller
Apr  1 15:01:40 carlos thermald[910]: Read set point 0
Apr  1 15:01:40 carlos thermald[910]: Set : 94000, 74000, 5, 0, 0
Apr  1 15:01:42 carlos kernel: [ 1837.163940] NMI watchdog: BUG: soft
lockup - CPU#4 stuck for 22s! [irq/19-b43:1082]
Apr  1 15:01:42 carlos kernel: [ 1837.163944] Modules linked in: rfcomm
bnep nls_iso8859_1 arc4 b43 mac80211 cfg80211 snd_hda_codec_hdmi ssb
eeepc_wmi asus_wmi sparse_keymap snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_intel snd_hda_controller intel_rapl iosf_mbi
snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hwdep coretemp
snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uvcvideo
aesni_intel snd_seq_midi videobuf2_vmalloc snd_seq_midi_event btusb
aes_x86_64 videobuf2_memops videobuf2_core lrw snd_rawmidi gf128mul
v4l2_common glue_helper ablk_helper nouveau bluetooth snd_seq cryptd
videodev cypress_m8 media serio_raw joydev snd_seq_device i915 usbserial
snd_timer mxm_wmi bcma lpc_ich ttm drm_kms_helper snd drm mei_me soundcore
mei i2c_algo_bit video intel_smartconnect ie31200_edac wmi shpchp edac_core
mac_hid xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev
xen_evtchn parport_pc ppdev lp parport autofs4 btrfs hid_generic usbhid hid
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
xor raid6_pq e1000e raid1 psmouse ptp r8169 mii raid0 pps_core ahci
multipath libahci linear
Apr  1 15:01:42 carlos kernel: [ 1837.164002] CPU: 4 PID: 1082 Comm:
irq/19-b43 Tainted: G             L 3.19.0-10-generic #10-Ubuntu
Apr  1 15:01:42 carlos kernel: [ 1837.164004] Hardware name: System
manufacturer System Product Name/P8Z77-V DELUXE, BIOS 2104 08/13/2013
Apr  1 15:01:42 carlos kernel: [ 1837.164005] task: ffff8808018809d0 ti:
ffff880802c88000 task.ti: ffff880802c88000
Apr  1 15:01:42 carlos kernel: [ 1837.164006] RIP:
e030:[<ffffffff8101e1b6>]  [<ffffffff8101e1b6>] native_read_tsc+0x6/0x20
Apr  1 15:01:42 carlos kernel: [ 1837.164011] RSP: e02b:ffff880802c8bd00
EFLAGS: 00000246
Apr  1 15:01:42 carlos kernel: [ 1837.164012] RAX: 00000000a08f0862 RBX:
00000000a08ef87e RCX: 00000000a08f082d
Apr  1 15:01:42 carlos kernel: [ 1837.164013] RDX: 00000000000005b2 RSI:
0000000000000000 RDI: 0000000000001a6e
Apr  1 15:01:42 carlos kernel: [ 1837.164013] RBP: ffff880802c8bd00 R08:
0000000000000000 R09: 0000000025ae8d40
Apr  1 15:01:42 carlos kernel: [ 1837.164014] R10: ffff88080d317520 R11:
ffffea001f6f6880 R12: 0000000000001a6e
Apr  1 15:01:42 carlos kernel: [ 1837.164015] R13: 0000000000000004 R14:
ffff8807e5d1f700 R15: ffff8807ffacb780
Apr  1 15:01:42 carlos kernel: [ 1837.164018] FS:  0000000000000000(0000)
GS:ffff88080d300000(0000) knlGS:ffff88080d300000
Apr  1 15:01:42 carlos kernel: [ 1837.164019] CS:  e033 DS: 0000 ES: 0000
CR0: 0000000080050033
Apr  1 15:01:42 carlos kernel: [ 1837.164020] CR2: 00007fc0598b2000 CR3:
0000000001c13000 CR4: 0000000000042660
Apr  1 15:01:42 carlos kernel: [ 1837.164021] Stack:
Apr  1 15:01:42 carlos kernel: [ 1837.164022]  ffff880802c8bd28
ffffffff813c17bb 0000000000000005 000000000000008a
Apr  1 15:01:42 carlos kernel: [ 1837.164023]  ffff88079f729240
ffff880802c8bd38 ffffffff813c16fb ffff880802c8bda8
Apr  1 15:01:42 carlos kernel: [ 1837.164025]  ffffffffc0e223e7
ffffffffc0e47ea0 0000010000000000 ffffffffc0e47ea0
Apr  1 15:01:42 carlos kernel: [ 1837.164026] Call Trace:
Apr  1 15:01:42 carlos kernel: [ 1837.164031]  [<ffffffff813c17bb>]
delay_tsc+0x3b/0x80
Apr  1 15:01:42 carlos kernel: [ 1837.164032]  [<ffffffff813c16fb>]
__const_udelay+0x2b/0x30
Apr  1 15:01:42 carlos kernel: [ 1837.164038]  [<ffffffffc0e223e7>]
b43_dma_rx+0xb7/0x3e0 [b43]
Apr  1 15:01:42 carlos kernel: [ 1837.164042]  [<ffffffff810135ea>] ?
__switch_to+0x15a/0x5f0
Apr  1 15:01:42 carlos kernel: [ 1837.164044]  [<ffffffff810ce2e0>] ?
irq_finalize_oneshot.part.30+0x170/0x170
Apr  1 15:01:42 carlos kernel: [ 1837.164047]  [<ffffffffc0df56ed>]
b43_interrupt_thread_handler+0x3dd/0x660 [b43]
Apr  1 15:01:42 carlos kernel: [ 1837.164049]  [<ffffffff817c337c>] ?
__schedule+0x39c/0x8e0
Apr  1 15:01:42 carlos kernel: [ 1837.164051]  [<ffffffff810ce300>]
irq_thread_fn+0x20/0x50
Apr  1 15:01:42 carlos kernel: [ 1837.164053]  [<ffffffff810ce2e0>] ?
irq_finalize_oneshot.part.30+0x170/0x170
Apr  1 15:01:42 carlos kernel: [ 1837.164054]  [<ffffffff810ce63f>]
irq_thread+0x11f/0x150
Apr  1 15:01:42 carlos kernel: [ 1837.164056]  [<ffffffff810ce3a0>] ?
irq_forced_thread_fn+0x70/0x70
Apr  1 15:01:42 carlos kernel: [ 1837.164058]  [<ffffffff810ce520>] ?
irq_thread_check_affinity+0xd0/0xd0
Apr  1 15:01:42 carlos kernel: [ 1837.164060]  [<ffffffff81094679>]
kthread+0xc9/0xe0
Apr  1 15:01:42 carlos kernel: [ 1837.164062]  [<ffffffff810945b0>] ?
kthread_create_on_node+0x1c0/0x1c0
Apr  1 15:01:42 carlos kernel: [ 1837.164064]  [<ffffffff817c8198>]
ret_from_fork+0x58/0x90
Apr  1 15:01:42 carlos kernel: [ 1837.164065]  [<ffffffff810945b0>] ?
kthread_create_on_node+0x1c0/0x1c0
"


2015-04-01 11:46 GMT-03:00 Ian Campbell <Ian.Campbell@citrix.com>:

> On Wed, 2015-04-01 at 11:23 -0300, Carlos Gustavo Ramirez Rodriguez
> wrote:
> > Anyone among the dev's can be help?
>
> Perhaps, you could report to xen-devel and Cc olaf@aepfle.de and
> mcgrof@suse.com since I think they are the ones most involved in the
> systemd integration for Xen.
>
> Ian.
>
>
>


-- 
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 10279 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Andrew Cooper]

[-- Attachment #1.1: Type: text/plain, Size: 9190 bytes --]

On 01/04/15 19:55, Carlos Gustavo Ramirez Rodriguez wrote:
> Hello DEVs, can anyone help me?
>
> Ian Campbell pointed me that maybe you could help me, here is the link
> to the last e-mail line that started this problem fixing:
> http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html
>
> A brief summary of my current problems after XEN installation:
>
> First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:
>
> "
> xc: error: Could not obtain handle on privileged command interface (2
> = No such file or directory): Internal error
> libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle:
> No such file or directory
> cannot init xl context
> "

You do not have /proc/xen/privcmd available in your environment.  Mount
xenfs

(note to self - dust off my patch which makes that error message more
useful)

>
> Second Problem:
> My boot.log is showing:
>
> "
> [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
> See "systemctl status systemd-modules-load.service" for details.
> "
>

What extra information do you get by following the instruction?

> Third Problem:
> Today doing an apt-get update and apt-get dist-upgrade to see if there
> was any major fix on stuff... and probably I am with a Regression in
> hands:
>
> "
> Error found when loading /etc/profile:
> /etc/profile.d/cedilla-brazil.sh: linha 21: [: n?mero excessivo de
> argumentos
>
> As a result the session will not be configured correctly
> You should fix the problem as soon as feasible.
> "
>
> Also trying to run "sudo su -" on terminal I get a message saying I
> have too much arguments for (su) but since it appears related to this
> problem above, I consider both the same.

I don't see how this could plausibly be a Xen issue.

>
> ***I have already sent an e-mail to the Ubuntu mailing list about this
> problem...
>
> Fourth Problem:
> I am receiving KERNEL OOPS messages saying my #4 processor is pausing:
> "
> NMI watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [irq/19-b43:1082]
> "
> that is a strip from syslog, showing that message:
> "
> Apr  1 15:01:34 carlos kernel: [ 1829.176231]  [<ffffffff817c5cf5>]
> __mutex_lock_slowpath+0x95/0x100
> Apr  1 15:01:34 carlos kernel: [ 1829.176233]  [<ffffffff817c5d83>]
> mutex_lock+0x23/0x40
> Apr  1 15:01:34 carlos kernel: [ 1829.176235]  [<ffffffffc0df47f3>]
> b43_periodic_work_handler+0x33/0x190 [b43]
> Apr  1 15:01:34 carlos kernel: [ 1829.176237]  [<ffffffff8108eb48>]
> process_one_work+0x158/0x430
> Apr  1 15:01:34 carlos kernel: [ 1829.176238]  [<ffffffff8108f5db>]
> worker_thread+0x5b/0x530
> Apr  1 15:01:34 carlos kernel: [ 1829.176239]  [<ffffffff8108f580>] ?
> rescuer_thread+0x3a0/0x3a0
> Apr  1 15:01:34 carlos kernel: [ 1829.176241]  [<ffffffff81094679>]
> kthread+0xc9/0xe0
> Apr  1 15:01:34 carlos kernel: [ 1829.176243]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:34 carlos kernel: [ 1829.176244]  [<ffffffff817c8198>]
> ret_from_fork+0x58/0x90
> Apr  1 15:01:34 carlos kernel: [ 1829.176246]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:36 carlos thermald[910]: Dropped below poll threshold
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 5:Processor
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 13:intel_powerclamp
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 14:rapl_controller
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 5:Processor
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 13:intel_powerclamp
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 14:rapl_controller
> Apr  1 15:01:40 carlos thermald[910]: Read set point 0
> Apr  1 15:01:40 carlos thermald[910]: Set : 94000, 74000, 5, 0, 0
> Apr  1 15:01:42 carlos kernel: [ 1837.163940] NMI watchdog: BUG: soft
> lockup - CPU#4 stuck for 22s! [irq/19-b43:1082]
> Apr  1 15:01:42 carlos kernel: [ 1837.163944] Modules linked in:
> rfcomm bnep nls_iso8859_1 arc4 b43 mac80211 cfg80211
> snd_hda_codec_hdmi ssb eeepc_wmi asus_wmi sparse_keymap
> snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel
> snd_hda_controller intel_rapl iosf_mbi snd_hda_codec
> x86_pkg_temp_thermal intel_powerclamp snd_hwdep coretemp snd_pcm
> crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uvcvideo aesni_intel
> snd_seq_midi videobuf2_vmalloc snd_seq_midi_event btusb aes_x86_64
> videobuf2_memops videobuf2_core lrw snd_rawmidi gf128mul v4l2_common
> glue_helper ablk_helper nouveau bluetooth snd_seq cryptd videodev
> cypress_m8 media serio_raw joydev snd_seq_device i915 usbserial
> snd_timer mxm_wmi bcma lpc_ich ttm drm_kms_helper snd drm mei_me
> soundcore mei i2c_algo_bit video intel_smartconnect ie31200_edac wmi
> shpchp edac_core mac_hid xen_pciback xen_netback xen_blkback
> xen_gntalloc xen_gntdev xen_evtchn parport_pc ppdev lp parport autofs4
> btrfs hid_generic usbhid hid raid10 raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq e1000e raid1
> psmouse ptp r8169 mii raid0 pps_core ahci multipath libahci linear
> Apr  1 15:01:42 carlos kernel: [ 1837.164002] CPU: 4 PID: 1082 Comm:
> irq/19-b43 Tainted: G             L 3.19.0-10-generic #10-Ubuntu
> Apr  1 15:01:42 carlos kernel: [ 1837.164004] Hardware name: System
> manufacturer System Product Name/P8Z77-V DELUXE, BIOS 2104 08/13/2013
> Apr  1 15:01:42 carlos kernel: [ 1837.164005] task: ffff8808018809d0
> ti: ffff880802c88000 task.ti: ffff880802c88000
> Apr  1 15:01:42 carlos kernel: [ 1837.164006] RIP:
> e030:[<ffffffff8101e1b6>]  [<ffffffff8101e1b6>] native_read_tsc+0x6/0x20
> Apr  1 15:01:42 carlos kernel: [ 1837.164011] RSP:
> e02b:ffff880802c8bd00  EFLAGS: 00000246
> Apr  1 15:01:42 carlos kernel: [ 1837.164012] RAX: 00000000a08f0862
> RBX: 00000000a08ef87e RCX: 00000000a08f082d
> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RDX: 00000000000005b2
> RSI: 0000000000000000 RDI: 0000000000001a6e
> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RBP: ffff880802c8bd00
> R08: 0000000000000000 R09: 0000000025ae8d40
> Apr  1 15:01:42 carlos kernel: [ 1837.164014] R10: ffff88080d317520
> R11: ffffea001f6f6880 R12: 0000000000001a6e
> Apr  1 15:01:42 carlos kernel: [ 1837.164015] R13: 0000000000000004
> R14: ffff8807e5d1f700 R15: ffff8807ffacb780
> Apr  1 15:01:42 carlos kernel: [ 1837.164018] FS: 
> 0000000000000000(0000) GS:ffff88080d300000(0000) knlGS:ffff88080d300000
> Apr  1 15:01:42 carlos kernel: [ 1837.164019] CS:  e033 DS: 0000 ES:
> 0000 CR0: 0000000080050033
> Apr  1 15:01:42 carlos kernel: [ 1837.164020] CR2: 00007fc0598b2000
> CR3: 0000000001c13000 CR4: 0000000000042660
> Apr  1 15:01:42 carlos kernel: [ 1837.164021] Stack:
> Apr  1 15:01:42 carlos kernel: [ 1837.164022]  ffff880802c8bd28
> ffffffff813c17bb 0000000000000005 000000000000008a
> Apr  1 15:01:42 carlos kernel: [ 1837.164023]  ffff88079f729240
> ffff880802c8bd38 ffffffff813c16fb ffff880802c8bda8
> Apr  1 15:01:42 carlos kernel: [ 1837.164025]  ffffffffc0e223e7
> ffffffffc0e47ea0 0000010000000000 ffffffffc0e47ea0
> Apr  1 15:01:42 carlos kernel: [ 1837.164026] Call Trace:
> Apr  1 15:01:42 carlos kernel: [ 1837.164031]  [<ffffffff813c17bb>]
> delay_tsc+0x3b/0x80
> Apr  1 15:01:42 carlos kernel: [ 1837.164032]  [<ffffffff813c16fb>]
> __const_udelay+0x2b/0x30
> Apr  1 15:01:42 carlos kernel: [ 1837.164038]  [<ffffffffc0e223e7>]
> b43_dma_rx+0xb7/0x3e0 [b43]
> Apr  1 15:01:42 carlos kernel: [ 1837.164042]  [<ffffffff810135ea>] ?
> __switch_to+0x15a/0x5f0
> Apr  1 15:01:42 carlos kernel: [ 1837.164044]  [<ffffffff810ce2e0>] ?
> irq_finalize_oneshot.part.30+0x170/0x170
> Apr  1 15:01:42 carlos kernel: [ 1837.164047]  [<ffffffffc0df56ed>]
> b43_interrupt_thread_handler+0x3dd/0x660 [b43]
> Apr  1 15:01:42 carlos kernel: [ 1837.164049]  [<ffffffff817c337c>] ?
> __schedule+0x39c/0x8e0
> Apr  1 15:01:42 carlos kernel: [ 1837.164051]  [<ffffffff810ce300>]
> irq_thread_fn+0x20/0x50
> Apr  1 15:01:42 carlos kernel: [ 1837.164053]  [<ffffffff810ce2e0>] ?
> irq_finalize_oneshot.part.30+0x170/0x170
> Apr  1 15:01:42 carlos kernel: [ 1837.164054]  [<ffffffff810ce63f>]
> irq_thread+0x11f/0x150
> Apr  1 15:01:42 carlos kernel: [ 1837.164056]  [<ffffffff810ce3a0>] ?
> irq_forced_thread_fn+0x70/0x70
> Apr  1 15:01:42 carlos kernel: [ 1837.164058]  [<ffffffff810ce520>] ?
> irq_thread_check_affinity+0xd0/0xd0
> Apr  1 15:01:42 carlos kernel: [ 1837.164060]  [<ffffffff81094679>]
> kthread+0xc9/0xe0
> Apr  1 15:01:42 carlos kernel: [ 1837.164062]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:42 carlos kernel: [ 1837.164064]  [<ffffffff817c8198>]
> ret_from_fork+0x58/0x90
> Apr  1 15:01:42 carlos kernel: [ 1837.164065]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> "
>

b43 (whatever it is) appears to be mad and is polling while in an rx
interrupt handler.  It also appears as if your CPU is too hot and is
being thermally throttled.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 13786 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 12270 bytes --]

>>First Problem:
>>...
>You do not have /proc/xen/privcmd available in your environment.  Mount
xenfs

How can I mount the XENFS? Is there any guide I should follow?

>>Second Problem:
>>...
>What extra information do you get by following the instruction?

As already shown at the e-mails that started this issue:

"
root@carlos:~# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service;
static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Qua 2015-04-01 15:37:58 BRT;
54min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 668 ExecStart=/lib/systemd/systemd-modules-load (code=exited,
status=1/FAILURE)
 Main PID: 668 (code=exited, status=1/FAILURE)

Abr 01 15:37:58 carlos systemd[1]: Starting Load Kernel Modules...
Abr 01 15:37:58 carlos systemd-modules-load[668]: Module 'fuse' is builtin
Abr 01 15:37:58 carlos systemd-modules-load[668]: Failed to find module
'evt...
Abr 01 15:37:58 carlos systemd[1]: systemd-modules-load.service: main
proc...RE
Abr 01 15:37:58 carlos systemd[1]: Failed to start Load Kernel Modules.
Abr 01 15:37:58 carlos systemd[1]: Unit systemd-modules-load.service
enter...e.
Abr 01 15:37:58 carlos systemd[1]: systemd-modules-load.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
"

>>Third Problem:
>>...
>I don't see how this could plausibly be a Xen issue.

Ok, thanks for the reply, I was just checking since all of this problems
started almost at the same time...

>>Fourth Problem:
>>...
>b43 (whatever it is) appears to be mad and is polling while in an rx
interrupt handler.  It also appears as if your CPU is too hot and is being
thermally throttled.

Any way I can find out how to I fix this issue, since my CPU is not hot at
all, running "sensors" from terminal:

"
root@carlos:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +106.0°C)
temp2:        +29.8°C  (crit = +106.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +51.0°C  (high = +85.0°C, crit = +105.0°C)
Core 0:         +45.0°C  (high = +85.0°C, crit = +105.0°C)
Core 1:         +51.0°C  (high = +85.0°C, crit = +105.0°C)
Core 2:         +46.0°C  (high = +85.0°C, crit = +105.0°C)
Core 3:         +51.0°C  (high = +85.0°C, crit = +105.0°C)

nouveau-pci-0100
Adapter: PCI adapter
fan1:        1170 RPM
temp1:        +41.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)
"

2015-04-01 16:14 GMT-03:00 Andrew Cooper <andrew.cooper3@citrix.com>:

>  On 01/04/15 19:55, Carlos Gustavo Ramirez Rodriguez wrote:
>
>   Hello DEVs, can anyone help me?
>
> Ian Campbell pointed me that maybe you could help me, here is the link to
> the last e-mail line that started this problem fixing:
> http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html
>
> A brief summary of my current problems after XEN installation:
>
>  First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:
>
> "
> xc: error: Could not obtain handle on privileged command interface (2 = No
> such file or directory): Internal error
> libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle: No
> such file or directory
> cannot init xl context
> "
>
>
> You do not have /proc/xen/privcmd available in your environment.  Mount
> xenfs
>
> (note to self - dust off my patch which makes that error message more
> useful)
>
>
> Second Problem:
> My boot.log is showing:
>
> "
> [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
> See "systemctl status systemd-modules-load.service" for details.
> "
>
>
> What extra information do you get by following the instruction?
>
>   Third Problem:
>  Today doing an apt-get update and apt-get dist-upgrade to see if there
> was any major fix on stuff... and probably I am with a Regression in hands:
>
> "
> Error found when loading /etc/profile:
> /etc/profile.d/cedilla-brazil.sh: linha 21: [: n?mero excessivo de
> argumentos
>
> As a result the session will not be configured correctly
> You should fix the problem as soon as feasible.
>  "
>
>  Also trying to run "sudo su -" on terminal I get a message saying I have
> too much arguments for (su) but since it appears related to this problem
> above, I consider both the same.
>
>
> I don't see how this could plausibly be a Xen issue.
>
>
>
>  ***I have already sent an e-mail to the Ubuntu mailing list about this
> problem...
>
> Fourth Problem:
> I am receiving KERNEL OOPS messages saying my #4 processor is pausing:
> "
> NMI watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [irq/19-b43:1082]
> "
>  that is a strip from syslog, showing that message:
> "
> Apr  1 15:01:34 carlos kernel: [ 1829.176231]  [<ffffffff817c5cf5>]
> __mutex_lock_slowpath+0x95/0x100
> Apr  1 15:01:34 carlos kernel: [ 1829.176233]  [<ffffffff817c5d83>]
> mutex_lock+0x23/0x40
> Apr  1 15:01:34 carlos kernel: [ 1829.176235]  [<ffffffffc0df47f3>]
> b43_periodic_work_handler+0x33/0x190 [b43]
> Apr  1 15:01:34 carlos kernel: [ 1829.176237]  [<ffffffff8108eb48>]
> process_one_work+0x158/0x430
> Apr  1 15:01:34 carlos kernel: [ 1829.176238]  [<ffffffff8108f5db>]
> worker_thread+0x5b/0x530
> Apr  1 15:01:34 carlos kernel: [ 1829.176239]  [<ffffffff8108f580>] ?
> rescuer_thread+0x3a0/0x3a0
> Apr  1 15:01:34 carlos kernel: [ 1829.176241]  [<ffffffff81094679>]
> kthread+0xc9/0xe0
> Apr  1 15:01:34 carlos kernel: [ 1829.176243]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:34 carlos kernel: [ 1829.176244]  [<ffffffff817c8198>]
> ret_from_fork+0x58/0x90
> Apr  1 15:01:34 carlos kernel: [ 1829.176246]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:36 carlos thermald[910]: Dropped below poll threshold
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 5:Processor
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 13:intel_powerclamp
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 14:rapl_controller
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 5:Processor
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 13:intel_powerclamp
> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
> 14:rapl_controller
> Apr  1 15:01:40 carlos thermald[910]: Read set point 0
> Apr  1 15:01:40 carlos thermald[910]: Set : 94000, 74000, 5, 0, 0
> Apr  1 15:01:42 carlos kernel: [ 1837.163940] NMI watchdog: BUG: soft
> lockup - CPU#4 stuck for 22s! [irq/19-b43:1082]
> Apr  1 15:01:42 carlos kernel: [ 1837.163944] Modules linked in: rfcomm
> bnep nls_iso8859_1 arc4 b43 mac80211 cfg80211 snd_hda_codec_hdmi ssb
> eeepc_wmi asus_wmi sparse_keymap snd_hda_codec_realtek
> snd_hda_codec_generic snd_hda_intel snd_hda_controller intel_rapl iosf_mbi
> snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hwdep coretemp
> snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uvcvideo
> aesni_intel snd_seq_midi videobuf2_vmalloc snd_seq_midi_event btusb
> aes_x86_64 videobuf2_memops videobuf2_core lrw snd_rawmidi gf128mul
> v4l2_common glue_helper ablk_helper nouveau bluetooth snd_seq cryptd
> videodev cypress_m8 media serio_raw joydev snd_seq_device i915 usbserial
> snd_timer mxm_wmi bcma lpc_ich ttm drm_kms_helper snd drm mei_me soundcore
> mei i2c_algo_bit video intel_smartconnect ie31200_edac wmi shpchp edac_core
> mac_hid xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev
> xen_evtchn parport_pc ppdev lp parport autofs4 btrfs hid_generic usbhid hid
> raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
> xor raid6_pq e1000e raid1 psmouse ptp r8169 mii raid0 pps_core ahci
> multipath libahci linear
> Apr  1 15:01:42 carlos kernel: [ 1837.164002] CPU: 4 PID: 1082 Comm:
> irq/19-b43 Tainted: G             L 3.19.0-10-generic #10-Ubuntu
> Apr  1 15:01:42 carlos kernel: [ 1837.164004] Hardware name: System
> manufacturer System Product Name/P8Z77-V DELUXE, BIOS 2104 08/13/2013
> Apr  1 15:01:42 carlos kernel: [ 1837.164005] task: ffff8808018809d0 ti:
> ffff880802c88000 task.ti: ffff880802c88000
> Apr  1 15:01:42 carlos kernel: [ 1837.164006] RIP:
> e030:[<ffffffff8101e1b6>]  [<ffffffff8101e1b6>] native_read_tsc+0x6/0x20
> Apr  1 15:01:42 carlos kernel: [ 1837.164011] RSP: e02b:ffff880802c8bd00
> EFLAGS: 00000246
> Apr  1 15:01:42 carlos kernel: [ 1837.164012] RAX: 00000000a08f0862 RBX:
> 00000000a08ef87e RCX: 00000000a08f082d
> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RDX: 00000000000005b2 RSI:
> 0000000000000000 RDI: 0000000000001a6e
> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RBP: ffff880802c8bd00 R08:
> 0000000000000000 R09: 0000000025ae8d40
> Apr  1 15:01:42 carlos kernel: [ 1837.164014] R10: ffff88080d317520 R11:
> ffffea001f6f6880 R12: 0000000000001a6e
> Apr  1 15:01:42 carlos kernel: [ 1837.164015] R13: 0000000000000004 R14:
> ffff8807e5d1f700 R15: ffff8807ffacb780
> Apr  1 15:01:42 carlos kernel: [ 1837.164018] FS:  0000000000000000(0000)
> GS:ffff88080d300000(0000) knlGS:ffff88080d300000
> Apr  1 15:01:42 carlos kernel: [ 1837.164019] CS:  e033 DS: 0000 ES: 0000
> CR0: 0000000080050033
> Apr  1 15:01:42 carlos kernel: [ 1837.164020] CR2: 00007fc0598b2000 CR3:
> 0000000001c13000 CR4: 0000000000042660
> Apr  1 15:01:42 carlos kernel: [ 1837.164021] Stack:
> Apr  1 15:01:42 carlos kernel: [ 1837.164022]  ffff880802c8bd28
> ffffffff813c17bb 0000000000000005 000000000000008a
> Apr  1 15:01:42 carlos kernel: [ 1837.164023]  ffff88079f729240
> ffff880802c8bd38 ffffffff813c16fb ffff880802c8bda8
> Apr  1 15:01:42 carlos kernel: [ 1837.164025]  ffffffffc0e223e7
> ffffffffc0e47ea0 0000010000000000 ffffffffc0e47ea0
> Apr  1 15:01:42 carlos kernel: [ 1837.164026] Call Trace:
> Apr  1 15:01:42 carlos kernel: [ 1837.164031]  [<ffffffff813c17bb>]
> delay_tsc+0x3b/0x80
> Apr  1 15:01:42 carlos kernel: [ 1837.164032]  [<ffffffff813c16fb>]
> __const_udelay+0x2b/0x30
> Apr  1 15:01:42 carlos kernel: [ 1837.164038]  [<ffffffffc0e223e7>]
> b43_dma_rx+0xb7/0x3e0 [b43]
> Apr  1 15:01:42 carlos kernel: [ 1837.164042]  [<ffffffff810135ea>] ?
> __switch_to+0x15a/0x5f0
> Apr  1 15:01:42 carlos kernel: [ 1837.164044]  [<ffffffff810ce2e0>] ?
> irq_finalize_oneshot.part.30+0x170/0x170
> Apr  1 15:01:42 carlos kernel: [ 1837.164047]  [<ffffffffc0df56ed>]
> b43_interrupt_thread_handler+0x3dd/0x660 [b43]
> Apr  1 15:01:42 carlos kernel: [ 1837.164049]  [<ffffffff817c337c>] ?
> __schedule+0x39c/0x8e0
> Apr  1 15:01:42 carlos kernel: [ 1837.164051]  [<ffffffff810ce300>]
> irq_thread_fn+0x20/0x50
> Apr  1 15:01:42 carlos kernel: [ 1837.164053]  [<ffffffff810ce2e0>] ?
> irq_finalize_oneshot.part.30+0x170/0x170
> Apr  1 15:01:42 carlos kernel: [ 1837.164054]  [<ffffffff810ce63f>]
> irq_thread+0x11f/0x150
> Apr  1 15:01:42 carlos kernel: [ 1837.164056]  [<ffffffff810ce3a0>] ?
> irq_forced_thread_fn+0x70/0x70
> Apr  1 15:01:42 carlos kernel: [ 1837.164058]  [<ffffffff810ce520>] ?
> irq_thread_check_affinity+0xd0/0xd0
> Apr  1 15:01:42 carlos kernel: [ 1837.164060]  [<ffffffff81094679>]
> kthread+0xc9/0xe0
> Apr  1 15:01:42 carlos kernel: [ 1837.164062]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> Apr  1 15:01:42 carlos kernel: [ 1837.164064]  [<ffffffff817c8198>]
> ret_from_fork+0x58/0x90
> Apr  1 15:01:42 carlos kernel: [ 1837.164065]  [<ffffffff810945b0>] ?
> kthread_create_on_node+0x1c0/0x1c0
> "
>
>
> b43 (whatever it is) appears to be mad and is polling while in an rx
> interrupt handler.  It also appears as if your CPU is too hot and is being
> thermally throttled.
>
> ~Andrew
>



-- 
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 17359 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 12848 bytes --]

Just a quick update on my bugs...

Third Problem:
Just fixed by Ubuntu team - Thanks for your time anyway.

2015-04-01 16:39 GMT-03:00 Carlos Gustavo Ramirez Rodriguez <
carlosgrr@gmail.com>:

> >>First Problem:
> >>...
> >You do not have /proc/xen/privcmd available in your environment.  Mount
> xenfs
>
> How can I mount the XENFS? Is there any guide I should follow?
>
> >>Second Problem:
> >>...
> >What extra information do you get by following the instruction?
>
> As already shown at the e-mails that started this issue:
>
> "
> root@carlos:~# systemctl status systemd-modules-load.service
> ● systemd-modules-load.service - Load Kernel Modules
>    Loaded: loaded (/lib/systemd/system/systemd-modules-load.service;
> static; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Qua 2015-04-01 15:37:58 BRT;
> 54min ago
>      Docs: man:systemd-modules-load.service(8)
>            man:modules-load.d(5)
>   Process: 668 ExecStart=/lib/systemd/systemd-modules-load (code=exited,
> status=1/FAILURE)
>  Main PID: 668 (code=exited, status=1/FAILURE)
>
> Abr 01 15:37:58 carlos systemd[1]: Starting Load Kernel Modules...
> Abr 01 15:37:58 carlos systemd-modules-load[668]: Module 'fuse' is builtin
> Abr 01 15:37:58 carlos systemd-modules-load[668]: Failed to find module
> 'evt...
> Abr 01 15:37:58 carlos systemd[1]: systemd-modules-load.service: main
> proc...RE
> Abr 01 15:37:58 carlos systemd[1]: Failed to start Load Kernel Modules.
> Abr 01 15:37:58 carlos systemd[1]: Unit systemd-modules-load.service
> enter...e.
> Abr 01 15:37:58 carlos systemd[1]: systemd-modules-load.service failed.
> Hint: Some lines were ellipsized, use -l to show in full.
> "
>
> >>Third Problem:
> >>...
> >I don't see how this could plausibly be a Xen issue.
>
> Ok, thanks for the reply, I was just checking since all of this problems
> started almost at the same time...
>
> >>Fourth Problem:
> >>...
> >b43 (whatever it is) appears to be mad and is polling while in an rx
> interrupt handler.  It also appears as if your CPU is too hot and is being
> thermally throttled.
>
> Any way I can find out how to I fix this issue, since my CPU is not hot at
> all, running "sensors" from terminal:
>
> "
> root@carlos:~# sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:        +27.8°C  (crit = +106.0°C)
> temp2:        +29.8°C  (crit = +106.0°C)
>
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:  +51.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 0:         +45.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 1:         +51.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 2:         +46.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 3:         +51.0°C  (high = +85.0°C, crit = +105.0°C)
>
> nouveau-pci-0100
> Adapter: PCI adapter
> fan1:        1170 RPM
> temp1:        +41.0°C  (high = +95.0°C, hyst =  +3.0°C)
>                        (crit = +105.0°C, hyst =  +5.0°C)
>                        (emerg = +135.0°C, hyst =  +5.0°C)
> "
>
> 2015-04-01 16:14 GMT-03:00 Andrew Cooper <andrew.cooper3@citrix.com>:
>
>  On 01/04/15 19:55, Carlos Gustavo Ramirez Rodriguez wrote:
>>
>>   Hello DEVs, can anyone help me?
>>
>> Ian Campbell pointed me that maybe you could help me, here is the link to
>> the last e-mail line that started this problem fixing:
>> http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html
>>
>> A brief summary of my current problems after XEN installation:
>>
>>  First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:
>>
>> "
>> xc: error: Could not obtain handle on privileged command interface (2 =
>> No such file or directory): Internal error
>> libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle: No
>> such file or directory
>> cannot init xl context
>> "
>>
>>
>> You do not have /proc/xen/privcmd available in your environment.  Mount
>> xenfs
>>
>> (note to self - dust off my patch which makes that error message more
>> useful)
>>
>>
>> Second Problem:
>> My boot.log is showing:
>>
>> "
>> [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
>> See "systemctl status systemd-modules-load.service" for details.
>> "
>>
>>
>> What extra information do you get by following the instruction?
>>
>>   Third Problem:
>>  Today doing an apt-get update and apt-get dist-upgrade to see if there
>> was any major fix on stuff... and probably I am with a Regression in hands:
>>
>> "
>> Error found when loading /etc/profile:
>> /etc/profile.d/cedilla-brazil.sh: linha 21: [: n?mero excessivo de
>> argumentos
>>
>> As a result the session will not be configured correctly
>> You should fix the problem as soon as feasible.
>>  "
>>
>>  Also trying to run "sudo su -" on terminal I get a message saying I
>> have too much arguments for (su) but since it appears related to this
>> problem above, I consider both the same.
>>
>>
>> I don't see how this could plausibly be a Xen issue.
>>
>>
>>
>>  ***I have already sent an e-mail to the Ubuntu mailing list about this
>> problem...
>>
>> Fourth Problem:
>> I am receiving KERNEL OOPS messages saying my #4 processor is pausing:
>> "
>> NMI watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [irq/19-b43:1082]
>> "
>>  that is a strip from syslog, showing that message:
>> "
>> Apr  1 15:01:34 carlos kernel: [ 1829.176231]  [<ffffffff817c5cf5>]
>> __mutex_lock_slowpath+0x95/0x100
>> Apr  1 15:01:34 carlos kernel: [ 1829.176233]  [<ffffffff817c5d83>]
>> mutex_lock+0x23/0x40
>> Apr  1 15:01:34 carlos kernel: [ 1829.176235]  [<ffffffffc0df47f3>]
>> b43_periodic_work_handler+0x33/0x190 [b43]
>> Apr  1 15:01:34 carlos kernel: [ 1829.176237]  [<ffffffff8108eb48>]
>> process_one_work+0x158/0x430
>> Apr  1 15:01:34 carlos kernel: [ 1829.176238]  [<ffffffff8108f5db>]
>> worker_thread+0x5b/0x530
>> Apr  1 15:01:34 carlos kernel: [ 1829.176239]  [<ffffffff8108f580>] ?
>> rescuer_thread+0x3a0/0x3a0
>> Apr  1 15:01:34 carlos kernel: [ 1829.176241]  [<ffffffff81094679>]
>> kthread+0xc9/0xe0
>> Apr  1 15:01:34 carlos kernel: [ 1829.176243]  [<ffffffff810945b0>] ?
>> kthread_create_on_node+0x1c0/0x1c0
>> Apr  1 15:01:34 carlos kernel: [ 1829.176244]  [<ffffffff817c8198>]
>> ret_from_fork+0x58/0x90
>> Apr  1 15:01:34 carlos kernel: [ 1829.176246]  [<ffffffff810945b0>] ?
>> kthread_create_on_node+0x1c0/0x1c0
>> Apr  1 15:01:36 carlos thermald[910]: Dropped below poll threshold
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 5:Processor
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 13:intel_powerclamp
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 14:rapl_controller
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 5:Processor
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 13:intel_powerclamp
>> Apr  1 15:01:36 carlos thermald[910]: thd_trip_cdev_state_reset index
>> 14:rapl_controller
>> Apr  1 15:01:40 carlos thermald[910]: Read set point 0
>> Apr  1 15:01:40 carlos thermald[910]: Set : 94000, 74000, 5, 0, 0
>> Apr  1 15:01:42 carlos kernel: [ 1837.163940] NMI watchdog: BUG: soft
>> lockup - CPU#4 stuck for 22s! [irq/19-b43:1082]
>> Apr  1 15:01:42 carlos kernel: [ 1837.163944] Modules linked in: rfcomm
>> bnep nls_iso8859_1 arc4 b43 mac80211 cfg80211 snd_hda_codec_hdmi ssb
>> eeepc_wmi asus_wmi sparse_keymap snd_hda_codec_realtek
>> snd_hda_codec_generic snd_hda_intel snd_hda_controller intel_rapl iosf_mbi
>> snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hwdep coretemp
>> snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uvcvideo
>> aesni_intel snd_seq_midi videobuf2_vmalloc snd_seq_midi_event btusb
>> aes_x86_64 videobuf2_memops videobuf2_core lrw snd_rawmidi gf128mul
>> v4l2_common glue_helper ablk_helper nouveau bluetooth snd_seq cryptd
>> videodev cypress_m8 media serio_raw joydev snd_seq_device i915 usbserial
>> snd_timer mxm_wmi bcma lpc_ich ttm drm_kms_helper snd drm mei_me soundcore
>> mei i2c_algo_bit video intel_smartconnect ie31200_edac wmi shpchp edac_core
>> mac_hid xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev
>> xen_evtchn parport_pc ppdev lp parport autofs4 btrfs hid_generic usbhid hid
>> raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
>> xor raid6_pq e1000e raid1 psmouse ptp r8169 mii raid0 pps_core ahci
>> multipath libahci linear
>> Apr  1 15:01:42 carlos kernel: [ 1837.164002] CPU: 4 PID: 1082 Comm:
>> irq/19-b43 Tainted: G             L 3.19.0-10-generic #10-Ubuntu
>> Apr  1 15:01:42 carlos kernel: [ 1837.164004] Hardware name: System
>> manufacturer System Product Name/P8Z77-V DELUXE, BIOS 2104 08/13/2013
>> Apr  1 15:01:42 carlos kernel: [ 1837.164005] task: ffff8808018809d0 ti:
>> ffff880802c88000 task.ti: ffff880802c88000
>> Apr  1 15:01:42 carlos kernel: [ 1837.164006] RIP:
>> e030:[<ffffffff8101e1b6>]  [<ffffffff8101e1b6>] native_read_tsc+0x6/0x20
>> Apr  1 15:01:42 carlos kernel: [ 1837.164011] RSP: e02b:ffff880802c8bd00
>> EFLAGS: 00000246
>> Apr  1 15:01:42 carlos kernel: [ 1837.164012] RAX: 00000000a08f0862 RBX:
>> 00000000a08ef87e RCX: 00000000a08f082d
>> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RDX: 00000000000005b2 RSI:
>> 0000000000000000 RDI: 0000000000001a6e
>> Apr  1 15:01:42 carlos kernel: [ 1837.164013] RBP: ffff880802c8bd00 R08:
>> 0000000000000000 R09: 0000000025ae8d40
>> Apr  1 15:01:42 carlos kernel: [ 1837.164014] R10: ffff88080d317520 R11:
>> ffffea001f6f6880 R12: 0000000000001a6e
>> Apr  1 15:01:42 carlos kernel: [ 1837.164015] R13: 0000000000000004 R14:
>> ffff8807e5d1f700 R15: ffff8807ffacb780
>> Apr  1 15:01:42 carlos kernel: [ 1837.164018] FS:  0000000000000000(0000)
>> GS:ffff88080d300000(0000) knlGS:ffff88080d300000
>> Apr  1 15:01:42 carlos kernel: [ 1837.164019] CS:  e033 DS: 0000 ES: 0000
>> CR0: 0000000080050033
>> Apr  1 15:01:42 carlos kernel: [ 1837.164020] CR2: 00007fc0598b2000 CR3:
>> 0000000001c13000 CR4: 0000000000042660
>> Apr  1 15:01:42 carlos kernel: [ 1837.164021] Stack:
>> Apr  1 15:01:42 carlos kernel: [ 1837.164022]  ffff880802c8bd28
>> ffffffff813c17bb 0000000000000005 000000000000008a
>> Apr  1 15:01:42 carlos kernel: [ 1837.164023]  ffff88079f729240
>> ffff880802c8bd38 ffffffff813c16fb ffff880802c8bda8
>> Apr  1 15:01:42 carlos kernel: [ 1837.164025]  ffffffffc0e223e7
>> ffffffffc0e47ea0 0000010000000000 ffffffffc0e47ea0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164026] Call Trace:
>> Apr  1 15:01:42 carlos kernel: [ 1837.164031]  [<ffffffff813c17bb>]
>> delay_tsc+0x3b/0x80
>> Apr  1 15:01:42 carlos kernel: [ 1837.164032]  [<ffffffff813c16fb>]
>> __const_udelay+0x2b/0x30
>> Apr  1 15:01:42 carlos kernel: [ 1837.164038]  [<ffffffffc0e223e7>]
>> b43_dma_rx+0xb7/0x3e0 [b43]
>> Apr  1 15:01:42 carlos kernel: [ 1837.164042]  [<ffffffff810135ea>] ?
>> __switch_to+0x15a/0x5f0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164044]  [<ffffffff810ce2e0>] ?
>> irq_finalize_oneshot.part.30+0x170/0x170
>> Apr  1 15:01:42 carlos kernel: [ 1837.164047]  [<ffffffffc0df56ed>]
>> b43_interrupt_thread_handler+0x3dd/0x660 [b43]
>> Apr  1 15:01:42 carlos kernel: [ 1837.164049]  [<ffffffff817c337c>] ?
>> __schedule+0x39c/0x8e0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164051]  [<ffffffff810ce300>]
>> irq_thread_fn+0x20/0x50
>> Apr  1 15:01:42 carlos kernel: [ 1837.164053]  [<ffffffff810ce2e0>] ?
>> irq_finalize_oneshot.part.30+0x170/0x170
>> Apr  1 15:01:42 carlos kernel: [ 1837.164054]  [<ffffffff810ce63f>]
>> irq_thread+0x11f/0x150
>> Apr  1 15:01:42 carlos kernel: [ 1837.164056]  [<ffffffff810ce3a0>] ?
>> irq_forced_thread_fn+0x70/0x70
>> Apr  1 15:01:42 carlos kernel: [ 1837.164058]  [<ffffffff810ce520>] ?
>> irq_thread_check_affinity+0xd0/0xd0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164060]  [<ffffffff81094679>]
>> kthread+0xc9/0xe0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164062]  [<ffffffff810945b0>] ?
>> kthread_create_on_node+0x1c0/0x1c0
>> Apr  1 15:01:42 carlos kernel: [ 1837.164064]  [<ffffffff817c8198>]
>> ret_from_fork+0x58/0x90
>> Apr  1 15:01:42 carlos kernel: [ 1837.164065]  [<ffffffff810945b0>] ?
>> kthread_create_on_node+0x1c0/0x1c0
>> "
>>
>>
>> b43 (whatever it is) appears to be mad and is polling while in an rx
>> interrupt handler.  It also appears as if your CPU is too hot and is being
>> thermally throttled.
>>
>> ~Andrew
>>
>
>
>
> --
> Gustavo
>



-- 
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 18121 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Olaf Hering]

On Wed, Apr 01, Carlos Gustavo Ramirez Rodriguez wrote:

> Hello DEVs, can anyone help me?
> 
> Ian Campbell pointed me that maybe you could help me, here is the link to the
> last e-mail line that started this problem fixing:
> http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html
> 
> A brief summary of my current problems after XEN installation:
> 
> First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:
> 
> "
> xc: error: Could not obtain handle on privileged command interface (2 = No such
> file or directory): Internal error
> libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle: No such
> file or directory
> cannot init xl context
> "

Which systemd services files from xen are enabled? See the systemd part
of the INSTALL file:
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob_plain;f=INSTALL;hb=staging

systemctl enable xen-qemu-dom0-disk-backend.service
systemctl enable xen-init-dom0.service
systemctl enable xenconsoled.service

> Second Problem:
> My boot.log is showing:
> 
> "
> [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
> See "systemctl status systemd-modules-load.service" for details.
> "

This is a bug in systemd. It assumes that all modules listed in
/usr/lib/modules-load.d/ are available in each and every runtime kernel.
Even grandma knows that this is not true. Just ignore errors from that
service.

Olaf

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Ian Campbell]

On Thu, 2015-04-02 at 08:23 +0200, Olaf Hering wrote:
> On Wed, Apr 01, Carlos Gustavo Ramirez Rodriguez wrote:
> > Second Problem:
> > My boot.log is showing:
> > 
> > "
> > [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
> > See "systemctl status systemd-modules-load.service" for details.
> > "
> 
> This is a bug in systemd. It assumes that all modules listed in
> /usr/lib/modules-load.d/ are available in each and every runtime kernel.
> Even grandma knows that this is not true. Just ignore errors from that
> service.

Has someone filed a wishlist bug with systemd?

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 4304 bytes --]

Hello,

First Problem:

>Which systemd services files from xen are enabled? See the systemd part
>of the INSTALL file:
>http://xenbits.xen.org/gitweb/?p=xen.git;a=blob_plain;f=INSTALL;hb=staging
<http://xenbits.xen.org/gitweb/?p=xen.git;a=blob_plain;f=INSTALL;hb=staging>

When compiled from source, no options where given, my ubuntu is installed
with systemd, so I guess the part of the installation file that states:
"
...

NOTE: if systemd development packages are installed the systemd support
will be the enabled per default.
...

"
Is somehow related to my situation.

>systemctl enable xen-qemu-dom0-disk-backend.service
>systemctl enable xen-init-dom0.service
>systemctl enable xenconsoled.service

These MAGIC lines did the trick! Thanks for the help, this solved the First
Problem, BUT, if you know those lines, can't you submit a patch to fix this
issue for the next "Lucky user"? How can I help to fix it?

Second Problem:
>OLAF:
>This is a bug in systemd. It assumes that all modules listed in
>/usr/lib/modules-load.d/ are available in each and every runtime kernel.
>Even grandma knows that this is not true. Just ignore errors from that
>service.

>IAN:
>Has someone filed a wishlist bug with systemd?

Should I ask the user list of the systemd?

After fixing the first problem, with those lines stated above here is the
new output:
"
root@carlos:~# systemctl status systemd-modules-load.service -l
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service;
static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Qui 2015-04-02 11:48:59 BRT;
5min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 671 ExecStart=/lib/systemd/systemd-modules-load (code=exited,
status=1/FAILURE)
 Main PID: 671 (code=exited, status=1/FAILURE)

Abr 02 11:48:59 carlos systemd[1]: Starting Load Kernel Modules...
Abr 02 11:48:59 carlos systemd-modules-load[671]: Module 'fuse' is builtin
Abr 02 11:48:59 carlos systemd[1]: systemd-modules-load.service: main
process exited, code=exited, status=1/FAILURE
Abr 02 11:48:59 carlos systemd[1]: Failed to start Load Kernel Modules.
Abr 02 11:48:59 carlos systemd[1]: Unit systemd-modules-load.service
entered failed state.
Abr 02 11:48:59 carlos systemd[1]: systemd-modules-load.service failed.
root@carlos:~#
"
Third Problem: Already SOLVED.

Fourth Problem:
After fixing the Third problem the Fourth Problem solved itself by MAGIC...
Probably it was somehow related to the language being used by the system...
Anyway... Thanks for the help.

2015-04-02 3:23 GMT-03:00 Olaf Hering <olaf@aepfle.de>:

> On Wed, Apr 01, Carlos Gustavo Ramirez Rodriguez wrote:
>
> > Hello DEVs, can anyone help me?
> >
> > Ian Campbell pointed me that maybe you could help me, here is the link
> to the
> > last e-mail line that started this problem fixing:
> >
> http://lists.xenproject.org/archives/html/xen-users/2015-04/msg00009.html
> >
> > A brief summary of my current problems after XEN installation:
> >
> > First Problem: XL "Anything", be it INFO, TOP, UPTIME, whatever, returns:
> >
> > "
> > xc: error: Could not obtain handle on privileged command interface (2 =
> No such
> > file or directory): Internal error
> > libxl: error: libxl.c:109:libxl_ctx_alloc: cannot open libxc handle: No
> such
> > file or directory
> > cannot init xl context
> > "
>
> Which systemd services files from xen are enabled? See the systemd part
> of the INSTALL file:
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob_plain;f=INSTALL;hb=staging
>
> systemctl enable xen-qemu-dom0-disk-backend.service
> systemctl enable xen-init-dom0.service
> systemctl enable xenconsoled.service
>
> > Second Problem:
> > My boot.log is showing:
> >
> > "
> > [ [1;31mFAILED [0m] Failed to start Load Kernel Modules.
> > See "systemctl status systemd-modules-load.service" for details.
> > "
>
> This is a bug in systemd. It assumes that all modules listed in
> /usr/lib/modules-load.d/ are available in each and every runtime kernel.
> Even grandma knows that this is not true. Just ignore errors from that
> service.
>
> Olaf
>



-- 
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 5652 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Olaf Hering]

On Thu, Apr 02, Carlos Gustavo Ramirez Rodriguez wrote:

> >systemctl enable xen-qemu-dom0-disk-backend.service
> >systemctl enable xen-init-dom0.service
> >systemctl enable xenconsoled.service
> These MAGIC lines did the trick! Thanks for the help, this solved the First
> Problem, BUT, if you know those lines, can't you submit a patch to fix this
> issue for the next "Lucky user"? How can I help to fix it?

make install will not enable sysv or systemd services. Distro packages
are supposed to enable themselve. If that is not desired by distro
maintainers the distro should provide ways to easily enable services.
Ubuntu probably has code to enable the sysv "xencommons" script. Perhaps
Ubuntu is not uptodate and lacks the knobs to enable all of the systemd
.service files above.

Olaf

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 1362 bytes --]

>make install will not enable sysv or systemd services. Distro packages
>are supposed to enable themselve. If that is not desired by distro
>maintainers the distro should provide ways to easily enable services.
>Ubuntu probably has code to enable the sysv "xencommons" script. Perhaps
>Ubuntu is not uptodate and lacks the knobs to enable all of the systemd
>.service files above.

Well, if it is not the default behavior to enable these services, at least
these procedures should be detailed at the WEBPAGE of XEN Installation, so
that someone installing the system might know that it is supposed to do
that after compiling inside Ubuntu, you have to start these services by
hand, or do you mean it is a BUG that should be opened inside the Ubuntu
Launchpad?
All of those commands had to be run just once, and by themselves they fixed
the problem... There was another service of xen not yet started, here is
the output:

"
root@carlos:/# systemctl enable xen-watchdog.service
Synchronizing state for xen-watchdog.service with sysvinit using
update-rc.d...
Executing /usr/sbin/update-rc.d xen-watchdog defaults
Executing /usr/sbin/update-rc.d xen-watchdog enable
Created symlink from
/etc/systemd/system/multi-user.target.wants/xen-watchdog.service to
/usr/local/lib/systemd/system/xen-watchdog.service.
"

Should I open a Bug Report inside Ubuntu?

-- 
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 1671 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Ian Campbell]

On Thu, 2015-04-02 at 14:42 -0300, Carlos Gustavo Ramirez Rodriguez
wrote:
> >make install will not enable sysv or systemd services. Distro
> packages
> >are supposed to enable themselve. If that is not desired by distro
> >maintainers the distro should provide ways to easily enable services.
> >Ubuntu probably has code to enable the sysv "xencommons" script.
> Perhaps
> >Ubuntu is not uptodate and lacks the knobs to enable all of the
> systemd
> >.service files above.

It's not Ubuntu, this is simply something which needs to be done after
installing Xen.

> Well, if it is not the default behavior to enable these services, at
> least these procedures should be detailed at the WEBPAGE of XEN
> Installation,

It's written at
http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source#Post-Installation
and in the file called INSTALL at the top level of the source tree.

Which instructions were you following which didn't mention them, so we
can update them?

> Should I open a Bug Report inside Ubuntu?

No, xen-watchdog.service is documented as being optional.

Ian.

Re: ENC:[Xen-users] Failed to insert 'xen_evtchn': No such device

[Carlos Gustavo Ramirez Rodriguez]

[-- Attachment #1.1: Type: text/plain, Size: 623 bytes --]

> Which instructions were you following which didn't mention them, so we
> can update them?

I was installing starting from the Quick-start Guide from the README file.

I thought that was the installation page and any specific case should be
searched in other files... Sorry for the misunderstanding, and THANKS for
helping me fix this issue, after a lot of bumps along the way you helped me
install it! Thank you very much, once again, thanks IAN for helping me, and
OLAF for pointing where I was doing it wrongly!

If any further problems arrive I will restart a new subject at the users
mailing list!

Thankful,
Gustavo

[-- Attachment #1.2: Type: text/html, Size: 844 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel