Re: Xen dom0 crash

2015-10-21 Thread Roger Pau Monné
El 21/10/15 a les 11.02, Eggert, Lars ha escrit:
> On 2015-10-21, at 10:53, Roger Pau Monné  wrote:
>> hw.pci.mcfg=0
> 
> Thanks! That gets me a bit further, but it now crashes with:
> 
> ...
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #14 Launched!
> SMP: AP CPU #11 Launched!
> SMP: AP CPU #21 Launched!
> SMP: AP CPU #30 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #20 Launched!
> panic: xen_pv_lapic_enable_pmc: not available in Xen PV port.
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x81fd5990
> vpanic() at vpanic+0x182/frame 0x81fd5a10
> panic() at panic+0x43/frame 0x81fd5a70
> xen_pv_lapic_enable_pmc() at xen_pv_lapic_enable_pmc+0x19/frame 
> 0x81fd5a80
> pmc_md_initialize() at pmc_md_initialize+0x3c/frame 0x81fd5aa0
> load() at load+0x41e/frame 0x81fd5af0
> syscall_module_handler() at syscall_module_handler+0x290/frame 
> 0x81fd5b20
> module_register_init() at module_register_init+0xfb/frame 0x81fd5b50
> mi_startup() at mi_startup+0x108/frame 0x81fd5b70
> xen_start() at xen_start+0x1f
> KDB: enter: panic
> [ thread pid 0 tid 10 ]
> Stopped at  kdb_enter+0x3b: movq$0,kdb_why
> db>

Hello,

Are you loading hwpmc by default? Performance monitor counters are not
yet implemented in the FreeBSD PVH port, so you should not load hwpmc. I
have to look at providing an error message here rather than panicking.

Roger.

___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"


Re: Xen dom0 crash

2015-10-21 Thread Eggert, Lars
On 2015-10-21, at 11:11, Roger Pau Monné  wrote:
> Are you loading hwpmc by default?

Yes.

> Performance monitor counters are not
> yet implemented in the FreeBSD PVH port, so you should not load hwpmc. I
> have to look at providing an error message here rather than panicking.

Strange, the same kernel config worked earlier. But without hwmpc, the it now 
boots.

Thanks!

Lars


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Xen dom0 crash

2015-10-21 Thread Roger Pau Monné
El 21/10/15 a les 11.51, Eggert, Lars ha escrit:
> On 2015-10-21, at 11:11, Roger Pau Monné  wrote:
>> Are you loading hwpmc by default?
> 
> Yes.
> 
>> Performance monitor counters are not
>> yet implemented in the FreeBSD PVH port, so you should not load hwpmc. I
>> have to look at providing an error message here rather than panicking.
> 
> Strange, the same kernel config worked earlier. But without hwmpc, the it now 
> boots.

It might well be that Xen is exposing different cpuid flags in 4.6 vs
4.5, and that makes hwpmc attach. All the cpuid stuff in PVH is still
in-flux.

Roger.

___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"


Re: Xen dom0 crash

