From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 29 20:00:44 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6800516A4D1 for ; Wed, 29 Sep 2004 20:00:44 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5994943D46 for ; Wed, 29 Sep 2004 20:00:44 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8TK0iJ7003365 for ; Wed, 29 Sep 2004 20:00:44 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8TK0ivJ003364; Wed, 29 Sep 2004 20:00:44 GMT (envelope-from gnats) Date: Wed, 29 Sep 2004 20:00:44 GMT Message-Id: <200409292000.i8TK0ivJ003364@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Lodewijk Voge Subject: Re: kern/46551: cbb driver hangs on Sony Vaio X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Lodewijk Voge List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 20:00:44 -0000 The following reply was made to PR kern/46551; it has been noted by GNATS. From: Lodewijk Voge To: Tilman Linneweh Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/46551: cbb driver hangs on Sony Vaio Date: Wed, 29 Sep 2004 21:16:06 +0200 On 27-aug-04, at 15:10, Tilman Linneweh wrote: > Synopsis: cbb driver hangs on Sony Vaio > > State-Changed-From-To: open->feedback > State-Changed-By: arved > State-Changed-When: Fri Aug 27 13:08:58 GMT 2004 > State-Changed-Why: > We need more information: > - Are you using ACPI? > - boot -v output > > http://www.freebsd.org/cgi/query-pr.cgi?pr=46551 I don't have regular access to the machine anymore, but I tried to boot 5.3-BETA6 on it today and it booted fine. the problem seems to have gone away, so unless it is still interesting why early 5.x had this problem, this can be closed. thanks, Lodewijk