Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jan 2015 20:58:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 196980] PCI Resource Allocation Causing 2 em devices to fail during initialization
Message-ID:  <bug-196980-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196980

            Bug ID: 196980
           Summary: PCI Resource Allocation Causing 2 em devices to fail
                    during initialization
           Product: Base System
           Version: 10.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: RonDzierwa@comcast.net

Created attachment 151991
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151991&action=edit
dmesg log

I am using FreeBSD on a rack of Sun X4500 to serve up ZFS space.  Each has 4
gigabit ethernet ports, but only 2 are working due to a PCI resource allocation
failure.  This seems similar to another bug (196501) that has been marked as
resolved.  I've tried 'hint.agp.0.disabled=1' as described in the bug report,
but no difference.  I also saw a recommendation about hw.pci.realloc_bars=1,
but it also made no difference. 
I am also using several Sun X4600 compute servers.  these have a similar
complement of em ports and all 4 of them work with the same kernel.  The X4500
supports 48 sata/sas disk drives, so it has quite a few sata controllers on the
bus.  I suspect that they are taking up enough space to make the allocations
for the extra em devices fail, but that's just my humble guess. 

I've attached my dmesg output.

thanks for any help or suggestions.

ron.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196980-8>