On Fri, Oct 04, 2019 at 10:49:28AM +0100, Julien Grall wrote:
> Hi Brian,
>
> On 04/10/2019 01:25, Brian Woods wrote:
> >
> >In the log, there's:
> >(XEN) MODULE[0]: 0140 - 015328f1 Xen
> >(XEN) MODULE[1]: 076d2000 - 076dc080 Device Tree
> >(XEN) MODULE[2]:
Hi Brian,
On 04/10/2019 01:25, Brian Woods wrote:
On Thu, Oct 03, 2019 at 10:20:36PM +0100, Julien Grall wrote:
Hi Brian,
On 10/3/19 9:24 PM, Brian Woods wrote:
On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
There's a WARN_ON() between the two debug printks calls I shared above
On Thu, Oct 03, 2019 at 10:20:36PM +0100, Julien Grall wrote:
> Hi Brian,
>
> On 10/3/19 9:24 PM, Brian Woods wrote:
> >On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
> >There's a WARN_ON() between the two debug printks calls I shared above.
>
> Looking at the log, the MFN seems to
Hi Brian,
On 10/3/19 9:24 PM, Brian Woods wrote:
On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
There's a WARN_ON() between the two debug printks calls I shared above.
Looking at the log, the MFN seems to correspond to the one right after
Xen (0140 - 015328f
On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 19:15, Brian Woods wrote:
> > On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> > (XEN) BW_DEBUG: .6 count_info=0x
> > (XEN) Domain heap initialised
> > (XEN) BW_DEBUG: 01 count_info
Hi,
On 03/10/2019 19:15, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> (XEN) BW_DEBUG: .6 count_info=0x
> (XEN) Domain heap initialised
> (XEN) BW_DEBUG: 01 count_info=0x0180
>
> Those debug messages sandwich end_boot_allocator()
On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 00:20, Brian Woods wrote:
> >On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> >>That's odd. I know I copied your and Stefano's email addresses from the
> >>MAINTAINERS file but under my sent emails
Hi,
On 03/10/2019 00:20, Brian Woods wrote:
On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
Hi,
On 10/2/19 7:56 PM, Brian Woods wrote:
Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
send to a
On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
> > Hi,
> >
> > On 10/2/19 7:56 PM, Brian Woods wrote:
> >
> > Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
> > send to a separate directory any
On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
> Hi,
>
> On 10/2/19 7:56 PM, Brian Woods wrote:
> >On 10/2/19 5:52 PM, Julien Grall wrote:
> >>On 10/2/19 1:32 AM, Brian Woods wrote:
> >>>Hello,
> >>
> >>Hi Brian,
> >>
> >>Thank you for report.
> >>
> >>I guess this Arm specific, rig
Hi,
On 10/2/19 7:56 PM, Brian Woods wrote:
On 10/2/19 5:52 PM, Julien Grall wrote:
On 10/2/19 1:32 AM, Brian Woods wrote:
Hello,
Hi Brian,
Thank you for report.
I guess this Arm specific, right? If so, please try to CC
the relevant maintainers and possibly add "arm" in the
subject to avoid
On 10/2/19 5:52 PM, Julien Grall wrote:
>On 10/2/19 1:32 AM, Brian Woods wrote:
>>Hello,
>
>Hi Brian,
>
>Thank you for report.
>
>I guess this Arm specific, right? If so, please try to CC
>the relevant maintainers and possibly add "arm" in the
>subject to avoid any delay (Xen-Devel has quite an hig
Sorry I forgot to CC xen-devel back.
On 10/2/19 5:52 PM, Julien Grall wrote:
On 10/2/19 1:32 AM, Brian Woods wrote:
Hello,
Hi Brian,
Thank you for report.
I guess this Arm specific, right? If so, please try to CC
the relevant maintainers and possibly add "arm" in the
subject to avoid any de
Hello,
While testing some things out, I found a possible bug in Xen. Xen would
successfully run when loaded (from u-boot) at some addresses but not
others. I didn't observe this issue in 4.11 stable, so I did a bisect
and found that:
commit f60658c6ae47e74792e6cc48ea2effac8bb52826
Author: Julien
14 matches
Mail list logo
