From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C16BF902 for ; Sat, 24 Jun 2017 22:42:19 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 30AD51E2 for ; Sat, 24 Jun 2017 22:42:19 +0000 (UTC) Date: Sat, 24 Jun 2017 18:42:16 -0400 From: Steven Rostedt To: Andrew Lunn Message-ID: <20170624184216.2ffd4a96@gandalf.local.home> In-Reply-To: <20170624140659.GM4875@lunn.ch> References: <20170619052146.GA2889@jagdpanzerIV.localdomain> <20170619103912.2edbf88a@gandalf.local.home> <20170619152055.GM3786@lunn.ch> <20170619122651.57ba27c4@gandalf.local.home> <20170624081411.58b4fb6a@vento.lan> <20170624140659.GM4875@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Mauro Carvalho Chehab , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] printk redesign List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 24 Jun 2017 16:06:59 +0200 Andrew Lunn wrote: > > If someone reports me a bug that the Kernel crashed because of some > > driver, I would ask him to enable debug messages and send the crash > > logs with it enabled. > > We also need a clear indication that ordering is broken and should not > be trusted when we get a crash log from some random user. When ordering is not ensured, then we can force timestamps. And I like the idea of the time stamp happening when the printk is called, not when it actually goes to the buffer. That way, we could see the timestamps out of order, and sequence them during postmortem. -- Steve