linux-kernel - Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAA9_cmcodVC84-fxN__+=A3nvUgVFv8yuuVvT7W7tH=Qa59Dag@mail.gmail.com>
Date:	Mon, 26 Nov 2012 17:11:09 -0800
From:	Dan Williams <dan.j.williams@...il.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Bruno Prémont <bonbons@...ux-vserver.org>,
	Justin Piszcz <jpiszcz@...idpixels.com>,
	support@...ermicro.com, linux-kernel@...r.kernel.org,
	Dan Williams <dan.j.williams@...el.com>,
	"dave.jiang" <dave.jiang@...el.com>
Subject: Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware
 bug question

On Mon, Nov 26, 2012 at 4:56 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> The "channel error register unreachable" message indicates that
> pci_read_config_dword() failed.  The register in question
> (IOAT_PCI_CHANERR_INT_OFFSET) is at 0x180, so possibly we don't have
> PCI config accessors for the extended config space (0x100-0xfff).  A
> complete dmesg log should show that.

Yes, this happens when extended pci configuration space is not
reachable.  Although the need to access this register has been found
to no longer be needed.  So, it appears this patch [1] from Dave
should be modified to just stop touching that register altogether and
then go to -stable.

--
Dan

[1]: http://marc.info/?l=linux-kernel&m=135310841032707&w=2
--
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/