From owner-freebsd-current@FreeBSD.ORG Wed May 16 18:20:01 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE09116A407 for ; Wed, 16 May 2007 18:20:01 +0000 (UTC) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.freebsd.org (Postfix) with ESMTP id 729E113C46E for ; Wed, 16 May 2007 18:20:01 +0000 (UTC) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net by neerbosch.nijmegen.internl.net via neerbosch.nijmegen.internl.net [217.149.193.38] with ESMTP id l4GI5Q2N000072 (8.13.4/1.4); Wed, 16 May 2007 20:05:26 +0200 (MEST) Received: from localhost by neerbosch.nijmegen.internl.net via mboland@localhost with ESMTP id l4GI5QHs000069 (8.13.4/2.02); Wed, 16 May 2007 20:05:26 +0200 (MEST) X-Authentication-Warning: neerbosch.nijmegen.internl.net: mboland owned process doing -bs Date: Wed, 16 May 2007 20:05:26 +0200 (MEST) From: Michiel Boland To: "S.N.Grigoriev" In-Reply-To: <464B3F00.000002.23382@camay.yandex.ru> Message-ID: References: <464B3F00.000002.23382@camay.yandex.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Crash during sending print jobs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2007 18:20:02 -0000 > Hi, > > beginning with last week my 7-Current amd64 system panics > during sending print jobs (especially PostScript) to my > LPT connected laser printer. I was having a similar problam. Although for me, the panic was not induced by the print per se. Rather it was the lprm I did when I tried to remove the job. I believe the panic message was something like 'System call write returning with 1 locks held'. Unfortunately I binned the crash dumps. Cheers Michiel