From owner-freebsd-usb@FreeBSD.ORG Sun Sep 11 13:47:07 2005 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5E3816A41F for ; Sun, 11 Sep 2005 13:47:07 +0000 (GMT) (envelope-from mathieu-prevot@wanadoo.fr) Received: from smtp8.wanadoo.fr (smtp8.wanadoo.fr [193.252.22.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F48743D45 for ; Sun, 11 Sep 2005 13:47:07 +0000 (GMT) (envelope-from mathieu-prevot@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0803.wanadoo.fr (SMTP Server) with ESMTP id 4C9F91C001AE for ; Sun, 11 Sep 2005 15:47:06 +0200 (CEST) Received: from [192.168.0.2] (APuteaux-154-1-53-35.w81-249.abo.wanadoo.fr [81.249.4.35]) by mwinf0803.wanadoo.fr (SMTP Server) with ESMTP id 9C06D1C0019F; Sun, 11 Sep 2005 15:47:04 +0200 (CEST) X-ME-UUID: 20050911134704639.9C06D1C0019F@mwinf0803.wanadoo.fr In-Reply-To: <200509111215.44213.hselasky@c2i.net> References: <200509062055.51077.hselasky@c2i.net> <66a11137cf88d55ec6a868dedb1c551a@wanadoo.fr> <200509111215.44213.hselasky@c2i.net> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <308cde6e8015c40187894201a781a0cb@wanadoo.fr> Content-Transfer-Encoding: 7bit From: Mathieu PREVOT Date: Sun, 11 Sep 2005 15:47:03 +0200 To: hselasky@c2i.net X-Mailer: Apple Mail (2.622) Cc: freebsd-usb@freebsd.org Subject: Re: kernel panic with pure usb2umass pluged on pure usb1only motherboard port X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 13:47:07 -0000 Hello Hans, I used your code new_ihfc_1_5_5 for the kernel compilation. I obtained several times a kernel panic. I have a fatal trap 12 (6 times, in the order): Stopped at sysctl_ctx_free+0x18: pushl 0(%esi) +0x36: movl 0x4(%eax),%eax xpt_path_comp+0x19: cmpl $-0x1,0x10(%eax) camisr+0xcd: movl 0x14(%eax),%eax +0xb3: movl %eax,0x28(%ecx) +0xcd: movl 0x14(%eax),%eax with trace, I have respectively: 2 times: sysctl_ctx_free() device_sysctl_fini() device_ detach() device_delete_child() usbd_free_device() uhub_explore() usb_discover() usb_event_thread() fork_exit() fork_trampoline() -- trap 0x1, eip=0, esp=0xd5424d7c, ebp=0 -- then 1time: xpt_path_comp() cam_periph_find() cam_periph_alloc() passasync() xpt_async_bcast() xpt_async() probedone camisr() ithread_loop() fork_exit() fork_trampoline() -- trap 0x1, eip=0, esp=0xd41f2d7c, ebp=0 -- and then 3 times: camisr() ithread_loop() fork_exit() fork_trampoline() -- trap 0x1, eip=0, esp=0xd41f2d7c, ebp=0 -- is it really useful in this case to report functions ? Maybe it can be important: the umass is also a mp3player (Zicplay). Regards, MP