Re: Xen HVM Panic, HEAD
Hi Adrian, On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, Since this is the (at least) second round of x2apic support broke me changes, can we please either back them out or set it to default to '0' for now? I don't think that is necessary. This is -current and there is a tunable to disable x2apic on platforms that are experiencing issues. More importantly the issues that have been reported are being resolved in a timely manner (for e.g., suspend/resume). best Neel Thanks, -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
On Thu, Feb 19, 2015 at 11:50:49AM -0800, Neel Natu wrote: Hi Adrian, On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, Since this is the (at least) second round of x2apic support broke me changes, can we please either back them out or set it to default to '0' for now? I don't think that is necessary. This is -current and there is a tunable to disable x2apic on platforms that are experiencing issues. More importantly the issues that have been reported are being resolved in a timely manner (for e.g., suspend/resume). There is only one really enigmatic issue, it was reported that sandy bridge laptop being unable to start APs. Koop stopped responding, so the issue is not progresed. My current idea is that a cause might be reduced intervals between init/startup ipis due to x2apic not requiring wait for icr idle. Anyway, I do not see it worth even discussing the revert or default' frobbing for now. The commit went mostly event-less for such kind of change. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This panic starts at: https://svnweb.freebsd.org/base?view=revisionrevision=278473 If I use 278472, I can boot the Xen VM normally. If I use head and set hw.x2apic_enable=0 in loader.conf and boot head (278970), it boots normally. Second issue: However, the UFS disk access is SO slow on this that it took 2+hours to do an installworld, which I couldn't abort because it had already started. I'm not sure if the UFS disk access is related at all or not. Once things are read from disk into memory they are fast and responsive (e.g. sshd, tmux, shells, etc). sean bcc royger Maybe helpful, verbose dmesg on bootup with x2apic disabled: https://people.freebsd.org/~sbruno/xen_dmesg_verbose.txt sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJU5mIxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kZewH/j/Fy9b8tteEM68ZGti3XZAK jLDkr8m21pFO8YxPYWrWhXp4f6pvLnTbUIjq5V+8nlCTK+douRfhy8OvG4lW2a5r Hvgwc147mDBpELtlByijsasc9ulkUveI7pSDDSu49dD8RBCOBhGjkfr4iU1tiSbI NHog3vBKk5IYV0u4pynyq1ROMESMNtHSfobt1oHgzxUS1xWHcv4YvnWK05dLM07D lU+g8sY9aBtU8L+IPlAtQW8fZFTwt1RO5oPk3BveA32KxV90vO9bJ2AyHl821/US Fo0NU8zhOuCYaSLF43xexEH1h3EQbjLJho6YslHtIaLqqE0cqpBhnbfKHsE4SmA= =H6sT -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This panic starts at: https://svnweb.freebsd.org/base?view=revisionrevision=278473 If I use 278472, I can boot the Xen VM normally. If I use head and set hw.x2apic_enable=0 in loader.conf and boot head (278970), it boots normally. Second issue: However, the UFS disk access is SO slow on this that it took 2+hours to do an installworld, which I couldn't abort because it had already started. I'm not sure if the UFS disk access is related at all or not. Once things are read from disk into memory they are fast and responsive (e.g. sshd, tmux, shells, etc). sean bcc royger BTW, my kernconf for this contains: include GENERIC ident BLOG nooptions DDB nooptions GDB nooptions DEADLKRES nooptions INVARIANTS # Enable calls of extra sanity checking nooptions INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect deadlocks and cycles nooptions WITNESS_SKIPSPIN# Don't run witness on spinlocks for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zone -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJU5iDJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kiOEIAM5UWud6DGlGgQM5PsHmP4nO LMiAyq2bIE/MtaR13IZL1hv9zBKHAYva9CyaAiAVDFtOSP6nR+/zcxi2SlkNbO9Z lmERNmIs2AvfZiX/+krqVJXcI0MoeXO+9WSpz1SuUo1kXRaWXYNuTDw2qG0lbG/e 282EyNBIg4Jz+KfcTK/cmKQCc1jCMA7Fwym1G7Lwfd8HwxaqJFGa446Y6vle8UZt BSa52DOUP5D0RswByXzNS4aqMI9fLJRcTQZSrY15lUAYmi8uF37n+u8KH7dzbRM+ czW3vJpwckJieA5h+EmV0bABplT3L80/JhdA6vXF98kgrq+6b7xPVowmmvxECfQ= =MPg8 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 12:30, Sean Bruno wrote:
On 02/17/15 12:26, Konstantin Belousov wrote:
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above
this that are relevant to this panic, but XENHVM kernel's
now panic booting on Xen server. The working kernel output
looks like this:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final
208032) 20140512 XEN: Hypervisor version 4.2 detected.
CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
(2400.05-MHz K8-class CPU) Origin=GenuineIntel
Id=0x206c2 Family=0x6 Model=0x2c Stepping=2
Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT
Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV
AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD
Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM
real memory = 1434451968 (1368 MB) avail memory =
1353293824 (1290 MB) Event timer LAPIC quality 400 ACPI
APIC Table: Xen HVM FreeBSD/SMP: Multiprocessor System
Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0
(BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing
APIC ID to 1 MADT: Forcing active-low polarity and level
trigger for SCI
I am not sure why your machine uses native lapic instead of
xen lapic, and should it be other way, or not.
Regardless, show the line number for the ipi_startup+0x56.
Did you performed clean kernel build ?
I have rebuilt a kernel/world based on head at svn r276627. I
have delete /usr/obj completely and started from scratch.
Updated kernelpanic image at
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
/usr/src/sys/x86/include # kgdb /boot/kernel/kernel GNU gdb
6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are welcome to change it and/or distribute
copies of it under certain conditions. Type show copying to
see the conditions. There is absolutely no warranty for GDB.
Type show warranty for details. This GDB was configured as
amd64-marcel-freebsd... (kgdb) list *(ipi_startup+0x56)
0x80e088c6 is in ipi_startup (apicvar.h:383). 378 379
static inline int 380 lapic_ipi_wait(int delay) 381 { 382 383
return (apic_ops.ipi_wait(delay)); 384 } 385 386 static inline
int 387 lapic_set_lvt_mask(u_int apic_id, u_int lvt, u_char
masked)
Please disassemble your ipi_startup, also please do 'p
*apic_ops'.
(kgdb) disassemble ipi_startup
Dump of assembler code for function ipi_startup: 0x80df3900
ipi_startup+0: push %rbp 0x80df3901
ipi_startup+1: mov%rsp,%rbp 0x80df3904
ipi_startup+4: push %r14 0x80df3906
ipi_startup+6: push %rbx 0x80df3907
ipi_startup+7: mov%esi,%ebx 0x80df3909
ipi_startup+9: mov%edi,%r14d 0x80df390c
ipi_startup+12:mov$0xc500,%edi 0x80df3911
ipi_startup+17:mov%r14d,%esi 0x80df3914
ipi_startup+20:callq *0x815ac428 0x80df391b
ipi_startup+27:mov$0x14,%edi 0x80df3920
ipi_startup+32:callq *0x815ac438 0x80df3927
ipi_startup+39:mov$0x8500,%edi 0x80df392c
ipi_startup+44:mov%r14d,%esi 0x80df392f
ipi_startup+47:callq *0x815ac428 0x80df3936
ipi_startup+54:mov$0x2710,%edi 0x80df393b
ipi_startup+59:callq 0x80f39c10 DELAY
0x80df3940 ipi_startup+64:or $0x4600,%ebx
0x80df3946 ipi_startup+70:movslq %ebx,%rbx
0x80df3949 ipi_startup+73:mov%rbx,%rdi
0x80df394c ipi_startup+76:mov%r14d,%esi
0x80df394f ipi_startup+79:callq *0x815ac428
0x80df3956 ipi_startup+86:mov$0x14,%edi
0x80df395b ipi_startup+91:callq *0x815ac438
0x80df3962 ipi_startup+98:test %eax,%eax
0x80df3964 ipi_startup+100: je 0x80df399b
ipi_startup+155 0x80df3966 ipi_startup+102: mov
$0xc8,%edi 0x80df396b ipi_startup+107: callq
0x80f39c10 DELAY 0x80df3970 ipi_startup+112:
mov%rbx,%rdi 0x80df3973 ipi_startup+115: mov
%r14d,%esi 0x80df3976 ipi_startup+118: callq
*0x815ac428 0x80df397d ipi_startup+125: mov
$0x14,%edi 0x80df3982 ipi_startup+130: callq
*0x815ac438 0x80df3989 ipi_startup+137: test
%eax,%eax 0x80df398b ipi_startup+139: je
0x80df39a4
Re: Xen HVM Panic, HEAD
Hi, Since this is the (at least) second round of x2apic support broke me changes, can we please either back them out or set it to default to '0' for now? Thanks, -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 12:26, Konstantin Belousov wrote:
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this
that are relevant to this panic, but XENHVM kernel's now
panic booting on Xen server. The working kernel output looks
like this:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final
208032) 20140512 XEN: Hypervisor version 4.2 detected. CPU:
Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz
K8-class CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6
Model=0x2c Stepping=2
Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT
Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV
AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD
Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real
memory = 1434451968 (1368 MB) avail memory = 1353293824
(1290 MB) Event timer LAPIC quality 400 ACPI APIC Table:
Xen HVM FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT:
Forcing active-low polarity and level trigger for SCI
I am not sure why your machine uses native lapic instead of
xen lapic, and should it be other way, or not.
Regardless, show the line number for the ipi_startup+0x56. Did
you performed clean kernel build ?
I have rebuilt a kernel/world based on head at svn r276627. I
have delete /usr/obj completely and started from scratch.
Updated kernelpanic image at
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
/usr/src/sys/x86/include # kgdb /boot/kernel/kernel GNU gdb 6.1.1
[FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is
free software, covered by the GNU General Public License, and you
are welcome to change it and/or distribute copies of it under
certain conditions. Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty
for details. This GDB was configured as
amd64-marcel-freebsd... (kgdb) list *(ipi_startup+0x56)
0x80e088c6 is in ipi_startup (apicvar.h:383). 378 379
static inline int 380lapic_ipi_wait(int delay) 381 { 382 383
return (apic_ops.ipi_wait(delay)); 384 } 385 386 static inline
int 387 lapic_set_lvt_mask(u_int apic_id, u_int lvt, u_char
masked)
Please disassemble your ipi_startup, also please do 'p *apic_ops'.
(kgdb) disassemble ipi_startup
Dump of assembler code for function ipi_startup:
0x80df3900 ipi_startup+0: push %rbp
0x80df3901 ipi_startup+1: mov%rsp,%rbp
0x80df3904 ipi_startup+4: push %r14
0x80df3906 ipi_startup+6: push %rbx
0x80df3907 ipi_startup+7: mov%esi,%ebx
0x80df3909 ipi_startup+9: mov%edi,%r14d
0x80df390c ipi_startup+12:mov$0xc500,%edi
0x80df3911 ipi_startup+17:mov%r14d,%esi
0x80df3914 ipi_startup+20:callq *0x815ac428
0x80df391b ipi_startup+27:mov$0x14,%edi
0x80df3920 ipi_startup+32:callq *0x815ac438
0x80df3927 ipi_startup+39:mov$0x8500,%edi
0x80df392c ipi_startup+44:mov%r14d,%esi
0x80df392f ipi_startup+47:callq *0x815ac428
0x80df3936 ipi_startup+54:mov$0x2710,%edi
0x80df393b ipi_startup+59:callq 0x80f39c10 DELAY
0x80df3940 ipi_startup+64:or $0x4600,%ebx
0x80df3946 ipi_startup+70:movslq %ebx,%rbx
0x80df3949 ipi_startup+73:mov%rbx,%rdi
0x80df394c ipi_startup+76:mov%r14d,%esi
0x80df394f ipi_startup+79:callq *0x815ac428
0x80df3956 ipi_startup+86:mov$0x14,%edi
0x80df395b ipi_startup+91:callq *0x815ac438
0x80df3962 ipi_startup+98:test %eax,%eax
0x80df3964 ipi_startup+100: je 0x80df399b
ipi_startup+155
0x80df3966 ipi_startup+102: mov$0xc8,%edi
0x80df396b ipi_startup+107: callq 0x80f39c10 DELAY
0x80df3970 ipi_startup+112: mov%rbx,%rdi
0x80df3973 ipi_startup+115: mov%r14d,%esi
0x80df3976 ipi_startup+118: callq *0x815ac428
0x80df397d ipi_startup+125: mov$0x14,%edi
0x80df3982 ipi_startup+130: callq *0x815ac438
0x80df3989 ipi_startup+137: test %eax,%eax
0x80df398b ipi_startup+139: je 0x80df39a4
ipi_startup+164
0x80df398d ipi_startup+141: mov$0xc8,%edi
Xen HVM Panic, HEAD
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png I suspect that there may be one or two more lines above this that are relevant to this panic, but XENHVM kernel's now panic booting on Xen server. The working kernel output looks like this: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz K8-class CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real memory = 1434451968 (1368 MB) avail memory = 1353293824 (1290 MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI bcc: royger@ -- The information in this message may be confidential. It is intended solely for the addressee(s). If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that
are relevant to this panic, but XENHVM kernel's now panic booting
on Xen server. The working kernel output looks like this:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032)
20140512 XEN: Hypervisor version 4.2 detected. CPU: Intel(R)
Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz K8-class
CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6 Model=0x2c
Stepping=2
Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT
Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV
AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD
Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real
memory = 1434451968 (1368 MB) avail memory = 1353293824 (1290
MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP:
1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC
ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low
polarity and level trigger for SCI
I am not sure why your machine uses native lapic instead of xen
lapic, and should it be other way, or not.
Regardless, show the line number for the ipi_startup+0x56. Did you
performed clean kernel build ?
I have rebuilt a kernel/world based on head at svn r276627. I have
delete /usr/obj completely and started from scratch.
Updated kernelpanic image at
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
/usr/src/sys/x86/include # kgdb /boot/kernel/kernel
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as amd64-marcel-freebsd...
(kgdb) list *(ipi_startup+0x56)
0x80e088c6 is in ipi_startup (apicvar.h:383).
378
379 static inline int
380 lapic_ipi_wait(int delay)
381 {
382
383 return (apic_ops.ipi_wait(delay));
384 }
385
386 static inline int
387 lapic_set_lvt_mask(u_int apic_id, u_int lvt, u_char masked)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQF8BAEBCgBmBQJU453BXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5k9PcH/07PKefR3xkJT0W10i2xHYcp
5jNoVfPCP+crWcP7OOqfLY9aQr3KDx5GDZtb/nMbQ36YfCfB5LwAX0cJcGqVbAby
LeznkBqzHa/KPl5RtHtQKPGi25YVm6Q+3mDbH/eGN9DcYwpuNyGrwd7J08XAioux
8UIMCzSy57GlUwMdr6EMOUIP8Uz5Fhm4cryTBhMgAzdIoXnTGIdG1jpatwvXQmtx
dFH3c+vDlJdo3eqA34kufw3yENEjvOd10SVmw1RVs4KJX8pcTJMxRZs4VbayEAFb
V/2FlunDsWnKGm8ybPXrUzSkGgKlQsmaM+gPRiUNpSc9tncnekX9YxqEt36UEJM=
=n5pr
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that
are relevant to this panic, but XENHVM kernel's now panic booting
on Xen server. The working kernel output looks like this:
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032)
20140512 XEN: Hypervisor version 4.2 detected. CPU: Intel(R)
Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz K8-class
CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6 Model=0x2c
Stepping=2
Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT
Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV
AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD
Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real
memory = 1434451968 (1368 MB) avail memory = 1353293824 (1290
MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP:
1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC
ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low
polarity and level trigger for SCI
I am not sure why your machine uses native lapic instead of xen
lapic, and should it be other way, or not.
Regardless, show the line number for the ipi_startup+0x56. Did you
performed clean kernel build ?
I have rebuilt a kernel/world based on head at svn r276627. I have
delete /usr/obj completely and started from scratch.
Updated kernelpanic image at
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
/usr/src/sys/x86/include # kgdb /boot/kernel/kernel
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as amd64-marcel-freebsd...
(kgdb) list *(ipi_startup+0x56)
0x80e088c6 is in ipi_startup (apicvar.h:383).
378
379 static inline int
380 lapic_ipi_wait(int delay)
381 {
382
383 return (apic_ops.ipi_wait(delay));
384 }
385
386 static inline int
387 lapic_set_lvt_mask(u_int apic_id, u_int lvt, u_char masked)
Please disassemble your ipi_startup, also please do 'p *apic_ops'.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://people.freebsd.org/~sbruno/Xen_APIC_panic.png I suspect that there may be one or two more lines above this that are relevant to this panic, but XENHVM kernel's now panic booting on Xen server. The working kernel output looks like this: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz K8-class CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real memory = 1434451968 (1368 MB) avail memory = 1353293824 (1290 MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI I am not sure why your machine uses native lapic instead of xen lapic, and should it be other way, or not. Regardless, show the line number for the ipi_startup+0x56. Did you performed clean kernel build ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://people.freebsd.org/~sbruno/Xen_APIC_panic.png I suspect that there may be one or two more lines above this that are relevant to this panic, but XENHVM kernel's now panic booting on Xen server. The working kernel output looks like this: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz K8-class CPU) Origin=GenuineIntel Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT Features2=0x81ba2201SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF Hypervisor: Origin = XenVMMXenVMM real memory = 1434451968 (1368 MB) avail memory = 1353293824 (1290 MB) Event timer LAPIC quality 400 ACPI APIC Table: Xen HVM FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI bcc: royger@ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJU4r8bXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kOTcH/R4jzSNBELU+Jc1E0N7b97wS pRzbL69AQaDnjI8yCHvMX9AwmqC1x4Fd+bpk4Xqf9Aut9SHZTUhlZlw3BAqZfPmj ofPaaDn3B4AUIMW/K1yPUE7tup1GlM+hSdX4czoBzzO3wKC5aBz4qgv+Peb2FMDe LwEoeWpbJFu5y11uITN0en08bdRAg7B+gJCPkPbzY+W6m0RKpWJ8PavXNfxlMTYt WQThTEy8SdRIPQRdAKURYSqWAPkfMP2s07h4Ckm9rXybbLWCQBYMwJZxhcDfXWlz EoYLHoQ2nt0dT3Lu9lxH8EppCZpVQRAnVLYYB6tBpeDt9boNpNxoJ0UuOf906AM= =EspR -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