2015-10-21 Thread Roger Pau Monné
El 20/10/15 a les 17.13, Eggert, Lars ha escrit:
> Hi,
> 
> with a recent -CURRENT and xen-4.6.0, I now see a different crash at boot on 
> the same box. Any ideas?
> 
> Thanks,
> Lars
> 
> 
> B2
>   __      _ _
>  |  | |  _ \ / |  __ \
>  | |___ _ __ ___  ___ | |_) | (___ | |  | |
>  |  ___| '__/ _ \/ _ \|  _ < \___ \| |  | |
>  | |   | | |  __/  __/| |_) |) | |__| |
>  | |   | | |||| |  |  |
>  Xen 4.6.0el/cc_vegas.ko size 0x3348 at 0x1403000`
> (XEN) Xen version 4.6.0 (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 
> 4.7.4) debug=n Wed Oct 14 18:50:20 CEST 2015g...el/cc_hd.ko size 0x2ea8 at 
> 0x13ff000o   .--` /y:`  +.
> (XEN) Latest ChangeSet: 'ertt' |  yo`:.:o  `+-
> (XEN) Bootloader: FreeBSD Loader   |   y/   -/`   -o/
> (XEN) Command line: guest_loglvl=all loglvl=al dom0_max_vcpus=32 
> dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com13. [Esc]ape to loader 
> prompt   |  / `--  /
> (XEN) Video information:   | `:  :`
> (XEN)  VGA is text mode 80x25, font 8x16   | `:  :`
> (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds  /
> (XEN)  EDID info not retrieved because no DDC retrieval method detected -.
> (XEN) Disc information:O]ptions... |   --  -.
> (XEN)  Found 1 MBR signatures  |`:`  `:`
> (XEN)  Found 1 EDD information structures  |  .-- `--.
> (XEN) Xen-e820 RAM map:| .---..
> (XEN)   - 0009ac00 (usable)
> (XEN)  0009ac00 - 000a (reserved)
> (XEN)  000e - 0010 (reserved)
> (XEN)  0010 - 7de19000 (usable)
> (XEN)  7de19000 - 7dea8000 (reserved)
> (XEN)  7dea8000 - 7dfb1000 (ACPI data)
> (XEN)  7dfb1000 - 7e1cb000 (ACPI NVS)
> (XEN)  7e1cb000 - 7f355000 (reserved)
> (XEN)  7f355000 - 7f80 (ACPI NVS)
> (XEN)  8000 - 9000 (reserved)
> (XEN)  fed1c000 - fed4 (reserved)
> (XEN)  ff00 - 0001 (reserved)
> (XEN)  0001 - 00208000 (usable)
> (XEN) ACPI: RSDP 000F04A0, 0024 (r2 SUPERM)
> (XEN) ACPI: XSDT 7DEDD088, 008C (r1 SUPERM SMCI--MB1 AMI 10013)
> (XEN) ACPI: FACP 7DEE80F8, 00F4 (r4 SUPERM SMCI--MB1 AMI 10013)
> (XEN) ACPI: DSDT 7DEDD1A0, AF53 (r2 SUPERM SMCI--MB0 INTL 20091112)
> (XEN) ACPI: FACS 7E1C2080, 0040
> (XEN) ACPI: APIC 7DEE81F0, 0224 (r31 AMI 10013)
> (XEN) ACPI: FPDT 7DEE8418, 0044 (r11 AMI 10013)
> (XEN) ACPI: HPET 7DEE8460, 0038 (r1 SUPERM SMCI--MB1 AMI.5)
> (XEN) ACPI: PRAD 7DEE8498, 00BE (r2 PRADID  PRADTID1 MSFT  400)
> (XEN) ACPI: SPMI 7DEE8558, 0040 (r5 A M I   OEMSPMI0 AMI.0)
> (XEN) ACPI: SSDT 7DEE8598, C7AE8 (r2  INTELCpuPm 4000 INTL 20091112)
> (XEN) ACPI: EINJ 7DFB0080, 0130 (r1AMI AMI EINJ0 0)
> (XEN) ACPI: ERST 7DFB01B0, 0230 (r1  AMIER AMI ERST0 0)
> (XEN) ACPI: HEST 7DFB03E0, 00A8 (r1AMI AMI HEST0 0)
> (XEN) ACPI: BERT 7DFB0488, 0030 (r1AMI AMI BERT0 0)
> (XEN) ACPI: DMAR 7DFB04B8, 0168 (r1 A M I   OEMDMAR1 INTL1)
> (XEN) ACPI: MCFG 7DFB0620, 003C (r1 SUPERM SMCI--MB1 MSFT   97)
> (XEN) System RAM: 131037MB (134182604kB)
> (XEN) Domain heap initialised
> (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7e1c2080/, 
> using 32
> (XEN) Processor #0 6:13 APIC version 21
> (XEN) Processor #2 6:13 APIC version 21
> (XEN) Processor #4 6:13 APIC version 21
> (XEN) Processor #6 6:13 APIC version 21
> (XEN) Processor #8 6:13 APIC version 21
> (XEN) Processor #10 6:13 APIC version 21
> (XEN) Processor #12 6:13 APIC version 21
> (XEN) Processor #14 6:13 APIC version 21
> (XEN) Processor #32 6:13 APIC version 21
> (XEN) Processor #34 6:13 APIC version 21
> (XEN) Processor #36 6:13 APIC version 21
> (XEN) Processor #38 6:13 APIC version 21
> (XEN) Processor #40 6:13 APIC version 21
> (XEN) Processor #42 6:13 APIC version 21
> (XEN) Processor #44 6:13 APIC version 21
> (XEN) Processor #46 6:13 APIC version 21
> (XEN) Processor #1 6:13 APIC version 21
> (XEN) Processor #3 6:13 APIC version 21
> (XEN) Processor #5 6:13 APIC version 21
> (XEN) Processor #7 6:13 APIC version 21
> (XEN) Processor #9 6:13 APIC version 21
> (XEN) Processor #11 6:13 APIC version 21
> (XEN) Processor #13 6:13 APIC version 21
> (XEN) Processor #15 6:13 APIC version 21
> (XEN) Processor #33 6:13 APIC version 21
> (XEN) Processor 

Re: Xen dom0 crash

2015-10-21 Thread Roger Pau Monné
El 21/10/15 a les 10.33, Eggert, Lars ha escrit:
> On 2015-10-21, at 9:40, Roger Pau Monné  wrote:
>> Can you execute:
>>
>> # addr2line -e /boot/kernel/kernel 8097bf80
>>
>> In order to get the file and line where the failure happens?
> 
> I guess you meant kernel.debug? Then I get:
> 
> /usr/home/elars/src/sys/amd64/pci/pci_cfgreg.c:365
> 
> Which is the __asm line in case 1 in pciereg_cfgwrite().

Hello,

Yes, I knew about this, sorry, with Xen 4.6 you need to add:

hw.pci.mcfg=0

to your /boot/loader.conf. This is because Xen prevents us from writing
at the PCI-e memory mapped config and we need to switch back to using
the IO ports.

Roger.

___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"


Re: Xen dom0 crash

2015-10-21 Thread Eggert, Lars
On 2015-10-21, at 10:53, Roger Pau Monné  wrote:
> hw.pci.mcfg=0

Thanks! That gets me a bit further, but it now crashes with:

...
SMP: AP CPU #7 Launched!
SMP: AP CPU #14 Launched!
SMP: AP CPU #11 Launched!
SMP: AP CPU #21 Launched!
SMP: AP CPU #30 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #20 Launched!
panic: xen_pv_lapic_enable_pmc: not available in Xen PV port.
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x81fd5990
vpanic() at vpanic+0x182/frame 0x81fd5a10
panic() at panic+0x43/frame 0x81fd5a70
xen_pv_lapic_enable_pmc() at xen_pv_lapic_enable_pmc+0x19/frame 
0x81fd5a80
pmc_md_initialize() at pmc_md_initialize+0x3c/frame 0x81fd5aa0
load() at load+0x41e/frame 0x81fd5af0
syscall_module_handler() at syscall_module_handler+0x290/frame 
0x81fd5b20
module_register_init() at module_register_init+0xfb/frame 0x81fd5b50
mi_startup() at mi_startup+0x108/frame 0x81fd5b70
xen_start() at xen_start+0x1f
KDB: enter: panic
[ thread pid 0 tid 10 ]
Stopped at  kdb_enter+0x3b: movq$0,kdb_why
db>

Lars


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Xen dom0 crash

2015-10-20 Thread Eggert, Lars
On 2015-10-20, at 17:13, Eggert, Lars  wrote:
> with a recent -CURRENT and xen-4.6.0, I now see a different crash at boot on 
> the same box. Any ideas?

Actually, it's a different box (Supermicro)

Lars

> 
> Thanks,
> Lars
> 
> 
>B2
>  __      _ _
> |  | |  _ \ / |  __ \
> | |___ _ __ ___  ___ | |_) | (___ | |  | |
> |  ___| '__/ _ \/ _ \|  _ < \___ \| |  | |
> | |   | | |  __/  __/| |_) |) | |__| |
> | |   | | |||| |  |  |
> Xen 4.6.0el/cc_vegas.ko size 0x3348 at 0x1403000`
> (XEN) Xen version 4.6.0 (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 
> 4.7.4) debug=n Wed Oct 14 18:50:20 CEST 2015g...el/cc_hd.ko size 0x2ea8 at 
> 0x13ff000o   .--` /y:`  +.
> (XEN) Latest ChangeSet: 'ertt' |  yo`:.:o  `+-
> (XEN) Bootloader: FreeBSD Loader   |   y/   -/`   -o/
> (XEN) Command line: guest_loglvl=all loglvl=al dom0_max_vcpus=32 
> dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com13. [Esc]ape to loader 
> prompt   |  / `--  /
> (XEN) Video information:   | `:  :`
> (XEN)  VGA is text mode 80x25, font 8x16   | `:  :`
> (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds  /
> (XEN)  EDID info not retrieved because no DDC retrieval method detected -.
> (XEN) Disc information:O]ptions... |   --  -.
> (XEN)  Found 1 MBR signatures  |`:`  `:`
> (XEN)  Found 1 EDD information structures  |  .-- `--.
> (XEN) Xen-e820 RAM map:| .---..
> (XEN)   - 0009ac00 (usable)
> (XEN)  0009ac00 - 000a (reserved)
> (XEN)  000e - 0010 (reserved)
> (XEN)  0010 - 7de19000 (usable)
> (XEN)  7de19000 - 7dea8000 (reserved)
> (XEN)  7dea8000 - 7dfb1000 (ACPI data)
> (XEN)  7dfb1000 - 7e1cb000 (ACPI NVS)
> (XEN)  7e1cb000 - 7f355000 (reserved)
> (XEN)  7f355000 - 7f80 (ACPI NVS)
> (XEN)  8000 - 9000 (reserved)
> (XEN)  fed1c000 - fed4 (reserved)
> (XEN)  ff00 - 0001 (reserved)
> (XEN)  0001 - 00208000 (usable)
> (XEN) ACPI: RSDP 000F04A0, 0024 (r2 SUPERM)
> (XEN) ACPI: XSDT 7DEDD088, 008C (r1 SUPERM SMCI--MB1 AMI 10013)
> (XEN) ACPI: FACP 7DEE80F8, 00F4 (r4 SUPERM SMCI--MB1 AMI 10013)
> (XEN) ACPI: DSDT 7DEDD1A0, AF53 (r2 SUPERM SMCI--MB0 INTL 20091112)
> (XEN) ACPI: FACS 7E1C2080, 0040
> (XEN) ACPI: APIC 7DEE81F0, 0224 (r31 AMI 10013)
> (XEN) ACPI: FPDT 7DEE8418, 0044 (r11 AMI 10013)
> (XEN) ACPI: HPET 7DEE8460, 0038 (r1 SUPERM SMCI--MB1 AMI.5)
> (XEN) ACPI: PRAD 7DEE8498, 00BE (r2 PRADID  PRADTID1 MSFT  400)
> (XEN) ACPI: SPMI 7DEE8558, 0040 (r5 A M I   OEMSPMI0 AMI.0)
> (XEN) ACPI: SSDT 7DEE8598, C7AE8 (r2  INTELCpuPm 4000 INTL 20091112)
> (XEN) ACPI: EINJ 7DFB0080, 0130 (r1AMI AMI EINJ0 0)
> (XEN) ACPI: ERST 7DFB01B0, 0230 (r1  AMIER AMI ERST0 0)
> (XEN) ACPI: HEST 7DFB03E0, 00A8 (r1AMI AMI HEST0 0)
> (XEN) ACPI: BERT 7DFB0488, 0030 (r1AMI AMI BERT0 0)
> (XEN) ACPI: DMAR 7DFB04B8, 0168 (r1 A M I   OEMDMAR1 INTL1)
> (XEN) ACPI: MCFG 7DFB0620, 003C (r1 SUPERM SMCI--MB1 MSFT   97)
> (XEN) System RAM: 131037MB (134182604kB)
> (XEN) Domain heap initialised
> (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7e1c2080/, 
> using 32
> (XEN) Processor #0 6:13 APIC version 21
> (XEN) Processor #2 6:13 APIC version 21
> (XEN) Processor #4 6:13 APIC version 21
> (XEN) Processor #6 6:13 APIC version 21
> (XEN) Processor #8 6:13 APIC version 21
> (XEN) Processor #10 6:13 APIC version 21
> (XEN) Processor #12 6:13 APIC version 21
> (XEN) Processor #14 6:13 APIC version 21
> (XEN) Processor #32 6:13 APIC version 21
> (XEN) Processor #34 6:13 APIC version 21
> (XEN) Processor #36 6:13 APIC version 21
> (XEN) Processor #38 6:13 APIC version 21
> (XEN) Processor #40 6:13 APIC version 21
> (XEN) Processor #42 6:13 APIC version 21
> (XEN) Processor #44 6:13 APIC version 21
> (XEN) Processor #46 6:13 APIC version 21
> (XEN) Processor #1 6:13 APIC version 21
> (XEN) Processor #3 6:13 APIC version 21
> (XEN) Processor #5 6:13 APIC version 21
> (XEN) Processor #7 6:13 APIC version 21
> (XEN) Processor #9 6:13 APIC version 21
> (XEN) Processor #11 6:13 APIC version 21
> (XEN) Processor #13 6:13 APIC version 21
> (XEN) Processor #15 6:13 APIC version 21
> (XEN) 

Re: Xen dom0 crash

2015-10-20 Thread Eggert, Lars
Hi,

with a recent -CURRENT and xen-4.6.0, I now see a different crash at boot on 
the same box. Any ideas?

Thanks,
Lars


B2
  __      _ _
 |  | |  _ \ / |  __ \
 | |___ _ __ ___  ___ | |_) | (___ | |  | |
 |  ___| '__/ _ \/ _ \|  _ < \___ \| |  | |
 | |   | | |  __/  __/| |_) |) | |__| |
 | |   | | |||| |  |  |
 Xen 4.6.0el/cc_vegas.ko size 0x3348 at 0x1403000`
(XEN) Xen version 4.6.0 (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 
4.7.4) debug=n Wed Oct 14 18:50:20 CEST 2015g...el/cc_hd.ko size 0x2ea8 at 
0x13ff000o   .--` /y:`  +.
(XEN) Latest ChangeSet: 'ertt' |  yo`:.:o  `+-
(XEN) Bootloader: FreeBSD Loader   |   y/   -/`   -o/
(XEN) Command line: guest_loglvl=all loglvl=al dom0_max_vcpus=32 dom0_mem=4096M 
dom0pvh=1 com1=115200,8n1 console=com13. [Esc]ape to loader prompt   |  
/ `--  /
(XEN) Video information:   | `:  :`
(XEN)  VGA is text mode 80x25, font 8x16   | `:  :`
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds  /
(XEN)  EDID info not retrieved because no DDC retrieval method detected -.
(XEN) Disc information:O]ptions... |   --  -.
(XEN)  Found 1 MBR signatures  |`:`  `:`
(XEN)  Found 1 EDD information structures  |  .-- `--.
(XEN) Xen-e820 RAM map:| .---..
(XEN)   - 0009ac00 (usable)
(XEN)  0009ac00 - 000a (reserved)
(XEN)  000e - 0010 (reserved)
(XEN)  0010 - 7de19000 (usable)
(XEN)  7de19000 - 7dea8000 (reserved)
(XEN)  7dea8000 - 7dfb1000 (ACPI data)
(XEN)  7dfb1000 - 7e1cb000 (ACPI NVS)
(XEN)  7e1cb000 - 7f355000 (reserved)
(XEN)  7f355000 - 7f80 (ACPI NVS)
(XEN)  8000 - 9000 (reserved)
(XEN)  fed1c000 - fed4 (reserved)
(XEN)  ff00 - 0001 (reserved)
(XEN)  0001 - 00208000 (usable)
(XEN) ACPI: RSDP 000F04A0, 0024 (r2 SUPERM)
(XEN) ACPI: XSDT 7DEDD088, 008C (r1 SUPERM SMCI--MB1 AMI 10013)
(XEN) ACPI: FACP 7DEE80F8, 00F4 (r4 SUPERM SMCI--MB1 AMI 10013)
(XEN) ACPI: DSDT 7DEDD1A0, AF53 (r2 SUPERM SMCI--MB0 INTL 20091112)
(XEN) ACPI: FACS 7E1C2080, 0040
(XEN) ACPI: APIC 7DEE81F0, 0224 (r31 AMI 10013)
(XEN) ACPI: FPDT 7DEE8418, 0044 (r11 AMI 10013)
(XEN) ACPI: HPET 7DEE8460, 0038 (r1 SUPERM SMCI--MB1 AMI.5)
(XEN) ACPI: PRAD 7DEE8498, 00BE (r2 PRADID  PRADTID1 MSFT  400)
(XEN) ACPI: SPMI 7DEE8558, 0040 (r5 A M I   OEMSPMI0 AMI.0)
(XEN) ACPI: SSDT 7DEE8598, C7AE8 (r2  INTELCpuPm 4000 INTL 20091112)
(XEN) ACPI: EINJ 7DFB0080, 0130 (r1AMI AMI EINJ0 0)
(XEN) ACPI: ERST 7DFB01B0, 0230 (r1  AMIER AMI ERST0 0)
(XEN) ACPI: HEST 7DFB03E0, 00A8 (r1AMI AMI HEST0 0)
(XEN) ACPI: BERT 7DFB0488, 0030 (r1AMI AMI BERT0 0)
(XEN) ACPI: DMAR 7DFB04B8, 0168 (r1 A M I   OEMDMAR1 INTL1)
(XEN) ACPI: MCFG 7DFB0620, 003C (r1 SUPERM SMCI--MB1 MSFT   97)
(XEN) System RAM: 131037MB (134182604kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 7e1c2080/, 
using 32
(XEN) Processor #0 6:13 APIC version 21
(XEN) Processor #2 6:13 APIC version 21
(XEN) Processor #4 6:13 APIC version 21
(XEN) Processor #6 6:13 APIC version 21
(XEN) Processor #8 6:13 APIC version 21
(XEN) Processor #10 6:13 APIC version 21
(XEN) Processor #12 6:13 APIC version 21
(XEN) Processor #14 6:13 APIC version 21
(XEN) Processor #32 6:13 APIC version 21
(XEN) Processor #34 6:13 APIC version 21
(XEN) Processor #36 6:13 APIC version 21
(XEN) Processor #38 6:13 APIC version 21
(XEN) Processor #40 6:13 APIC version 21
(XEN) Processor #42 6:13 APIC version 21
(XEN) Processor #44 6:13 APIC version 21
(XEN) Processor #46 6:13 APIC version 21
(XEN) Processor #1 6:13 APIC version 21
(XEN) Processor #3 6:13 APIC version 21
(XEN) Processor #5 6:13 APIC version 21
(XEN) Processor #7 6:13 APIC version 21
(XEN) Processor #9 6:13 APIC version 21
(XEN) Processor #11 6:13 APIC version 21
(XEN) Processor #13 6:13 APIC version 21
(XEN) Processor #15 6:13 APIC version 21
(XEN) Processor #33 6:13 APIC version 21
(XEN) Processor #35 6:13 APIC version 21
(XEN) Processor #37 6:13 APIC version 21
(XEN) Processor #39 6:13 APIC version 21
(XEN) Processor #41 6:13 APIC version 21
(XEN) Processor #43 6:13 APIC version 21
(XEN) Processor #45 6:13 APIC version 21
(XEN) 

Re: Xen dom0 crash

2015-05-26 Thread Roger Pau Monné
El 26/05/15 a les 9.30, Eggert, Lars ha escrit:
 On 2015-5-22, at 18:27, Roger Pau Monné roger@citrix.com wrote:

 The issue mentioned in this thread has been fixed in the xen-kernel port
 with the following commit:

 https://svnweb.freebsd.org/ports?view=revisionrevision=386935
 
 Will this make it into upstream Xen?

I hope so, I've already sent the patch and it has been acked by one of
the Intel VMX maintainers, so I guess it's not going to take long before
it's committed:

http://lists.xenproject.org/archives/html/xen-devel/2015-05/msg03068.html

Roger.

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: Xen dom0 crash

2015-05-26 Thread Eggert, Lars
On 2015-5-22, at 18:27, Roger Pau Monné roger@citrix.com wrote:
 
 The issue mentioned in this thread has been fixed in the xen-kernel port
 with the following commit:
 
 https://svnweb.freebsd.org/ports?view=revisionrevision=386935

Will this make it into upstream Xen?

Lars


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roger Pau Monné wrote:

 El 18/05/15 a les 15.04, Eggert, Lars ha escrit:
  Hi,
  
  I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen 
  crashes when starting the kernel. Log below; any ideas?
  
  Thanks,
  Lars
  (XEN) [ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]
  (XEN) CPU:0
  (XEN) RIP::[80854000]
  (XEN) RFLAGS: 0200   CONTEXT: hvm guest (d0v0)
  (XEN) rax:    rbx: 82d0802e8000   rcx: 82d0802eff80
  (XEN) rdx: 82d0801e1500   rsi:    rdi: 82d0801ed77c
  (XEN) rbp: 82d0801061d2   rsp: 81bb5000   r8:  83103ff0
  (XEN) r9:  82d08010623f   r10: 82d0802eff70   r11: 
  (XEN) r12: 82d0802eff50   r13: 831033ae7000   r14: 83103ff0
  (XEN) r15: 82d08018eae3   cr0: 8011   cr4: 0020
  (XEN) cr3: 01ba1000   cr2: 
  (XEN) ds:    es:    fs:    gs:    ss:    cs: 
  (XEN) Guest stack trace from rsp=81bb5000:
  (XEN)   Fault while accessing guest memory.
  (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
  (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 
 Hello,
 
 This looks very similar to the crash reported at:
 
 https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html
 
 Which was also reported at xen-devel, but nobody seems to have looked
 into it.
 
 Could you send a bug report to xen-devel with the following trace
 (please make sure to mention PVH in the subject line) CCing the Intel
 VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen
 source tree).

H,

I'm observing a crash that looks similar to me:

(XEN) [ Xen-4.5.0  x86_64  debug=n  Not tainted ]
(XEN) CPU:0
(XEN) RIP:0020:[8034a2f3]
(XEN) RFLAGS: 00010246   CONTEXT: hvm guest
(XEN) rax: f800d887c1b0   rbx: f8000ed85100   rcx: 
(XEN) rdx: 81788560   rsi: 0008   rdi: f8000ed85100
(XEN) rbp: fe023956a850   rsp: fe023956a850   r8:  815056f8
(XEN) r9:  8178857c   r10: f8000ea9e0f0   r11: 81664200
(XEN) r12: 0004   r13: 80ee832b   r14: f8000ed85118
(XEN) r15: f8000ed85100   cr0: 8005003b   cr4: 000406e0
(XEN) cr3: 02cca000   cr2: 00080a8da140
(XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
(XEN) Guest stack trace from rsp=fe023956a850:
(XEN)   Fault while accessing guest memory.
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

I'm wondering if it's related to the same issue?

It's triggered only when I try to reboot/poweroff the guest.

Roman Bogorodskiy



pgpMB7f3P5A43.pgp
Description: PGP signature


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roman Bogorodskiy wrote:

   Roger Pau Monné wrote:
 
  El 18/05/15 a les 15.04, Eggert, Lars ha escrit:
   Hi,
   
   I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen 
   crashes when starting the kernel. Log below; any ideas?
   
   Thanks,
   Lars
   (XEN) [ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]
   (XEN) CPU:0
   (XEN) RIP::[80854000]
   (XEN) RFLAGS: 0200   CONTEXT: hvm guest (d0v0)
   (XEN) rax:    rbx: 82d0802e8000   rcx: 
   82d0802eff80
   (XEN) rdx: 82d0801e1500   rsi:    rdi: 
   82d0801ed77c
   (XEN) rbp: 82d0801061d2   rsp: 81bb5000   r8:  
   83103ff0
   (XEN) r9:  82d08010623f   r10: 82d0802eff70   r11: 
   
   (XEN) r12: 82d0802eff50   r13: 831033ae7000   r14: 
   83103ff0
   (XEN) r15: 82d08018eae3   cr0: 8011   cr4: 
   0020
   (XEN) cr3: 01ba1000   cr2: 
   (XEN) ds:    es:    fs:    gs:    ss:    cs: 
   (XEN) Guest stack trace from rsp=81bb5000:
   (XEN)   Fault while accessing guest memory.
   (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
   (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
  
  Hello,
  
  This looks very similar to the crash reported at:
  
  https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html
  
  Which was also reported at xen-devel, but nobody seems to have looked
  into it.
  
  Could you send a bug report to xen-devel with the following trace
  (please make sure to mention PVH in the subject line) CCing the Intel
  VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen
  source tree).
 
 H,
 
 I'm observing a crash that looks similar to me:
 
 (XEN) [ Xen-4.5.0  x86_64  debug=n  Not tainted ]
 (XEN) CPU:0
 (XEN) RIP:0020:[8034a2f3]
 (XEN) RFLAGS: 00010246   CONTEXT: hvm guest
 (XEN) rax: f800d887c1b0   rbx: f8000ed85100   rcx: 
 (XEN) rdx: 81788560   rsi: 0008   rdi: f8000ed85100
 (XEN) rbp: fe023956a850   rsp: fe023956a850   r8:  815056f8
 (XEN) r9:  8178857c   r10: f8000ea9e0f0   r11: 81664200
 (XEN) r12: 0004   r13: 80ee832b   r14: f8000ed85118
 (XEN) r15: f8000ed85100   cr0: 8005003b   cr4: 000406e0
 (XEN) cr3: 02cca000   cr2: 00080a8da140
 (XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
 (XEN) Guest stack trace from rsp=fe023956a850:
 (XEN)   Fault while accessing guest memory.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
 (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 
 I'm wondering if it's related to the same issue?
 
 It's triggered only when I try to reboot/poweroff the guest.
 
 Roman Bogorodskiy

And the full log from guest start to crash:

https://dpaste.de/mWNu


Roman Bogorodskiy


pgpX3J5D6I0Rq.pgp
Description: PGP signature


Re: Xen dom0 crash

2015-05-22 Thread Roger Pau Monné
Hello,

El 22/05/15 a les 18.11, Roman Bogorodskiy ha escrit:
 H,
 
 I'm observing a crash that looks similar to me:
 
 (XEN) [ Xen-4.5.0  x86_64  debug=n  Not tainted ]
 (XEN) CPU:0
 (XEN) RIP:0020:[8034a2f3]
 (XEN) RFLAGS: 00010246   CONTEXT: hvm guest
 (XEN) rax: f800d887c1b0   rbx: f8000ed85100   rcx: 
 (XEN) rdx: 81788560   rsi: 0008   rdi: f8000ed85100
 (XEN) rbp: fe023956a850   rsp: fe023956a850   r8:  815056f8
 (XEN) r9:  8178857c   r10: f8000ea9e0f0   r11: 81664200
 (XEN) r12: 0004   r13: 80ee832b   r14: f8000ed85118
 (XEN) r15: f8000ed85100   cr0: 8005003b   cr4: 000406e0
 (XEN) cr3: 02cca000   cr2: 00080a8da140
 (XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
 (XEN) Guest stack trace from rsp=fe023956a850:
 (XEN)   Fault while accessing guest memory.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
 (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 
 I'm wondering if it's related to the same issue?

The issue mentioned in this thread has been fixed in the xen-kernel port
with the following commit:

https://svnweb.freebsd.org/ports?view=revisionrevision=386935

Not sure if binary packages in pkg have been updated or not.

 It's triggered only when I try to reboot/poweroff the guest.

I'm not sure if it's the same issue.

In this case the crash happened when booting Dom0 (well even before
booting Dom0).

Can you please provide the full log (including Xen and FreeBSD boot
output)? With just this chunk it's impossible to guess what's going on.

Also, if I understand it correctly, the crash you are seeing happens
when trying to shutdown/reboot a running DomU?

Roger.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roger Pau Monné wrote:

 El 22/05/15 a les 18.40, Roman Bogorodskiy ha escrit:
  No, the guest is:
  
  FreeBSD 10.0-RELEASE amd64.
  
  Here's dmesg.boot from dom0:
  
  https://dpaste.de/ey7Q
 
 I think I know what's going on, you are using a rather old kernel (from
 27/04/15) which doesn't contain r282634. Could you update your Dom0
 kernel to recent HEAD and try again?

That worked, thanks!

Roman Bogorodskiy


pgptElbXey3Lc.pgp
Description: PGP signature


Re: Xen dom0 crash

2015-05-18 Thread Roger Pau Monné
El 18/05/15 a les 15.04, Eggert, Lars ha escrit:
 Hi,
 
 I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen 
 crashes when starting the kernel. Log below; any ideas?
 
 Thanks,
 Lars
 
 
 B2
   __      _ _
  |  | |  _ \ / |  __ \
  | |___ _ __ ___  ___ | |_) | (___ | |  | |
  |  ___| '__/ _ \/ _ \|  _  \___ \| |  | |
  | |   | | |  __/  __/| |_) |) | |__| |
  | |   | | |||| |  |
  |_|   |_|  \___|\___||/|_/|_/````
  s` `.---...--.```   -/
  +Welcome to FreeBSD   +4H+   .--` /y:`  +.
 /boot/kernel/cc_vegas.ko size 0x30d0 at 0x1068000:.:o  `+-
 Booting...el/cc_hd.ko size 0x2c00 at 0x106200   -/`   -o/
  Xen 4.6-unstabletcp.ko size 0x2f90 at 0x1065000  ::/sy+:.
 (XEN) Xen version 4.6-unstable (r...@netapp.com) (gcc47 (FreeBSD Ports 
 Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015  
 :`
 (XEN) Latest ChangeSet:| `:  :`
 (XEN) Bootloader: FreeBSD Loader   |  /  /
 (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1.
 (XEN) Video information:]ptions... |   --  -.
 (XEN)  VGA is text mode 80x25, font 8x16   |`:`  `:`
 (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds   `--.
 (XEN)  EDID info not retrieved because no DDC retrieval method 
 detected=(XEN) Disc information:
 (XEN)  Found 0 MBR signatures
 (XEN)  Found 0 EDD information structures
 (XEN) Xen-e820 RAM map:+0x50db0 -
 (XEN)   - 0008b800 (usable)
 (XEN)  0008b800 - 000a (reserved)
 (XEN)  000e - 0010 (reserved)
 (XEN)  0010 - 7cb09000 (usable)
 (XEN)  7cb09000 - 7cb39000 (reserved)
 (XEN)  7cb39000 - 7cc52000 (ACPI data)
 (XEN)  7cc52000 - 7d4b (ACPI NVS)
 (XEN)  7d4b - 7eafb000 (reserved)
 (XEN)  7eafb000 - 7eafc000 (usable)
 (XEN)  7eafc000 - 7eb82000 (ACPI NVS)
 (XEN)  7eb82000 - 7f00 (usable)
 (XEN)  8000 - 9000 (reserved)
 (XEN)  fed1c000 - fed2 (reserved)
 (XEN)  ff00 - 0001 (reserved)
 (XEN)  0001 - 00208000 (usable)
 (XEN) ACPI: RSDP 000F04A0, 0024 (r2 FTS   )
 (XEN) ACPI: XSDT 7CB71090, 00A4 (r1 FTSD2939-B1  1072009 AMI 10013)
 (XEN) ACPI: FACP 7CB7FAA8, 010C (r5 FTSD2939-B1  1072009 AMI 10013)
 (XEN) ACPI: DSDT 7CB711C8, E8DD (r2 FTSD2939-B1  114 INTL 20091112)
 (XEN) ACPI: FACS 7D4A7080, 0040
 (XEN) ACPI: APIC 7CB7FBB8, 0294 (r3 FTSD2939-B1  1072009 AMI 10013)
 (XEN) ACPI: FPDT 7CB7FE50, 0044 (r1 FTSD2939-B1  1072009 AMI 10013)
 (XEN) ACPI: MCFG 7CB7FE98, 003C (r1 FTSOEMMCFG.  1072009 MSFT   97)
 (XEN) ACPI: SRAT 7CB7FED8, 0530 (r1 A M I  AMI SRAT1 AMI.0)
 (XEN) ACPI: SLIT 7CB80408, 0030 (r1 A M I  AMI SLIT0 AMI.0)
 (XEN) ACPI: HPET 7CB80438, 0038 (r1 FTSD2939-B1  1072009 AMI.5)
 (XEN) ACPI: PRAD 7CB80470, 00BE (r2 PRADID  PRADTID1 MSFT  301)
 (XEN) ACPI: SPMI 7CB80530, 0040 (r5 A M I   OEMSPMI0 AMI.0)
 (XEN) ACPI: SSDT 7CB80570, D0CB0 (r2  INTELCpuPm 4000 INTL 20051117)
 (XEN) ACPI: SPCR 7CC51220, 0050 (r1  A M I   APTIO4  1072009 AMI.5)
 (XEN) ACPI: EINJ 7CC51270, 0130 (r1AMI AMI EINJ0 0)
 (XEN) ACPI: ERST 7CC513A0, 0230 (r1  AMIER AMI ERST0 0)
 (XEN) ACPI: HEST 7CC515D0, 00A8 (r1AMI AMI HEST0 0)
 (XEN) ACPI: BERT 7CC51678, 0030 (r1AMI AMI BERT0 0)
 (XEN) ACPI: DMAR 7CC516A8, 0110 (r1 A M I   OEMDMAR1 INTL1)
 (XEN) System RAM: 131023MB (134167628kB)
 (XEN) SRAT: PXM 0 - APIC 0 - Node 0
 (XEN) SRAT: PXM 0 - APIC 1 - Node 0
 (XEN) SRAT: PXM 0 - APIC 2 - Node 0
 (XEN) SRAT: PXM 0 - APIC 3 - Node 0
 (XEN) SRAT: PXM 0 - APIC 4 - Node 0
 (XEN) SRAT: PXM 0 - APIC 5 - Node 0
 (XEN) SRAT: PXM 0 - APIC 6 - Node 0
 (XEN) SRAT: PXM 0 - APIC 7 - Node 0
 (XEN) SRAT: PXM 0 - APIC 8 - Node 0
 (XEN) SRAT: PXM 0 - APIC 9 - Node 0
 (XEN) SRAT: PXM 0 - APIC 16 - Node 0
 (XEN) SRAT: PXM 0 - APIC 17 - Node 0
 (XEN) SRAT: PXM 0 - APIC 18 - Node 0
 (XEN) SRAT: PXM 0 - APIC 19 - Node 0
 (XEN) SRAT: PXM 0 - APIC 20 - Node 0
 (XEN) SRAT: PXM 0 - APIC 21 - Node 0
 (XEN) SRAT: PXM 0 - APIC 22 - Node 0
 (XEN) SRAT: PXM 0 - APIC 23 - Node 0
 (XEN) SRAT: PXM 0 - APIC 24 - Node 0
 (XEN) SRAT: PXM 0 - APIC 25 - Node 0
 (XEN) SRAT: PXM 1 - APIC 32 - Node 1
 (XEN) SRAT: PXM 1 - APIC 33 - Node