[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091113125946.5353164c@marrow.netinsight.se>
Date: Fri, 13 Nov 2009 12:59:46 +0100
From: Simon Kagstrom <simon.kagstrom@...insight.net>
To: dedekind1@...il.com
Cc: David VomLehn <dvomlehn@...co.com>,
Marco Stornelli <marco.stornelli@...il.com>,
linux-embedded@...r.kernel.org, akpm@...ux-foundation.org,
dwmw2@...radead.org, linux-kernel@...r.kernel.org, mpm@...enic.com,
paul.gortmaker@...driver.com,
"Shargorodsky Atal (EXT-Teleca/Helsinki)"
<ext-atal.shargorodsky@...ia.com>
Subject: Re: [PATCH, RFC] panic-note: Annotation from user space for panics
(Also fix David Woodhouses address and add Atal)
On Fri, 13 Nov 2009 13:45:48 +0200
Artem Bityutskiy <dedekind1@...il.com> wrote:
> So we really need to print some user-space supplied information during
> the panic, and then we store it on flash with mtdoops, and the later,
> when the device has network access we send whole bunch of oopses via the
> network.
Yes, I see that your case would have to be handled differently. A
complication (which I believe was discussed before) is that kmsg_dump()
is done before the panic notifiers are called.
The reason I put it there is to have it before crash_kexec(), so I
guess we'll have to take up the discussion on what to do with it. For
me it now seems like it would be OK to move kmsg_dump() down below the
panic notifiers.
If you have a kdump kernel to load, then you will most likely not need
the kmsg dumped data anyway.
// Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists