All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Andryuk <jandryuk@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, andy@strugglers.net
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Problems booting 32-bit PV; just me or more widespread?
Date: Fri, 31 Aug 2018 08:48:36 -0400	[thread overview]
Message-ID: <CAKf6xpvasS53VZZgRPNu1ohHw2AUGBpq1bQY5G3pVumD1kdHqg@mail.gmail.com> (raw)
In-Reply-To: <958fdd6b-f67d-098e-c713-7c50a6b64ce6@oracle.com>

On Thu, Aug 30, 2018 at 6:00 PM Boris Ostrovsky
<boris.ostrovsky@oracle.com> wrote:
>
> On 08/29/2018 08:51 PM, Andy Smith wrote:
> > Hi,
> >
> > I'm sorry this is a long email, but I wanted to explain everything
> > that I have tried, because it seems like quite a few different
> > versions of 32-bit upstream Linux kernel no longer boot as PV guest
> > and I'm surprised I am the first to encounter this. Probably I
> > have done something wrong.
> >
> > I cannot get any of the Ubuntu packaged 32-bit mainline kernels
> > after v4.13.16 that are found at
> > http://kernel.ubuntu.com/~kernel-ppa/mainline/ to boot in 32-bit PV
> > mode. All of them from v4.14.0rc1 onwards crash on xl create either
> > saying "error: no XEN note found."
>
> Don't know what this error is, perhaps kernel was not compiled with
> CONFIG_XEN.

32bit 4.14 stable kernels work for me. Like Boris said, "error: no XEN
note found." makes me think CONFIG_XEN was not set.

> > or else immediately producing a
> > kernel panic like:
> >
> > .
> > .
> > .
> > [ 0.114370] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
> > [ 0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
> > [ 0.114423] pinctrl core: initialized pinctrl subsystem
> > [ 0.134326] RTC time: 165:165:165, date: 165/165/65
> > [ 0.134442] NET: Registered protocol family 16
> > [ 0.134457] xen:grant_table: Grant tables using version 1 layout
> > [ 0.134502] Grant table initialized
> > [ 0.134544] audit: initializing netlink subsys (disabled)
> > [ 0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized audit_enabled=0 res=1
> > [ 0.134678] EISA bus registered
> > [ 0.136019] PCI: setting up Xen PCI frontend stub
> > [ 0.136073] BUG: unable to handle kernel paging request at edc21fd9
> > [ 0.136084] IP: eisa_bus_probe+0x19/0x36
> > [ 0.136089] *pdpt = 0000000001ee6027 *pde = 0000000029cc6067 *pte = 0000000000000000
> > [ 0.136100] Oops: 0000 [#1] SMP
> > [ 0.136105] Modules linked in:
> > [ 0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic #36-Ubuntu
> > [ 0.136120] EIP: eisa_bus_probe+0x19/0x36
> > [ 0.136125] EFLAGS: 00010246 CPU: 0
> > [ 0.136130] EAX: edc21fd9 EBX: 00000000 ECX: 01e0d000 EDX: 00000200
> > [ 0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
> > [ 0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
> > [ 0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e10000 CR4: 00042660
> > [ 0.136166] Call Trace:
> > [ 0.136173] do_one_initcall+0x49/0x174
> > [ 0.136179] ? parse_args+0x143/0x390
> > [ 0.136187] ? set_debug_rodata+0x14/0x14
> > [ 0.136193] kernel_init_freeable+0x149/0x1c5
> > [ 0.136201] ? rest_init+0xa0/0xa0
> > [ 0.136207] kernel_init+0xd/0xf0
> > [ 0.136213] ret_from_fork+0x2e/0x38
> > [ 0.140000] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
> > [ 0.140000] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
> > [ 0.140000] CR2: 00000000edc21fd9
> > [ 0.140000] ---[ end trace 8c00b3cb7d4f06ba ]---
> > [ 0.140013] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
> >
> > (that one was from the currently-packaged linux-image-generic in
> > Ubuntu 18.04 LTS).
>
>
> Yes, this looks like it was broken by f7eaf6e00fd5 ("x86/boot: Move EISA
> setup to a separate file").
>
> We used to use fixmap for EISA addresses, but not anymore. If you can
> build your own kernel you could try the patch below (may be
> whitespace-damaged)

My kernels disable CONFIG_ISA, and therefore CONFIG_EISA, so I haven't hit this.

Regards,
Jason

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-08-31 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  0:51 Problems booting 32-bit PV; just me or more widespread? Andy Smith
2018-08-30 21:59 ` Boris Ostrovsky
2018-08-31 12:48   ` Jason Andryuk [this message]
2018-09-02 22:39   ` Andy Smith
2018-09-03  0:32   ` Andy Smith
2018-09-04 23:53     ` Boris Ostrovsky

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=CAKf6xpvasS53VZZgRPNu1ohHw2AUGBpq1bQY5G3pVumD1kdHqg@mail.gmail.com \
    --to=jandryuk@gmail.com \
    --cc=andy@strugglers.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.