From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Randy.Dunlap" Subject: Re: nfs and printk's Date: Thu, 04 Nov 2004 10:19:01 -0800 Message-ID: <418A7295.8090001@osdl.org> References: <1099535189.27369.4.camel@dent> <1099592258.11255.6.camel@lade.trondhjem.org> <1099592435.5999.6.camel@dent> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Trond Myklebust , Linux Filesystem Development Return-path: Received: from fire.osdl.org ([65.172.181.4]:10216 "EHLO fire-1.osdl.org") by vger.kernel.org with ESMTP id S262358AbUKDSa1 (ORCPT ); Thu, 4 Nov 2004 13:30:27 -0500 To: Shaya Potter In-Reply-To: <1099592435.5999.6.camel@dent> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Shaya Potter wrote: > On Thu, 2004-11-04 at 10:17 -0800, Trond Myklebust wrote: > >>on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter: >> >>>is there any reason why printk's I'm putting in nfs_readdir() don't >>>appear at all (when other's, such as in nfsd) do appear. If it matters, >>>this is a 2.4.23 kernel. Is printk somehow defined out in fs/nfs/ ? >> >>printk() should always work. Just make sure that you are not confusing >>it with "dprintk()". > > > I'm not, but there's something else screwed up with my build. none of > the printk's I'm adding now are doing anything. very weird, probably a > stupid screw up on my part. It could also depend on the log level used in the printk() call. Are you using one (like KERN_DEBUG)? If so, either don't use one (usually Works For Me) or increase the level of logging (Alt-SysRq-9). -- ~Randy