[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F31CBD158@ORSMSX106.amr.corp.intel.com>
Date: Thu, 15 Aug 2013 19:14:34 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"rjw@...k.pl" <rjw@...k.pl>,
"lance.ortiz@...com" <lance.ortiz@...com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error
trace event
> Well, if I have serial connected to the box, it will contain basically
> everything the machine said, no?
Yes - but the serial port is too slow to log everything that you might
conceivably need to debug your problem. Imagine trying to log every
interrupt and every pagefault on every processor down a single 115200
baud connection. Thus my earlier comments about guessing what to
log.
-Tony
Powered by blists - more mailing lists