From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Linux as 32-bit Dom0?
Date: Wed, 22 Nov 2017 15:40:10 +0100 [thread overview]
Message-ID: <d2fbfd1d-7f92-c97d-9a05-b3849608b6c3@suse.com> (raw)
In-Reply-To: <5A159246020000780019108B@suse.com>
On 22/11/17 15:05, Jan Beulich wrote:
> Jürgen, Boris,
>
> am I trying something that's not allowed, but selectable via Kconfig?
> On system with multiple IO-APICs (I assume that's what triggers the
> problem) I get
>
> Kernel panic - not syncing: Max apic_id exceeded!
Generally I don't think 32 bit dom0 is forbidden, but rarely used. I
wouldn't be too sad in case we'd decide to drop that support. ;-)
Can you please be a little bit more specific?
How many IOAPICs? From the code I guess this is an INTEL system with not
too recent IOAPIC versions (<0x14)?
Having a little bit more of the boot log might help, too.
Juergen
>
> CPU: 0 PID: 0 Comm: swapper Not tainted 4.14.1-2017-11-21-xen0 #6
> Hardware name: ...
> Call Trace:
> ? show_stack+0x20/0x50
> ? dump_stack+0x7e/0xc0
> ? panic+0x99/0x220
> ? io_apic_get_unique_id+0x207/0x210
> ? __raw_callee_save_xen_restore_fl+0x6/0x8
> ? xen_flush_tlb_single+0x6f/0x80
> ? set_pte_vaddr+0xef/0x110
> ? xen_io_apic_read+0x36/0x90
> ? mp_register_ioapic+0x2b7/0x410
> ? acpi_os_map_iomem+0x14d/0x210
> ? acpi_parse_ioapic+0x6b/0x6f
> ? acpi_parse_entries_array+0xa1/0x16d
> ? acpi_tb_get_table+0x95/0x9d
> ? acpi_ut_release_mutex+0x109/0x10e
> ? acpi_table_parse_entries_array+0x98/0xa8
> ? acpi_table_parse_entries+0x30/0x35
> ? acpi_boot_init+0x65/0x65
> ? acpi_table_parse_madt+0x1b/0x1f
> ? acpi_boot_init+0x65/0x65
> ? acpi_parse_madt_ioapic_entries+0x4a/0x119
> ? mutex_lock+0x8/0x30
> ? acpi_process_madt+0xbe/0x105
> ? acpi_boot_init+0x3d/0x65
> ? setup_arch+0x67a/0x83f
> ? 0xc1000000
> ? start_kernel+0x46/0x361
> ? x86_early_init_platform_quirks+0x4d/0x90
> ? i386_start_kernel+0x22/0x88
> ? xen_start_kernel+0x453/0x639
> (XEN) Hardware Dom0 crashed: 'noreboot' set - not rebooting.
>
> I admit I have a few custom patches in that tree, but I'm reasonably
> certain that none of them comes even close to having such an effect.
>
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2017-11-22 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5A159246020000780019108B@suse.com>
2017-11-22 14:40 ` Juergen Gross [this message]
2017-11-22 14:48 ` Linux as 32-bit Dom0? Jan Beulich
2017-11-22 14:50 ` Boris Ostrovsky
[not found] ` <5A159C4B02000078001910EE@suse.com>
2017-11-23 9:47 ` Juergen Gross
2017-11-22 14:05 Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2fbfd1d-7f92-c97d-9a05-b3849608b6c3@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).