search for: cpu23

...nt.us wrote: >> Current kernel, and I just booted, and dmesg shows, of the 32 cores, 0, >> 2, 4 and 6 ok, and *all* other show "is now offline. >> >> What's happening here? <snip> Ok, more info. I found how to online a CPU - echo 1 > /sys/devices/system/cpu/cpu23/online Perhaps I should have started with 1,3, etc, but I was doing the 20's, instead. Got to CPU27... and the system rebooted. Now I'm wondering if the offline'd CPUs have something to do with the fact that this (and an identical one, in the datacenter, are rebooting around 04:00 eve...

...rk thins, > and others to transmit/receive data. > > So, in this case, it seems to driver need to touch the IRQ numbers. > > wr-linux:~ # cat /proc/interrupts > CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 > ...... > 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 > 101: 2 0 0 0 0 0 302830488 0 0 0 IR-PCI...

...rk thins, > and others to transmit/receive data. > > So, in this case, it seems to driver need to touch the IRQ numbers. > > wr-linux:~ # cat /proc/interrupts > CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 > ...... > 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 > 101: 2 0 0 0 0 0 302830488 0 0 0 IR-PCI...

On Wednesday 30 July 2014, Yijing Wang wrote: > >>> > >>> The other part I'm not completely sure about is how you want to > >>> have MSIs map into normal IRQ descriptors. At the moment, all > >>> MSI users are based on IRQ numbers, but this has known scalability problems. > >> > >> Hmmm, I still use the IRQ number to map the

On Wednesday 30 July 2014, Yijing Wang wrote: > >>> > >>> The other part I'm not completely sure about is how you want to > >>> have MSIs map into normal IRQ descriptors. At the moment, all > >>> MSI users are based on IRQ numbers, but this has known scalability problems. > >> > >> Hmmm, I still use the IRQ number to map the

Current kernel, and I just booted, and dmesg shows, of the 32 cores, 0, 2, 4 and 6 ok, and *all* other show "is now offline. What's happening here? mark

...them to process trivial network thins, and others to transmit/receive data. So, in this case, it seems to driver need to touch the IRQ numbers. wr-linux:~ # cat /proc/interrupts CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23 ...... 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 101: 2 0 0 0 0 0 302830488 0 0 0 IR-PCI-MSI-edge...

...handle kernel NULL pointer dereference at 000000000000003e [10542399.523469] IP: [<ffffffffa1491a4b>] find_appropriate_src+0xdb/0x1a0 [nf_nat] [10542399.530843] PGD 17f55ec067 PUD 17fba37067 PMD 0 [10542399.535727] Oops: 0000 [#1] SMP [10542399.539220] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map [10542399.547355] CPU 8 [10542399.647544] Supported: Yes, External [10542399.651361] Pid: 0, comm: swapper Tainted: P NX 2.6.32.43-0.4-default #1 Thurley [10542399.659755] RIP: 0010:[<ffffffffa1491a4b>] [<ffffffffa1491a4b>] find_appropriate_src+0xdb...

...1M Active, 1351M Inact, 2905M Wired, 8K Cache, 7488K Buf, 85G Free ARC: 1073M Total, 107M MRU, 828M MFU, 784K Anon, 7647K Header, 130M Other Swap: 8192M Total, 8192M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 24 155 ki31 0K 384K CPU23 23 431.4H 847.95% idle 0 root 248 -8 0 0K 3968K - 1 10:24 89.45% kernel 2880 _relayd 1 79 0 69608K 54764K *unp_l 22 18:47 25.68% relayd 2879 _relayd 1 80 0 49128K 34232K *unp_l 6 9:22 25.29% relayd 2881 _relayd 1 79 0 7370...

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

...U19 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU20 (XEN) CMCI: CPU20 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU21 (XEN) CMCI: CPU21 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU22 (XEN) CMCI: CPU22 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU23 (XEN) CMCI: CPU23 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU24 (XEN) CMCI: CPU24 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU25 (XEN) CMCI: CPU25 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU26 (XEN) CMCI: CPU26 owner_map[b], no_cmci_map[14] (XEN) CMCI:...

...bus_scale = 0x00008834 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET ?(XEN) Allocated console ring of 256 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU13 resumed (XEN) microcode.c:73:d32767 microcode: CPU23 resumed (XEN) microcode.c:73:d32767 microcode: CPU21 resumed (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) microcode.c:73:d32767 microcode: CPU22 resumed (XEN) microcode.c:73:d32767 microcode: CPU10 resumed (XEN) microcode.c:73:d32767 microcode: CPU11 resumed (XEN) microcode.c:73:d32767...

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so