All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Re: 4.12.0-rc5+git: kernel BUG at arch/x86/mm/highmem_32.c:47
Date: Wed, 28 Jun 2017 00:26:26 +0200	[thread overview]
Message-ID: <20170627222626.opk2qkfj4wcue6bf@pd.tnic> (raw)
In-Reply-To: <alpine.LRH.2.20.1706271847300.28262@math.ut.ee>

On Tue, Jun 27, 2017 at 06:49:14PM +0300, Meelis Roos wrote:
> > > This is 4.12.0-rc5-00137-ga090bd4ff838 on a dual AthlonMP server tha has 
> > > been running fine until 4.11.0 included. 4.12.0-rc5-00137-ga090bd4ff838 
> > > was the first kernel after 4.11 that I tried and the problem happened 
> > > while compiling next kernel from git.
> > 
> > I can't reproduce this in a guest. Can you send .config please?
> 
> Here it is.

Thanks.

So plain 4.12.0-rc7 booted all the way in the athlon guest here. So I
either can't reproduce in the guest or I need to try linux-next. Well,
tomorrow...

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2017-06-27 22:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24 20:39 4.12.0-rc5+git: kernel BUG at arch/x86/mm/highmem_32.c:47 Meelis Roos
2017-06-26 10:53 ` Borislav Petkov
2017-06-27 15:49   ` Meelis Roos
2017-06-27 22:26     ` Borislav Petkov [this message]
2017-06-28  4:49       ` Meelis Roos
2017-06-28 10:20       ` Meelis Roos
2017-07-03 10:39         ` Thomas Gleixner
2017-07-03 11:32           ` Meelis Roos
2017-07-06 12:50       ` Meelis Roos

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=20170627222626.opk2qkfj4wcue6bf@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=x86@kernel.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.