linux-kernel - Re: [2.6.30] e1000e: pci_enable_pcie_error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200905212232.24232.rjw@sisk.pl>
Date:	Thu, 21 May 2009 22:32:23 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	Netdev <netdev@...r.kernel.org>, linux-kernel@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net,
	linux-pm@...ts.linux-foundation.org,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	Linux PCI <linux-pci@...r.kernel.org>
Subject: Re: [2.6.30] e1000e: pci_enable_pcie_error_reporting failed 0xfffffffb

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
--
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/