From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 7 16:20:07 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10D7116A4CE for ; Thu, 7 Oct 2004 16:20:07 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 376D643D55 for ; Thu, 7 Oct 2004 16:20:06 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i97GH4Au088411 for hackers@freebsd.org.checked; (8.12.8/vak/2.1) Thu, 7 Oct 2004 20:17:04 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i97GE2KG088289; (8.12.8/vak/2.1) Thu, 7 Oct 2004 20:14:02 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <41656BF8.1000703@cronyx.ru> Date: Thu, 07 Oct 2004 20:16:56 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <41645625.3020209@cronyx.ru> <4164E3A9.2050209@DeepCore.dk> In-Reply-To: <4164E3A9.2050209@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: hackers@freebsd.org Subject: Re: Printing from kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 16:20:07 -0000 Søren Schmidt wrote: > Roman Kurakin wrote: > >> Hi, >> >> I have some problems with printing from kernel. >> At first I think that my problems was cause I use printf, >> but changed all of them to log cause it safe to use from >> interrupt handlers. The situation become better but I still >> observe system lockup in case I output some debug information >> from my driver. > > Yes its a known problem, if you output "enough" from the kernel the > console will eventually lockup, its been so for ages, and I dont think > anyone really have been looking into it. I didn't saw it before, only now after moving from Giant, but probably some system changes affect this. Hm. may be I need to try some old versions to check for this. I'll try to dig this. This was the only eye in kernel I use for ages. rik