From owner-freebsd-current@FreeBSD.ORG  Thu Aug 18 12:16:26 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9B75B16A41F
	for <current@freebsd.org>; Thu, 18 Aug 2005 12:16:26 +0000 (GMT)
	(envelope-from huang@gddsn.org.cn)
Received: from gddsn.org.cn (gddsn.org.cn [218.19.164.145])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 738AC43D49
	for <current@freebsd.org>; Thu, 18 Aug 2005 12:16:24 +0000 (GMT)
	(envelope-from huang@gddsn.org.cn)
Received: from [192.168.1.5] (unknown [218.20.228.62])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by gddsn.org.cn (Postfix) with ESMTP id 806FA38CB4D
	for <current@freebsd.org>; Thu, 18 Aug 2005 19:54:37 +0800 (CST)
Message-ID: <430476F7.6030007@gddsn.org.cn>
Date: Thu, 18 Aug 2005 19:54:31 +0800
From: Huang wen hui <huang@gddsn.org.cn>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050812)
X-Accept-Language: zh-cn,zh
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Cc: 
Subject: suspend/resume operation broken with usb mouse
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2005 12:16:26 -0000

hi,
Using today's CURRENT, my TP42P could not resume with usb mouse.
cause "double fault" panic. With internal TrackPoint is OK,
The DDB backtrace message can be found:

http://hwh.gddsn.org.cn:8180/suc50848.jpg

Revert the following commit also help that.

phk         2005-08-17 08:19:53 UTC

  FreeBSD src repository

  Modified files:
    sys/fs/devfs         devfs_vnops.c 
    sys/kern             kern_conf.c 
    sys/sys              conf.h 
  Log:
  Handle device drivers with D_NEEDGIANT in a way which does not
  penalize the 'good' drivers:  Allocate a shadow cdevsw and populate
  it with wrapper functions which grab Giant
  
  Revision  Changes    Path
  1.120     +0 -24     src/sys/fs/devfs/devfs_vnops.c <http://cvsweb.FreeBSD.org//src/sys/fs/devfs/devfs_vnops.c.diff?r1=1.119&r2=1.120>
  1.190     +155 -9    src/sys/kern/kern_conf.c <http://cvsweb.FreeBSD.org//src/sys/kern/kern_conf.c.diff?r1=1.189&r2=1.190>
  1.226     +1 -0      src/sys/sys/conf.h <http://cvsweb.FreeBSD.org//src/sys/sys/conf.h.diff?r1=1.225&r2=1.226>


Thanks,

--hwh