From owner-freebsd-firewire@FreeBSD.ORG Tue Jun 8 08:58:00 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5075F16A4CE for ; Tue, 8 Jun 2004 08:58:00 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (80-219-172-121.dclient.hispeed.ch [80.219.172.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D2643D4C for ; Tue, 8 Jun 2004 08:57:58 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:50db:ac79:0:250:daff:fe5a:2107]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id i588vp601523 verified NO) for ; Tue, 8 Jun 2004 10:57:55 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id i588vo301522; Tue, 8 Jun 2004 10:57:50 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Tue, 8 Jun 2004 10:57:50 +0200 (CEST) Message-Id: <200406080857.i588vo301522@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Firewire Developers Subject: orb pointer printf() question X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 08:58:00 -0000 [drop the above ipv6-only address that only sometimes works from the recipients and I'll catch up later from the archives, thanks] Moin, moin. A quick question, concerning the following code: if ((sdev->flags & ORB_POINTER_ACTIVE) != 0) { SBP_DEBUG(0) printf("%s: orb pointer active\n", __func__); END_DEBUG sdev->flags |= ORB_POINTER_NEED; return; } This is in the sbp.c code from the time of 4.10, which is what I've used on my machine with a hard drive attached via firewire. It seems to be working just fine, with the only thing being that the above printf() makes it to the kernel messages a few times each minute during disk activity. Is this something for me to concern myself over? What does it mean? If it's harmless, would it be better to change the above SBP_DEBUG to be DEBUG(1) instead of (0) so as not to print at the default level of debugging, or is it better to log it as is? thanks barry bouwsma