On Mon, Feb 17, 2014 at 09:32:36AM -0500, Aristeu Rozanski wrote:
> On Mon, Feb 17, 2014 at 01:10:23PM +0800, Jiang Liu wrote:
> > On a system with four Intel processor, it generates too many messages
> > "EDAC sbridge: Seeking for: dev 1d.3 PCI ID ". And it doesn't
> > give many useful
On Mon, Feb 17, 2014 at 09:32:36AM -0500, Aristeu Rozanski wrote:
On Mon, Feb 17, 2014 at 01:10:23PM +0800, Jiang Liu wrote:
On a system with four Intel processor, it generates too many messages
EDAC sbridge: Seeking for: dev 1d.3 PCI ID . And it doesn't
give many useful information for
On Mon, Feb 17, 2014 at 01:10:23PM +0800, Jiang Liu wrote:
> On a system with four Intel processor, it generates too many messages
> "EDAC sbridge: Seeking for: dev 1d.3 PCI ID ". And it doesn't
> give many useful information for normal users, so change log level
> from INFO to DEBUG.
>
>
On Mon, Feb 17, 2014 at 01:10:23PM +0800, Jiang Liu wrote:
On a system with four Intel processor, it generates too many messages
EDAC sbridge: Seeking for: dev 1d.3 PCI ID . And it doesn't
give many useful information for normal users, so change log level
from INFO to DEBUG.
On a system with four Intel processor, it generates too many messages
"EDAC sbridge: Seeking for: dev 1d.3 PCI ID ". And it doesn't
give many useful information for normal users, so change log level
from INFO to DEBUG.
Signed-off-by: Jiang Liu
---
drivers/edac/sb_edac.c |2 +-
1 file
On a system with four Intel processor, it generates too many messages
EDAC sbridge: Seeking for: dev 1d.3 PCI ID . And it doesn't
give many useful information for normal users, so change log level
from INFO to DEBUG.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
6 matches
Mail list logo
