public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani-VXdhtT5mjnY@public.gmane.org>
To: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: EFI tree kernel panic in phys_efi_set_virtual_address_map()
Date: Thu, 12 Dec 2013 10:36:17 -0700	[thread overview]
Message-ID: <1386869777.1791.314.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1386869221.1791.311.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>

On Thu, 2013-12-12 at 10:27 -0700, Toshi Kani wrote:
> On Thu, 2013-12-12 at 09:43 -0700, Toshi Kani wrote:
> > On Thu, 2013-12-12 at 17:23 +0100, Borislav Petkov wrote:
> > > On Wed, Dec 11, 2013 at 06:10:20PM -0700, Toshi Kani wrote:
> > > > > Unfortunately, it did not work.  Hit the same panic again.
> > > > 
> > > > dmesg output attached.
> > > 
> > > Ok, thanks.
> > > 
> > > Let's have a look at the EFI pagetable then. Please apply the attached
> > > patch, make sure CONFIG_X86_PTDUMP is enabled, build, boot and catch
> > > full dmesg again and send it to me.
> > 
> > Yes, I will test with the change, and send a full dmesg output to you.
> 
> Attached.

BTW, the test system is shared and will be used by other test for a
couple of hours or so.  So, please take your time. :-)

Thanks!
-Toshi

  parent reply	other threads:[~2013-12-12 17:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12  0:01 EFI tree kernel panic in phys_efi_set_virtual_address_map() Toshi Kani
     [not found] ` <1386806463.1791.295.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12  0:29   ` Borislav Petkov
     [not found]     ` <20131212002946.GF8863-fF5Pk5pvG8Y@public.gmane.org>
2013-12-12  0:32       ` Toshi Kani
     [not found]         ` <1386808323.1791.299.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12  1:08           ` Toshi Kani
     [not found]             ` <1386810620.1791.307.camel@misato.fc.hp.com>
     [not found]               ` <1386810620.1791.307.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12 16:23                 ` Borislav Petkov
     [not found]                   ` <20131212162351.GA26927-fF5Pk5pvG8Y@public.gmane.org>
2013-12-12 16:43                     ` Toshi Kani
     [not found]                       ` <1386866583.1791.310.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12 17:27                         ` Toshi Kani
     [not found]                           ` <1386869221.1791.311.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12 17:36                             ` Toshi Kani [this message]
     [not found]                               ` <1386869777.1791.314.camel-RbGIw1UOYPVo/CpIj0byZw@public.gmane.org>
2013-12-12 20:35                                 ` Borislav Petkov
     [not found]                                   ` <20131212203533.GB26927-fF5Pk5pvG8Y@public.gmane.org>
2013-12-12 20:44                                     ` Toshi Kani

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=1386869777.1791.314.camel@misato.fc.hp.com \
    --to=toshi.kani-vxdhtt5mjny@public.gmane.org \
    --cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox