Bug#684049: linux-image-3.2.0-3-amd64: syslog flooded with [e|o]hci_hcd related messages

2012-08-07 Thread Juha Heinanen
Ben Hutchings writes:

 I do recognise that syslog should not be filled up with this noise,
 though.  Can you test whether the attached patch fixes this for you?
 Instructions for building a patched kernel package are at
 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.1.

Ben,

Thanks for the patch.  I build and installed patched linux-image and
after that I have not seen those syslog messages anymore.  So looks like
the patch fixed the issue.

-- Juha


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#684049: linux-image-3.2.0-3-amd64: syslog flooded with [e|o]hci_hcd related messages

2012-08-06 Thread Juha Heinanen
Package: src:linux
Version: 3.2.21-3
Severity: normal

Dear Maintainer,

Recently I noticed that syslog is flooded with these kind of messages:

Aug  6 16:43:26 siika kernel: [  657.856294] ehci_hcd :00:12.2: PME#
enabled
Aug  6 16:43:26 siika kernel: [  658.324244] ehci_hcd :00:12.2: BAR 0: set
to [mem 0xf034c000-0xf034c0ff] (PCI address [0xf034c000-0xf034c0ff])
Aug  6 16:43:26 siika kernel: [  658.324357] ehci_hcd :00:12.2: restoring
config space at offset 0x1 (was 0x2b0, writing 0x2b00013)
Aug  6 16:43:26 siika kernel: [  658.324419] ehci_hcd :00:12.2: PME#
disabled
Aug  6 16:43:26 siika kernel: [  658.324445] ehci_hcd :00:12.2: PCI INT B
- GSI 17 (level, low) - IRQ 17
Aug  6 16:43:26 siika kernel: [  658.368211] ehci_hcd :00:13.2: BAR 0: set
to [mem 0xf034a000-0xf034a0ff] (PCI address [0xf034a000-0xf034a0ff])
Aug  6 16:43:26 siika kernel: [  658.368347] ehci_hcd :00:13.2: restoring
config space at offset 0x1 (was 0x2b0, writing 0x2b00013)
Aug  6 16:43:26 siika kernel: [  658.368413] ehci_hcd :00:13.2: PME#
disabled
Aug  6 16:43:26 siika kernel: [  658.368440] ehci_hcd :00:13.2: PCI INT B
- GSI 17 (level, low) - IRQ 17
Aug  6 16:43:26 siika kernel: [  658.396646] ohci_hcd :00:12.0: PCI INT A
- GSI 18 (level, low) - IRQ 18
Aug  6 16:43:27 siika kernel: [  658.528792] ohci_hcd :00:13.0: PCI INT A
- GSI 18 (level, low) - IRQ 18
Aug  6 16:43:29 siika kernel: [  660.809470] ohci_hcd :00:12.0: PCI INT A
disabled
Aug  6 16:43:29 siika kernel: [  660.824144] ehci_hcd :00:13.2: PCI INT B
disabled
Aug  6 16:43:29 siika kernel: [  660.824222] ehci_hcd :00:13.2: PME#
enabled
Aug  6 16:43:29 siika kernel: [  660.825707] ohci_hcd :00:13.0: PCI INT A
disabled
Aug  6 16:43:31 siika kernel: [  662.856405] ehci_hcd :00:12.2: PCI INT B
disabled

I have not noticed that something would not work, but the messages are
annoying.

I don't remember seeing them when I started using wheezy in April.



