From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 13 20:19:26 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D9D76D0 for ; Mon, 13 Jan 2014 20:19:26 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 761DF1361 for ; Mon, 13 Jan 2014 20:19:26 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 54ED8B9B9; Mon, 13 Jan 2014 15:19:25 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Atom Board ACPI API MOPNV10J failing since 9.1 Date: Mon, 13 Jan 2014 14:28:47 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <52CF850A.9060906@erdgeist.org> In-Reply-To: <52CF850A.9060906@erdgeist.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201401131428.47517.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 13 Jan 2014 15:19:25 -0500 (EST) Cc: Dirk Engling X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 20:19:26 -0000 On Friday, January 10, 2014 12:28:42 am Dirk Engling wrote: > Dear fellow hackers, > > after upgrade my atom board to use the newer zfs features, I could not > use my network cards anymore, neither the builtin realtek, nor my intel > e1000 card. > > You can see it in the http://erdgeist.org/MOPNV10J/dmesg (here one from > FreeBSD-10.0-RC5, but 9.1 and 9.2 behave the same) > > re0: PHY read failed > re0: attaching PHYs failed > ... > em0: port > 0x1000-0x103f irq 21 at device 0.0 on pci5 > em0: Setup of Shared code failed > device_attach: em0 attach returned 6 > > Searching the forums and mailing lists I found this might be related to > the new pcib code and indeed I found in every dmesg since 9.1: > > pcib1: at device 28.0 on pci0 > pcib1: failed to allocate initial prefetch window: 0xe0000000-0xe00fffff This is because it tries to allocate the same space used for AGP. It would really be helpful if you could provide a verbose dmesg when it fails and a verbose dmesg from a working kernel. pciconf -lb output from a working system would be useful as well. -- John Baldwin