Date: Tue, 27 Apr 2010 19:36:17 +0200
From: Johannes Stezenbach <js@sig21.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fat: excessive log spamming due to corrupted fs
Message-ID: <20100427173617.GA712@sig21.net>
References: <20100422155944.GA22181@sig21.net>
 <87633d2pm3.fsf@devron.myhome.or.jp>
 <20100427101423.GA30678@sig21.net>
 <87wrvt16p7.fsf@devron.myhome.or.jp>
 <874oiw26hd.fsf@devron.myhome.or.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <874oiw26hd.fsf@devron.myhome.or.jp>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 924
Lines: 21

On Wed, Apr 28, 2010 at 01:41:18AM +0900, OGAWA Hirofumi wrote:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
> 
> >> comment about KERN_CONT in kernel.h.  But maybe it only happens
> >> for /var/log/kern.log and my xconsole when generating too much
> >> output too quickly, "dmesg -s 10000000 | less" did not show
> >> the corruption (but only shows ~2700 lines out of the ~10000).
> 
> Um, please check syslog at same time with dmesg. If there is corruption
> in syslog, but there is not in dmesg. It sounds like userland problem.

I guess klogd cannot handle that much output.  If you'd add some
rate limiting that might fix the log corruption, too.

Thanks
Johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/