From owner-freebsd-firewire@FreeBSD.ORG Mon May 18 11:06:51 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59478106564A for ; Mon, 18 May 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 453048FC1E for ; Mon, 18 May 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4IB6pGG075630 for ; Mon, 18 May 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4IB6oHl075626 for freebsd-firewire@FreeBSD.org; Mon, 18 May 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 May 2009 11:06:50 GMT Message-Id: <200905181106.n4IB6oHl075626@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 7 problems total. From owner-freebsd-firewire@FreeBSD.ORG Wed May 20 19:04:23 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 393331065677; Wed, 20 May 2009 19:04:23 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from woodbine.london.02.net (woodbine.london.02.net [87.194.255.145]) by mx1.freebsd.org (Postfix) with ESMTP id CCDA08FC18; Wed, 20 May 2009 19:04:22 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from eight.config (93.97.24.219) by woodbine.london.02.net (8.5.016.1) id 49D39EA901FA647F; Wed, 20 May 2009 19:53:12 +0100 Message-ID: <4A14519C.7090205@onetel.com> Date: Wed, 20 May 2009 19:53:16 +0100 From: Chris Whitehouse User-Agent: Thunderbird 2.0.0.21 (X11/20090411) MIME-Version: 1.0 To: freebsd-firewire@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ikob@freebsd.org Subject: [Fwd: run_interrupt_driven_hooks: still waiting... for xpt_config] X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 19:04:23 -0000 Hi, I asked this question on questions@ but didn't get a reply. Since I seem to have narrowed the problem down to the sbp driver I am hoping this might be a good place to ask. [Please could you copy me on any reply as I am not subscribed to this list, thanks] I'm trying to install on a new motherboard ASUS M3N78-EM. While booting from CD I'm getting run_interrupts_driven_hooks: still waiting after 60 seconds for xpt_config This is repeated a few times then installation stops and the machine stops responding. I've tried various versions of FreeBSD, including 6.4R, 7.0R 7.2R and 8.0-CURRENT-200905-i386-disc1.iso, all i386. I've also tried SATA mode and AHCI mode for the SATA controller. I get panicks on 8.0-CURRENT and on 7.2R with a debug kernel. After some trial and error the problem seems to be device sbp in the kernel config file. Comment that out and rebuild kernel and it boots. Here's a backtrace from 7.2R using a GENERIC kernel (with sbp enabled) with debug options added. run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config panic: run_interrupt_driven_config_hooks: waited too long cpuid=0 KDB: enter: panic [thread pid 0 tid 0 ] stopped at kdb_enter_why+0x3a: movl $0,kdb_why db> bt Tracing pid 0 tid 0 td 0xc0cc1b40 kdb_enter_why(c0b87110,c0b87110,c0b89425,c1020d0c,0,...) at kdb_enter_why+0x3a panic(c0b89425,0,c0b893c0,71,ea60,...) at panic+0x136 run_interrupt_driven_config_hooks(0,101ec00,101ec00,101e000,1025000,...) at run_interrupt_driven_config_hooks+0x1b7 mi_startup() at mi_startup+0x96 begin()at begin+0x2c db> Here's a backtrace from 8.0-CURRENT panic: run_interrupt_driven_config_hooks: waited too long cpuid=0 KDB: enter: panic [thread pid 0 tid 100000 ] stopped at kdb_enter+0x3a: movl $0,kdb_why db> bt Tracing pid 0 tid 100000 td 0xc0d88fd0 kdb_enter(c0c3d8cf,c0c3d8cf,c0c3feac,c1820d08,0,...) at kdb_enter+0x3a panic(c0c3feac,0,c0c3fe43,70,ea60,...) at panic+0x136 run_interrupt_driven_config_hooks(0,181ec00,181ec00,181e000,1825000,...) at run_interrupt_driven_config_hooks+0x1c7 mi_startup() at mi_startup+0x96 begin()at begin+0x2c db> My original emails are here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1705690+0+/usr/local/www/db/text/2009/freebsd-questions/20090517.freebsd-questions http://docs.freebsd.org/cgi/getmsg.cgi?fetch=166763+0+current/freebsd-questions Thanks Chris From owner-freebsd-firewire@FreeBSD.ORG Fri May 22 12:35:38 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EA8C1065740 for ; Fri, 22 May 2009 12:35:38 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 4CBC98FC1B for ; Fri, 22 May 2009 12:35:38 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Fri, 22 May 2009 08:14:57 -0400 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::0 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-firewire@FreeBSD.org X-SMFBL: ZnJlZWJzZC1maXJld2lyZUBGcmVlQlNELm9yZw== Message-ID: <4A169891.5080609@comcast.net> Date: Fri, 22 May 2009 08:20:33 -0400 From: Steve Polyack User-Agent: Thunderbird 2.0.0.21 (X11/20090327) MIME-Version: 1.0 To: freebsd-firewire@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: libraw1394 and FreeBSD X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 12:35:38 -0000 Hello, I've seen a few posts in the archives referring to porting libraw1394 to FreeBSD. However, none of these appear to have been successful. I'm considering giving this a shot, but I will likely need some guidance. I have a few questions/points from what I've gathered from past discussions: 1. libraw1394 implements some ISO 1394 read/write/stop/start/etc functions for firewire on linux. It's been said that these are already implemented in the FreeBSD kernel modules which provide firewire access. Is this correct? If so, libraw1394 only needs rewritten enough to provide the freebsd kernel interface in a linux application-familiar sense. 2. What is going on with firewire development in FreeBSD currently? If I attempt to complete this port, am I better off working with 8-CURRENT as opposed to 7.2-RELEASE? I'm aware the USB stack in 8 is totally rewritten; is the same true for the firewire modules? I believe this would be a valuable port for FreeBSD. It would enable us to use a wide range of audio and DV interfaces via firewire and existing linux "drivers" which only depend on libraw1394, opening up possibilities like using FreeBSD for audio and video editing. Thanks, Steve Polyack From owner-freebsd-firewire@FreeBSD.ORG Fri May 22 19:15:29 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52750106568E for ; Fri, 22 May 2009 19:15:29 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4588FC1B for ; Fri, 22 May 2009 19:15:28 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 7731 invoked from network); 22 May 2009 12:15:26 -0700 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.130?) (69.64.235.60) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 May 2009 12:15:26 -0700 From: Sean Bruno To: Steve Polyack In-Reply-To: <4A169891.5080609@comcast.net> References: <4A169891.5080609@comcast.net> Content-Type: text/plain Date: Fri, 22 May 2009 12:15:27 -0700 Message-Id: <1243019727.3373.16.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10) Content-Transfer-Encoding: 7bit Cc: freebsd-firewire@FreeBSD.org Subject: Re: libraw1394 and FreeBSD X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 19:15:29 -0000 On Fri, 2009-05-22 at 08:20 -0400, Steve Polyack wrote: > Hello, > I've seen a few posts in the archives referring to porting libraw1394 > to FreeBSD. However, none of these appear to have been successful. I'm > considering giving this a shot, but I will likely need some guidance. I > have a few questions/points from what I've gathered from past discussions: Excellent. I'm around, but a little swamped right now under other school related things. I hope to have some free time soon though. I've jotted down a few thoughts below. > 1. libraw1394 implements some ISO 1394 read/write/stop/start/etc > functions for firewire on linux. It's been said that these are already > implemented in the FreeBSD kernel modules which provide firewire > access. Is this correct? If so, libraw1394 only needs rewritten enough > to provide the freebsd kernel interface in a linux application-familiar > sense. > Take a look at how fwcontrol interfaces with the driver. Let me know if you would like to see some changes at the interface. > 2. What is going on with firewire development in FreeBSD currently? If > I attempt to complete this port, am I better off working with 8-CURRENT > as opposed to 7.2-RELEASE? I'm aware the USB stack in 8 is totally > rewritten; is the same true for the firewire modules? > Firewire is fairly static right now. I had hoped to start a bit of re-writing before 8.0 is released, but it's going to be cutting it close. I have been enhancing -Current only for the last few months, and I have been kind of ignoring 7 and 6. So the code has diverged a bit. If you can do it, please start with -Current and see what can be done there first. > > I believe this would be a valuable port for FreeBSD. It would enable us > to use a wide range of audio and DV interfaces via firewire and existing > linux "drivers" which only depend on libraw1394, opening up > possibilities like using FreeBSD for audio and video editing. Agreed. Let me know what devices you have access to. Sean