Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Apr 2002 10:46:11 -0500
From:      Mark Nipper <nipsy@tamu.edu>
To:        freebsd-stable@freebsd.org
Subject:   cdda2wav locked up...
Message-ID:  <20020430154611.GA27686@arrakis.tamu.edu>

next in thread | raw e-mail | index | archive | help

--qDbXVdCdHGoSgWSk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	I realize this is a difficult problem, but I've seen
similarly screwy things under both Linux and now FreeBSD.

	Usually I'd be using cdparanoia, which unfortunately is
not available under FreeBSD.  But I was curious to see how things
would work under FreeBSD with my 40x Plextor burner and cdda2wav.
I have a somewhat scratched CD as the test CD.

	So, I start up cdda2wav with some somewhat arbitrary
flags:
---
> cdda2wav -D /dev/acd0c -c 2 -x -O wav -v 1
cdrom device (/dev/acd0c) is not of type generic SCSI. Setting
interface to cooked_ioctl.
266240 bytes buffer memory requested, 4 buffers, 27 sectors
#Cdda2wav version 1.11a19_freebsd_4.5-stable_i386_i386 real time
sched. soundcard support
CD with illegal leadout position detected!
Restrictions apply, since the size of the last track is unknown!
cdda2wav: Operation not permitted. cannot set posix realtime
scheduling policy
overlap:min/max/cur, jitter, percent_done:
 1/ 1/ 1/      0  78%^C
^C
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Cc

^Z
^C^Z^C^Z^C^Z^C
---

And all of my subsequent attempts to break out have, of course,
failed.

	Looking at ps as root:
---
> ps axfu | grep cdda
nipsy    27569  0.0  0.2  1412 1068  pb  D+   10:32AM   0:00.16 cdda2wav -D=
 /dev/acd0c -c 2 -x -O wav -v 1
nipsy    27570  0.0  0.0     0    0  pb  Z+   10:32AM   0:00.00 (cdda2wav)
---

Both kill and 'kill -9' do nothing.

	Now this doesn't bother me so much since I'll have to
take the machine down soon to upgrade the memory on my Adaptec
2400A and increase the NMBCLUSTERS value in the kernel.

	But I'm curious, is this causing problems being hung like
this?  It's not really eating any CPU time and I don't need the
drive right this second.  It just seems like there should be a
way to avoid this lockup in the kernel...

--=20
Mark Nipper                                                e-contacts:
Computing and Information Services                      nipsy@tamu.edu
Texas A&M University                    http://arrakis.tamu.edu/nipsy/
College Station, TX 77843-3142           AIM: texasnipsy ICQ: 66971617
(979)575-3193                                        Yahoo: texasnipsy

-----BEGIN GEEK CODE BLOCK-----
GG/IT d- s++:+ a-- C++$ UBL+++$ P--->+++ L+++$ E---
W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+
PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------

---begin random quote of the moment---
And if I close my mind in fear, please pry it open.
----end random quote of the moment----

--qDbXVdCdHGoSgWSk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjzOvEMACgkQ79RuBNw99zAWXwCgk2hhw/7c/DYIi9qutJT0sDlY
wBUAnjyG11GjfFm52eTghO1frpwfi1PR
=e765
-----END PGP SIGNATURE-----

--qDbXVdCdHGoSgWSk--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020430154611.GA27686>