[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121204203640.GB6242@liondog.tnic>
Date: Tue, 4 Dec 2012 21:36:40 +0100
From: Borislav Petkov <bp@...en8.de>
To: Mauro Carvalho Chehab <mchehab@...hat.com>
Cc: "Ortiz, Lance E" <lance.oritz@...com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"lance_ortiz@...mail.com" <lance_ortiz@...mail.com>,
"jiang.liu@...wei.com" <jiang.liu@...wei.com>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 2/3] aerdrv: Enhanced AER logging
On Tue, Dec 04, 2012 at 06:31:10PM -0200, Mauro Carvalho Chehab wrote:
> However, in this particular case, if PCI AER got an error, but the
> device is not found when trying to handle it, it can be an indication
> that the PCI device has a more serious issue. So, I'm in favor
> of changing it, and likely be more verbose at the error message,
> saying that the device was not found while trying to report an error
> condition that happened there. It could make sense to even send a
> trace for the daemon to be aware of the error, on some pci device that
> vanished likely due to the error.
Let's leave it at pr_err now and if we actually start seeing errors like
that and decide that they need more verbose reporting, then to change it
to whatever's best. IOW, do the empirical approach.
Thanks.
--
Regards/Gruss,
Boris.
--
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