From owner-freebsd-bugs@freebsd.org  Fri Nov 20 13:54:52 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9CA0A33A2F
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 20 Nov 2015 13:54:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8CB011E70
 for <freebsd-bugs@FreeBSD.org>; Fri, 20 Nov 2015 13:54:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAKDsq2D006121
 for <freebsd-bugs@FreeBSD.org>; Fri, 20 Nov 2015 13:54:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 196980] [pci] PCI Resource Allocation Causing 2 em devices to
 fail during initialization
Date: Fri, 20 Nov 2015 13:54:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: peter@ifm.liu.se
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-196980-8-83lPQwHWcX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196980-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-196980-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 13:54:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196980

Peter Eriksson <peter@ifm.liu.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peter@ifm.liu.se

--- Comment #6 from Peter Eriksson <peter@ifm.liu.se> ---
Just a quick comment that this indeed seems to be a problem in 10.2-RELEASE
also.

I tried the MSI-quirks hack described above but it makes no difference.

In my case (also using Sun Fire X4500 - Thumper) the following devices seems to
be affected:

> pcib8: <ACPI PCI-PCI bridge> at device 6.0 on pci4
> pcib8: failed to allocate initial I/O port window: 0xd000-0xdfff

> em2: <Intel(R) PRO/1000 Legacy Network Connection 1.0.6> mem 0xfdbe0000-0xfdbfffff irq 61 at device 1.0 on pci8
> em2: 0x40 bytes of rid 0x20 res 4 failed (0, 0xffffffffffffffff).
> em2: Unable to allocate bus resource: ioport
> em2: Allocation of PCI resources failed
> device_attach: em2 attach returned 6

> em2: <Intel(R) PRO/1000 Legacy Network Connection 1.0.6> mem 0xfdbc0000-0xfdbdffff irq 62 at device 1.1 on pci8
> em2: 0x40 bytes of rid 0x20 res 4 failed (0, 0xffffffffffffffff).
> em2: Unable to allocate bus resource: ioport
> em2: Allocation of PCI resources failed
> device_attach: em2 attach returned 6

> pcib14: <ACPI PCI-PCI bridge> at device 8.0 on pci9
> pcib14: failed to allocate initial I/O port window: 0xf000-0xffff

> ppc0: cannot reserve I/O port range

(the ppc0 is not really a problem though - doubt there even is a parallel
printer port :-)

- Peter

-- 
You are receiving this mail because:
You are the assignee for the bug.