-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 
root=UUID=0c009ddc-ed8b-4e55-a799-0cf38e3174a4 ro

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[  813.809296] ohci_hcd :00:13.0: PCI INT A disabled
[  813.824258] ehci_hcd :00:13.2: PCI INT B disabled
[  813.824277] ohci_hcd :00:12.0: PCI INT A disabled
[  813.824513] ehci_hcd :00:13.2: PME# enabled
[  815.840121] ehci_hcd :00:12.2: PCI INT B disabled
[  815.840178] ehci_hcd :00:12.2: PME# enabled
[  816.552119] ehci_hcd :00:12.2: BAR 0: set to [mem 0xf034c000-0xf034c0ff] 
(PCI address [0xf034c000-0xf034c0ff])
[  816.552171] ehci_hcd :00:12.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[  816.552221] ehci_hcd :00:12.2: PME# disabled
[  816.552240] ehci_hcd :00:12.2: PCI INT B - GSI 17 (level, low) - IRQ 17
[  816.596144] ehci_hcd :00:13.2: BAR 0: set to [mem 0xf034a000-0xf034a0ff] 
(PCI address [0xf034a000-0xf034a0ff])
[  816.596197] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[  816.596244] ehci_hcd :00:13.2: PME# disabled
[  816.596264] ehci_hcd :00:13.2: PCI INT B - GSI 17 (level, low) - IRQ 17
[  816.624407] ohci_hcd :00:12.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[  816.760469] ohci_hcd :00:13.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[  818.825090] ohci_hcd :00:12.0: PCI INT A disabled
[  818.840193] ehci_hcd :00:13.2: PCI INT B disabled
[  818.840263] ehci_hcd :00:13.2: PME# enabled
[  818.864301] ohci_hcd :00:13.0: PCI INT A disabled
[  821.024084] ehci_hcd :00:12.2: PCI INT B disabled
[  821.024145] ehci_hcd :00:12.2: PME# enabled
[  822.012216] ehci_hcd :00:12.2: BAR 0: set to [mem 0xf034c000-0xf034c0ff] 
(PCI address [0xf034c000-0xf034c0ff])
[  822.012350] ehci_hcd :00:12.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[  822.012415] ehci_hcd :00:12.2: PME# disabled
[  822.012441] ehci_hcd :00:12.2: PCI INT B - GSI 17 (level, low) - IRQ 17
[  822.056297] ehci_hcd :00:13.2: BAR 0: set to [mem 0xf034a000-0xf034a0ff] 
(PCI address [0xf034a000-0xf034a0ff])
[  822.056432] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[  822.056495] ehci_hcd :00:13.2: PME# disabled
[  822.056522] ehci_hcd :00:13.2: PCI INT B - GSI 17 (level, low) - IRQ 17
[  822.084591] ohci_hcd :00:12.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[  822.216637] ohci_hcd :00:13.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[  824.825365] ohci_hcd :00:12.0: PCI INT A disabled
[  824.825464] ohci_hcd :00:13.0: PCI INT A disabled
[  824.840255] ehci_hcd :00:13.2: PCI INT B disabled
[  

Bug#684049: linux-image-3.2.0-3-amd64: syslog flooded with [e|o]hci_hcd related messages

2012-08-06 Thread Ben Hutchings
On Mon, 2012-08-06 at 16:55 +0300, Juha Heinanen wrote:
 Package: src:linux
 Version: 3.2.21-3
 Severity: normal
 
 Dear Maintainer,
 
 Recently I noticed that syslog is flooded with these kind of messages:
[...]

This is probably the result of run-time power management.  It seems very
eager to turn off the USB ports, but I don't think that's actually a
problem.

I do recognise that syslog should not be filled up with this noise,
though.  Can you test whether the attached patch fixes this for you?
Instructions for building a patched kernel package are at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.1.

Ben.

-- 
Ben Hutchings
Theory and practice are closer in theory than in practice.
- John Levine, moderator of comp.compilers
From: Vincent Palatin vpala...@chromium.org
Date: Mon, 5 Dec 2011 11:51:18 -0800
Subject: PCI/PM/Runtime: make PCI traces quieter

commit 85b8582d7ca516030efb84d94fa29a73c1d9a125 upstream.

When the runtime PM is activated on PCI, if a device switches state
frequently (e.g. an EHCI controller with autosuspending USB devices
connected) the PCI configuration traces might be very verbose in the
kernel log.  Let's guard those traces with DEBUG condition.

Acked-by: Rafael J. Wysocki r...@sisk.pl
Signed-off-by: Vincent Palatin vpala...@chromium.org
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
---
 drivers/acpi/pci_irq.c  |   10 +-
 drivers/pci/pci.c   |5 ++---
 drivers/pci/setup-res.c |6 +++---
 3 files changed, 10 insertions(+), 11 deletions(-)

diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
index 7f9eba9..0eefa12 100644
--- a/drivers/acpi/pci_irq.c
+++ b/drivers/acpi/pci_irq.c
@@ -487,10 +487,10 @@ int acpi_pci_irq_enable(struct pci_dev *dev)
 	else
 		link_desc[0] = '\0';
 
-	dev_info(dev-dev, PCI INT %c%s - GSI %u (%s, %s) - IRQ %d\n,
-		 pin_name(pin), link_desc, gsi,
-		 (triggering == ACPI_LEVEL_SENSITIVE) ? level : edge,
-		 (polarity == ACPI_ACTIVE_LOW) ? low : high, dev-irq);
+	dev_dbg(dev-dev, PCI INT %c%s - GSI %u (%s, %s) - IRQ %d\n,
+		pin_name(pin), link_desc, gsi,
+		(triggering == ACPI_LEVEL_SENSITIVE) ? level : edge,
+		(polarity == ACPI_ACTIVE_LOW) ? low : high, dev-irq);
 
 	return 0;
 }
@@ -524,6 +524,6 @@ void acpi_pci_irq_disable(struct pci_dev *dev)
 	 * (e.g. PCI_UNDEFINED_IRQ).
 	 */
 
-	dev_info(dev-dev, PCI INT %c disabled\n, pin_name(pin));
+	dev_dbg(dev-dev, PCI INT %c disabled\n, pin_name(pin));
 	acpi_unregister_gsi(gsi);
 }
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 5c5adef..54343aa 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -973,7 +973,7 @@ void pci_restore_state(struct pci_dev *dev)
 	for (i = 15; i = 0; i--) {
 		pci_read_config_dword(dev, i * 4, val);
 		if (val != dev-saved_config_space[i]) {
-			dev_printk(KERN_DEBUG, dev-dev, restoring config 
+			dev_dbg(dev-dev, restoring config 
 space at offset %#x (was %#x, writing %#x)\n,
 i, val, (int)dev-saved_config_space[i]);
 			pci_write_config_dword(dev,i * 4,
@@ -1542,8 +1542,7 @@ void pci_pme_active(struct pci_dev *dev, bool enable)
 	}
 
 out:
-	dev_printk(KERN_DEBUG, dev-dev, PME# %s\n,
-			enable ? enabled : disabled);
+	dev_dbg(dev-dev, PME# %s\n, enable ? enabled : disabled);
 }
 
 /**
diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c
index 5717509b..b66bfdb 100644
--- a/drivers/pci/setup-res.c
+++ b/drivers/pci/setup-res.c
@@ -85,9 +85,9 @@ void pci_update_resource(struct pci_dev *dev, int resno)
 		}
 	}
 	res-flags = ~IORESOURCE_UNSET;
-	dev_info(dev-dev, BAR %d: set to %pR (PCI address [%#llx-%#llx])\n,
-		 resno, res, (unsigned long long)region.start,
-		 (unsigned long long)region.end);
+	dev_dbg(dev-dev, BAR %d: set to %pR (PCI address [%#llx-%#llx])\n,
+		resno, res, (unsigned long long)region.start,
+		(unsigned long long)region.end);
 }
 
 int pci_claim_resource(struct pci_dev *dev, int resource)


signature.asc
Description: This is a digitally signed message part