From owner-freebsd-hackers@FreeBSD.ORG  Sat Nov  5 16:42:20 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DC6C11065672
	for <freebsd-hackers@freebsd.org>; Sat,  5 Nov 2011 16:42:20 +0000 (UTC)
	(envelope-from falkman@gamozo.org)
Received: from fireblade.netcore2k.net (fireblade.netcore2k.net [92.48.127.72])
	by mx1.freebsd.org (Postfix) with ESMTP id 695F98FC0A
	for <freebsd-hackers@freebsd.org>; Sat,  5 Nov 2011 16:42:19 +0000 (UTC)
Received: by fireblade.netcore2k.net with ESMTP id pA5GgGHa027661
	for <freebsd-hackers@freebsd.org>; Sat, 5 Nov 2011 16:42:18 GMT
Date: Sat, 5 Nov 2011 12:42:12 -0400
From: Brandon Falk <falkman@gamozo.org>
To: freebsd-hackers@freebsd.org
Message-ID: <20111105164212.GB50362@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: cdparanoia stuck in cbwait
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2011 16:42:20 -0000

Hello,

I was got some read errors when I was reading from my disk, which is
fine. But then cdparanoia starting to no longer respond. Now it's
zombied and sitting in cbwait. `kill -9 <pid>` does not take it down, it
seems like it's stuck in the kernel (?). Is this an issue to look at
cdparanoia for, or to look in the kernel? Perhaps cdparanoia or the
kernel should have some sort of a timeout? Currently it looks like the
only fix is a full reboot.

Regards,
Brandon Falk