Displaying 20 results from an estimated 31 matches for "cpu8".
Did you mean:
cpu
2012 Apr 24
3
xen acpi cpufreq driver
Hi,
i''m not sure if i understood the new acpi xen cpufreq driver - here''s the
output when loading xen_acpi_processor module in linux 3.4:
dom0 dmesg:
[ 32.728151] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU8
[ 32.728156] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU9
[ 32.728160] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU10
[ 32.728164] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU11
[ 32.728168] xen-acpi-processor: (CX): Hypervisor error (-22)...
2010 Oct 27
2
Why is cpu-to-node mapping different between Xen 4.0.2-rc1-pre and Xen 4.1-unstable?
...) idx1 -> NODE1 start->1703936 size->1572863
(XEN) phys_to_nid(00000001a0001000) -> 1 should be 1
(XEN) CPU0 -> NODE0
(XEN) CPU1 -> NODE1
(XEN) CPU2 -> NODE0
(XEN) CPU3 -> NODE1
(XEN) CPU4 -> NODE0
(XEN) CPU5 -> NODE1
(XEN) CPU6 -> NODE0
(XEN) CPU7 -> NODE1
(XEN) CPU8 -> NODE0
(XEN) CPU9 -> NODE1
(XEN) CPU10 -> NODE0
(XEN) CPU11 -> NODE1
(XEN) CPU12 -> NODE0
(XEN) CPU13 -> NODE1
(XEN) CPU14 -> NODE0
(XEN) CPU15 -> NODE1
CPU-to-node mapping for Xen 4.1-unstable (xen_changeset:Mon Oct 18
17:40:08 2010 +0100 22262:c0a39dbc624d):
(XEN) **...
2010 Jan 26
1
Bug#567025: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
...stepping 05
(XEN) Booting processor 8/1 eip 8c000
(XEN) Initializing CPU#8
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) Intel machine check reporting enabled on CPU#8.
(XEN) CPU8: Thermal monitoring enabled (TM1)
(XEN) CMCI: find owner on CPU8
(XEN) CMCI: CPU8 owner_map[0], no_cmci_map[93]
(XEN) CPU8: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 9/17 eip 8c000
(XEN) Initializing CPU#9
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) C...
2010 Jan 26
1
Bug#567026: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
...stepping 05
(XEN) Booting processor 8/1 eip 8c000
(XEN) Initializing CPU#8
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) Intel machine check reporting enabled on CPU#8.
(XEN) CPU8: Thermal monitoring enabled (TM1)
(XEN) CMCI: find owner on CPU8
(XEN) CMCI: CPU8 owner_map[0], no_cmci_map[93]
(XEN) CPU8: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 9/17 eip 8c000
(XEN) Initializing CPU#9
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) C...
2009 Jul 27
0
Problems with power management xen 3.4
...@ 2.40GHz stepping 05
(XEN) Booting processor 6/22 eip 8c000
(XEN) CPU6: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05
(XEN) Booting processor 7/6 eip 8c000
(XEN) CPU7: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05
(XEN) Booting processor 8/17 eip 8c000
(XEN) CPU8: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05
(XEN) Booting processor 9/1 eip 8c000
(XEN) CPU9: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05
(XEN) Booting processor 10/19 eip 8c000
(XEN) CPU10: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping 05
(XEN)...
2017 Apr 14
4
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...found a fix/workaround for my reboot issues with Xen 4.6.3-12 + Kernel 4.9.13:
Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
[Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
installing Xen timer for CPU 8
[Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
------------[ cut here ]------------
kernel BUG at arch/x86/kernel/cpu/common.c:997!
invalid opcode: 0000 [#1] SMP
Modules linked in:
CPU: 8 PID: 0 Comm: swapper/8 Not tainted 4.9.13-22.el7.x86_64 #1
Ha...
2008 Nov 13
5
BAD TRAP with Crossbow Beta October 31 2008
...39;'s not so pleasing is the fact that after installing this,
the computer now get very frequent kernel panics. Sometimes it
stays up for less than an hour before crashing.
The crashes look like this:
Nov 12 14:04:15 bahamut unix: [ID 836849 kern.notice]
Nov 12 14:04:15 bahamut ^Mpanic[cpu8]/thread=2a101695ca0:
Nov 12 14:04:15 bahamut unix: [ID 799565 kern.notice] BAD TRAP: type=34 rp=2a101694c30 addr=60014b2f652 mmu_fsr=0
Nov 12 14:04:15 bahamut unix: [ID 100000 kern.notice]
Nov 12 14:04:15 bahamut unix: [ID 839527 kern.notice] sched:
Nov 12 14:04:15 bahamut unix: [ID 123557 kern....
2017 Apr 14
4
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...4.6.3-12 + Kernel 4.9.13:
>>
>> Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
>>
>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>> installing Xen timer for CPU 8
>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>> ------------[ cut here ]------------
>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>> invalid opcode: 0000 [#1] SMP
>> Modules linked in:
>> CPU: 8 PID: 0...
2009 Nov 22
4
Xen 3.4.2 DomU Network Issues
...E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 6/20 eip 8c000
(XEN) CPU6: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 7/22 eip 8c000
(XEN) CPU7: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 8/1 eip 8c000
(XEN) CPU8: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 9/3 eip 8c000
(XEN) CPU9: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 10/5 eip 8c000
(XEN) CPU10: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting pr...
2017 Apr 14
0
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...reboot issues with Xen 4.6.3-12 + Kernel 4.9.13:
>
> Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
>
> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
> installing Xen timer for CPU 8
> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
> ------------[ cut here ]------------
> kernel BUG at arch/x86/kernel/cpu/common.c:997!
> invalid opcode: 0000 [#1] SMP
> Modules linked in:
> CPU: 8 PID: 0 Comm: swapper/8 Not tain...
2008 Jun 20
1
zfs corruption...
...ly caused by a failure
in
the Veritas Cluster in which two nodes tried to write to the same zpool
simultaneously. If not that, perhaps some random driver error or
bug… I don’t know. All theories aside, here is the output of
the error we see every time the `zpool import home` command fails:
panic[cpu8]/thread=2a100b69cc0:
ZFS: bad checksum (read on off 0: zio 60015f26a40 [L0
packed
nvlist] 4000L/400P DVA[0]=<0:4000b7000:400>
DVA[1]=<0:4600063800:400> fletcher4 lzjb BE contiguous
birth=3865837
fill=1 cksum=6e858ee992:2cad0296498c:cae1d40ad3d38:2e1daaef734ef08):
error...
2017 Apr 18
2
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...> Once I finally got serial output all the way through the boot process
> (xen+dom0) I discovered the stack trace:
> >>>
> >>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
> >>> installing Xen timer for CPU 8
> >>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
> >>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
> >>> ------------[ cut here ]------------
> >>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
> >>> invalid opcode: 0000 [#1] SMP
> >>&g...
2013 May 24
0
Problem After adding Bricks
...54.2%sy, 0.0%ni, 1.0%id, 8.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu5 : 36.9%us, 53.0%sy, 0.0%ni, 2.0%id, 8.1%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu6 : 38.6%us, 54.0%sy, 0.0%ni, 1.3%id, 5.7%wa, 0.0%hi, 0.3%si, 0.0%st
Cpu7 : 34.3%us, 59.3%sy, 0.0%ni, 2.4%id, 4.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu8 : 36.5%us, 55.7%sy, 0.0%ni, 3.4%id, 4.4%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu9 : 34.7%us, 59.2%sy, 0.0%ni, 0.7%id, 5.4%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu10 : 34.9%us, 58.2%sy, 0.0%ni, 1.7%id, 5.1%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu11 : 38.4%us, 55.0%sy, 0.0%ni, 1.0%id, 5.6%wa, 0.0%hi, 0.0%...
2017 Apr 18
2
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...l the way through the boot
>>> process (xen+dom0) I discovered the stack trace:
>>> >>>
>>> >>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>>> >>> installing Xen timer for CPU 8
>>> >>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>>> >>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>>> >>> ------------[ cut here ]------------
>>> >>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>>> >>> invalid opcod...
2017 Apr 18
0
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...13:
>>>
>>> Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
>>>
>>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>>> installing Xen timer for CPU 8
>>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>>> ------------[ cut here ]------------
>>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>>> invalid opcode: 0000 [#1] SMP
>>> Modules linked in:
>...
2017 Apr 14
0
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...:
>>>
>>> Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
>>>
>>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>>> installing Xen timer for CPU 8
>>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>>> ------------[ cut here ]------------
>>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>>> invalid opcode: 0000 [#1] SMP
>>> Modules linked in:
>...
2012 Nov 13
1
thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC
...0K 384K RUN 6 18.4H 31.88% idle{idle: cpu6}
11 root 155 ki31 0K 384K RUN 1 18.4H 31.79% idle{idle: cpu1}
11 root 155 ki31 0K 384K RUN 19 18.3H 31.59% idle{idle: cpu19}
11 root 155 ki31 0K 384K RUN 8 18.4H 30.96% idle{idle: cpu8}
7619 dovenull 81 0 59048K 32864K CPU20 20 2:01 30.96% imap-login
11 root 155 ki31 0K 384K CPU18 18 18.3H 30.76% idle{idle: cpu18}
11 root 155 ki31 0K 384K RUN 13 18.3H 30.57% idle{idle: cpu13}
11 root 155 ki31 0K 384K RUN...
2017 Apr 18
0
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...got serial output all the way through the boot process
>> (xen+dom0) I discovered the stack trace:
>> >>>
>> >>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>> >>> installing Xen timer for CPU 8
>> >>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>> >>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>> >>> ------------[ cut here ]------------
>> >>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>> >>> invalid opcode: 0000 [#1] SMP...
2010 Jul 19
1
packet loss on ixgbe using vlans and ipv6
Hi,
I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel
82599 cards). It is running FreeBSD RELENG_8 last updated on July 13.
What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the
machine is not the originator of the packets.
Let me try to describe a little more. If a neigbouring machine ping6 it,
there will be packet loss. If it act as a router for ipv6,
2017 Apr 18
0
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
...e boot
>>>> process (xen+dom0) I discovered the stack trace:
>>>> >>>
>>>> >>> [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7
>>>> >>> installing Xen timer for CPU 8
>>>> >>> [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20
>>>> >>> smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>>>> >>> ------------[ cut here ]------------
>>>> >>> kernel BUG at arch/x86/kernel/cpu/common.c:997!
>>>> >>&g...