On Wed, 09 Mar, at 10:56:07PM, Matt Fleming wrote:
> On Wed, 09 Mar, at 11:01:18PM, Alexis Murzeau wrote:
> >
> > Indeed I get the "Could not reserve range" message, and with a kernel
> > v4.3 the physical address 0x1 contains the value 1.
> > And this pat
On Wed, 09 Mar, at 11:01:18PM, Alexis Murzeau wrote:
>
> Indeed I get the "Could not reserve range" message, and with a kernel
> v4.3 the physical address 0x1 contains the value 1.
> And this patch works and make a unmodified + this patch 4.4 debian
> kernel boots, nice well found :)
Great, than
On Wed, 09 Mar, at 01:02:44AM, Alexis Murzeau wrote:
>
> Thanks for you suggestion.
> Unfortunately, this patch doesn't make it works, the crash still
> occurs (at the same RIP and traceback).
>
> Using /dev/mem on a running system (with kernel 4.3), the memory
> around RIP (0xaa9462ee) is :
> aa
On Tue, 01 Mar, at 01:03:22AM, Alexis Murzeau wrote:
>
> I've updated my additional debug code to dump all entries of virtual_map
> when calling SetVirtualAddressMap. (new diff of my changes in attachment:
> additionnal_printk_dump_SetVirtualAddressMap.diff)
>
> I've run 3 tests with and without
On Mon, 29 Feb, at 09:34:55PM, Roger Shimizu wrote:
> On Mon, Feb 29, 2016 at 9:25 PM, Matt Fleming
> wrote:
> > On Mon, 29 Feb, at 10:49:54AM, Raphael Hertzog wrote:
> >> Hello Matt and Borislav,
> >>
> >> in Debian we got a report (see below and htt
On Mon, 29 Feb, at 10:49:54AM, Raphael Hertzog wrote:
> Hello Matt and Borislav,
>
> in Debian we got a report (see below and https://bugs.debian.org/815125) that
> https://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit?id=67a9108ed4313b85a9c53406d80dc1ae3f8c3e36
> was breaking early
6 matches
Mail list logo
