On Sat, 15 Mar, at 03:26:25PM, Borislav Petkov wrote:
>
> Btw, Matt, your whole efi/next stuff is already in tip, right? Because
> if so, Linn could simply test latest tip/master.
Yep, everything is in tip/master.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this
On Sat, Mar 15, 2014 at 03:26:25PM +0100, Borislav Petkov wrote:
> Also, please try to catch full dmesg and the whole oops.
Ok, nevermind, I've got your mail with full dmesg in my other mbox; I'll
take a look next week.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-k
On Fri, Mar 14, 2014 at 02:27:06PM -0600, Linn Crosetto wrote:
> Since this testing was done on a prototype, I will send you the log in
> a separate email. I tried efi.git/next (with the addition of 4ce7a86),
> and hit the same panic.
Well, if the stack trace is the same:
> ? __unmap_pmd_range+0
On Fri, Mar 14, 2014 at 08:26:15AM +, Matt Fleming wrote:
> On Fri, 14 Mar, at 10:47:26AM, Dave Young wrote:
> >
> > Can you test with matt's tree to see if it works?
> > If it still happens please post the full log.
>
> So that'd be the 'next' branch at,
>
> git://git.kernel.org/pub/scm/l
On Fri, 14 Mar, at 10:47:26AM, Dave Young wrote:
>
> Can you test with matt's tree to see if it works?
> If it still happens please post the full log.
So that'd be the 'next' branch at,
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
which contains Borislav's fixes for the EFI
> [..]
>
> I tested on a prototype system with 231 entries in the map with good results.
> Everything succeeds when using kexec to initiate a fast reboot. For crash, it
> works with and without --pass-memmap-cmdline when using noefi. I hit the
> following panic when initiating a crash leaving EFI
6 matches
Mail list logo
