[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F1936EA97@ORSMSX104.amr.corp.intel.com>
Date: Thu, 19 Jul 2012 22:10:52 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Seiji Aguchi <seiji.aguchi@....com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mikew@...gle.com" <mikew@...gle.com>,
"dzickus@...hat.com" <dzickus@...hat.com>,
"Matthew Garrett (mjg@...hat.com)" <mjg@...hat.com>
CC: "dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: RE: [RFC][PATCH v2 2/3] Hold multiple logs
> If users specify a number of that is too big, the message will be meaningless.
> I just couldn't decide the appropriate number by myself.
> Then, I make it tunable.
I think that 3 or 4 logs should be plenty to cover almost all situations. E.g.
with 3 logs you could capture 2 OOPS (and perhaps miss some other OOPS)
and then get the final panic that kills the system. Messier crashes are of
course possible ... but that would give lots of clues on where the problems
lie.
I was just wondering whether you had successfully stored 2, or 3, or
more logs - and if you'd seen any problems doing so. Matthew seemed
very worried about the amount of available space for EFI.
If you don't know what is the appropriate number ... then how will
users decide? We should really give them some guidance ... especially
if there are odd problems[1] if they pick a number that is too big.
-Tony
[1] I don't know if there will be problems ... I don't know what else
EFI will store here, and what would happen if it ran out of space.
--
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