From owner-freebsd-current@FreeBSD.ORG Fri Oct 21 21:05:15 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 819441065670 for ; Fri, 21 Oct 2011 21:05:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 57DDD8FC0C for ; Fri, 21 Oct 2011 21:05:15 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1110C46B37; Fri, 21 Oct 2011 17:05:15 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A3AAC8A02E; Fri, 21 Oct 2011 17:05:14 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 21 Oct 2011 16:37:34 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110211637.34240.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 21 Oct 2011 17:05:14 -0400 (EDT) Cc: "Bjoern A. Zeeb" Subject: Re: orm0/ISA strangeness on HEAD preventing drivers from probe/attach? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2011 21:05:15 -0000 On Thursday, October 20, 2011 7:01:42 pm Bjoern A. Zeeb wrote: > Hi, > > I am seeing some strangeness on booting a recent HEAD on an atom machine; the entire orm0 and related stuff looks wrong. Also some things like a watchdog driver etc. no longer probe or attach it seems. Anyone an idea? The orm0 stuff is normal after some of the NEW_PCIB changes. The first ting to try for the watchdog not working on an Intel system by failing to allocate its GCS registers is a known issue, but I don't have a workaround for that currently. -- John Baldwin