mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Frans Pop <elendil@planet.nl>
Cc: Netdev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
	linux-pm@lists.linux-foundation.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [2.6.30] e1000e: pci_enable_pcie_error_reporting failed 0xfffffffb
Date: Thu, 21 May 2009 22:32:23 +0200	[thread overview]
Message-ID: <200905212232.24232.rjw@sisk.pl> (raw)
In-Reply-To: <200905212200.14375.elendil@planet.nl>

On Thursday 21 May 2009, Frans Pop wrote:
> On Thursday 14 May 2009, Frans Pop wrote:
> > With 2.6.30-rc[45] I'm always seeing this error while resuming from STR
> > on my HP 2510p notebook:
> >
> >   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: wake-up capability disabled by ACPI
> >   e1000e 0000:00:19.0: PME# disabled
> >   e1000e 0000:00:19.0: wake-up capability disabled by ACPI
> >   e1000e 0000:00:19.0: PME# disabled
> >   e1000e 0000:00:19.0: irq 26 for MSI/MSI-X
> >
> > The error only shows up during resume, not during normal boot.
> >
> > With 2.6.29 the error is not present. Is this something that should be
> > looked into? Networking still comes up normally.
> 
> I'm still seeing this with 2.6.30-rc6. Should I just ignore it or is it an
> indication of a problem/regression?

Sorry for the lack of response.

I'm not sure if this is a symptom of a regression.  It looks like the driver
has become more verbose.

Thanks,
Rafael

      reply	other threads:[~2009-05-21 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 11:12 Frans Pop
2009-05-21 20:00 ` Frans Pop
2009-05-21 20:32   ` Rafael J. Wysocki [this message]

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=200905212232.24232.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=elendil@planet.nl \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®