mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC PATCH] x86/debug: Dump more detailed segfault info
Date: Tue, 15 Nov 2016 11:22:01 +0100	[thread overview]
Message-ID: <20161115102201.wewvjts7uj2663pv@pd.tnic> (raw)
In-Reply-To: <20161115101903.GA15249@gmail.com>

On Tue, Nov 15, 2016 at 11:19:03AM +0100, Ingo Molnar wrote:
> Well, bfd8d3f23b51 was part of -rc1 already, so you have it too.

Right.

> What might have made the difference is that I tested it on real hardware with 
> serial logging, which delays printk() and might have created the race with the 
> systemd kernel logger. (Which is impossible to turn off :-( )

Of course it is!

printk.devkmsg=off

:-)

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2016-11-15 10:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 10:19 Borislav Petkov
2016-11-12 11:06 ` Ingo Molnar
2016-11-12 12:27   ` Borislav Petkov
2016-11-13  7:39     ` Ingo Molnar
2016-11-13 11:25       ` Borislav Petkov
2016-11-13 15:49         ` Borislav Petkov
2016-11-15  6:14           ` Ingo Molnar
2016-11-15 10:06             ` Borislav Petkov
2016-11-15 10:19               ` Ingo Molnar
2016-11-15 10:22                 ` Borislav Petkov [this message]
2016-11-15 10:38                   ` Ingo Molnar
2016-11-13 16:15     ` Andy Lutomirski
2016-11-14  6:18       ` Borislav Petkov
2016-11-17 23:33         ` Andy Lutomirski
2016-11-18 12:38           ` Borislav Petkov

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=20161115102201.wewvjts7uj2663pv@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®