From owner-freebsd-bugs Mon Dec 10 4:49:32 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 24D9037B41C; Mon, 10 Dec 2001 04:49:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBACjUq17822; Mon, 10 Dec 2001 04:45:30 -0800 (PST) (envelope-from sheldonh) Date: Mon, 10 Dec 2001 04:45:30 -0800 (PST) From: Message-Id: <200112101245.fBACjUq17822@freefall.freebsd.org> To: larse@isi.edu, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/32605: SMBus driver broken Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: SMBus driver broken State-Changed-From-To: open->feedback State-Changed-By: sheldonh State-Changed-When: Mon Dec 10 04:40:52 PST 2001 State-Changed-Why: The smbus(4) driver doesn't have an active maintainer. If you want the problem fixed, you're going to have to try to get a better idea of what the problem is. Try booting the systems that work with boot -v and comparing the attach messages with those on a system that doesn't work (also booted with boot -v). Also, try to provide more detail on the exact hardware in the boxes (both working and not) using pciconf -vl. Note that the -v option was only added to picconf(8) in -STABLE recently. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=32605 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message