All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Môshe van der Sterre" <me-A/3C56C7qwM@public.gmane.org>
To: Sai Praneeth
	<sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Matt Fleming
	<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
	Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>,
	Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: BGRT doesn't work for me on efi-next
Date: Thu, 17 Dec 2015 17:30:45 +0100	[thread overview]
Message-ID: <5672E335.8000004@moshe.nl> (raw)
In-Reply-To: <5667E7B5.3080705-A/3C56C7qwM@public.gmane.org>

Hello Sai and others,

The change to use early_mem*() instead of early_io*() in 50a0cb56 does 
not work on my machine. Last week I discussed some BGRT changes and I 
created a patch for that, but can't test it on efi-next because of this.

I get this (when booting 50a0cb56, without any of my changes):
[    0.026936] ------------[ cut here ]------------
[    0.026941] WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:137 
__early_ioremap+0x102/0x1bb()
[    0.026941] Modules linked in:
[    0.026944] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-rc1 #2
[    0.026945] Hardware name: Dell Inc. XPS 13 9343/09K8G1, BIOS A05 
07/14/2015
[    0.026946]  0000000000000000 900f03d5a116524d ffffffff81c03e60 
ffffffff813a3fff
[    0.026948]  0000000000000000 ffffffff81c03e98 ffffffff810a0852 
00000000d7b76000
[    0.026949]  0000000000000000 0000000000000001 0000000000000001 
000000000000017c
[    0.026951] Call Trace:
[    0.026955]  [<ffffffff813a3fff>] dump_stack+0x44/0x55
[    0.026958]  [<ffffffff810a0852>] warn_slowpath_common+0x82/0xc0
[    0.026959]  [<ffffffff810a099a>] warn_slowpath_null+0x1a/0x20
[    0.026961]  [<ffffffff81d8c395>] __early_ioremap+0x102/0x1bb
[    0.026962]  [<ffffffff81d8c602>] early_memremap+0x13/0x15
[    0.026964]  [<ffffffff81d78361>] efi_bgrt_init+0x162/0x1ad
[    0.026966]  [<ffffffff81d778ec>] efi_late_init+0x9/0xb
[    0.026968]  [<ffffffff81d58ff5>] start_kernel+0x46f/0x49f
[    0.026970]  [<ffffffff81d58120>] ? early_idt_handler_array+0x120/0x120
[    0.026972]  [<ffffffff81d58339>] x86_64_start_reservations+0x2a/0x2c
[    0.026974]  [<ffffffff81d58485>] x86_64_start_kernel+0x14a/0x16d
[    0.026977] ---[ end trace f9b3812eb8e24c58 ]---
[    0.026978] efi_bgrt: Ignoring BGRT: failed to map image memory

This is the second early_memremap call in efi_bgrt_init triggering 
WARN_ON(nrpages > NR_FIX_BTMAPS). Can you comment on this?

Greetings,
Môshe van der Sterre

       reply	other threads:[~2015-12-17 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5665E8E0.4050203@moshe.nl>
     [not found] ` <20151207204451.GC16222@cloud>
     [not found]   ` <56660979.5080204@moshe.nl>
     [not found]     ` <20151207235520.GA17617@cloud>
     [not found]       ` <566623B3.8010104@moshe.nl>
     [not found]         ` <20151208023443.GA10087@x>
     [not found]           ` <56664F79.6060100@moshe.nl>
     [not found]             ` <20151208140529.GH2518@codeblueprint.co.uk>
     [not found]               ` <5667E7B5.3080705@moshe.nl>
     [not found]                 ` <5667E7B5.3080705-A/3C56C7qwM@public.gmane.org>
2015-12-17 16:30                   ` Môshe van der Sterre [this message]
     [not found]                     ` <5672E335.8000004-A/3C56C7qwM@public.gmane.org>
2015-12-18 12:56                       ` BGRT doesn't work for me on efi-next Matt Fleming
     [not found]                         ` <20151218125628.GA2638-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-18 13:22                           ` Juergen Gross
2015-12-20 19:24                           ` Môshe van der Sterre

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=5672E335.8000004@moshe.nl \
    --to=me-a/3c56c7qwm@public.gmane.org \
    --cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
    --cc=sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.