From: Frans Pop <elendil@planet.nl>
To: Netdev <netdev@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, Xiaotian Feng <dfeng@redhat.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: e1000e: why does pci_enable_pcie_error_reporting() fail on my hp2510p?
Date: Thu, 20 Aug 2009 17:14:29 +0200 [thread overview]
Message-ID: <200908201714.30638.elendil@planet.nl> (raw)
With the current kernel I suddenly get the following error displayed
during boot:
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
! e1000e 0000:00:19.0: pci_enable_pcie_error_reporting failed 0xfffffffb
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: irq 26 for MSI/MSI-X
This looks to be the consequence of:
commit 68eac4602b9104cdaa6c18b3edd914cececa6a1e
Author: Xiaotian Feng <dfeng@redhat.com>
Date: Fri Aug 14 14:35:52 2009 +0000
e1000e: fix use of pci_enable_pcie_error_reporting
Looking at the change it seems logical that this error, that I previously
only saw during resumes from suppend to RAM, now also shows up during
system boot. So I don't think it can be qualified as a regression, but it
is certainly rather annoying.
Questions:
- is it possible that the error occurs due to a kernel bug, or is this
certain to be due to broken hardware?
- as the error is non-fatal, should it maybe be changed from dev_err
to dev_info, so that at least it does not show up during a boot
with 'quiet'?
- if broken hardware is common, should the kernel complain at all,
or at least maybe show a slightly "friendlier" message?
System: hp2510p (ICH8, Core2 Duo) running x86_64, Debian stable ("Lenny")
00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM
Gigabit Network Connection [8086:1049] (rev 03)
Subsystem: Hewlett-Packard Company Device 30c9
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 26
Region 0: Memory at e0620000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at e0640000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 2060 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 41b1
Kernel driver in use: e1000e
Kernel modules: e1000e
I can provide full dmesg and kernel config if desired.
Cheers,
FJP
next reply other threads:[~2009-08-20 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 15:14 Frans Pop [this message]
2009-08-20 19:25 ` e1000e: why does pci_enable_pcie_error_reporting() fail on my hp2510p? Bjørn Mork
2009-08-20 19:25 ` Bjørn Mork
2009-08-21 2:08 ` Danny Feng
2009-08-21 6:29 ` [PATCH] " Frans Pop
2009-08-21 6:33 ` Danny Feng
2009-08-21 6:48 ` [PATCH,v2] " Frans Pop
2009-08-21 6:52 ` David Miller
2009-08-21 7:01 ` Jeff Kirsher
2009-08-21 7:01 ` Jeff Kirsher
2009-08-21 7:06 ` Jens Rosenboom
2009-08-21 7:39 ` [PATCH,v3] " Frans Pop
2009-09-02 1:18 ` [PATCH,v2] " Jeff Kirsher
2009-09-02 1:18 ` Jeff Kirsher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908201714.30638.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=dfeng@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.