Any idea why that happens? It used to work w/o any trouble. The
only thing that changed is that the drive that held the data being burned
was IDE, and now all the drives are scsi. Everything seems fine on the
bus.  No errors from debugging information. The system is an amd
2000 xp w/ 256 MB DDR 2700. Can anyone think of any other ways troubleshoot this.
scsi bus seems fine, mutliple kernels have the problem, v 1.1 and 2.0 of
cdrecord have the problem. And it used to work great. I suppose I can put
an IDE drive back on it, and try writing data from it. The hard drives are
68pin lvd and the burned is 50 pin scsi on an adaptec 2940u2w

Casey

On Mon, 13 Jan 2003, Joerg Schilling wrote:

> >From: Casey Scott <[EMAIL PROTECTED]>
>
> >        I previously wrote in about a problem with cdrecord freezing my
> >system with a particular kernel. The problem has been narrowed down more,
> >and exists in any kernel I build. The system is all scsi, and the writer
> >is a Yamaha 4416S. While watching top, noticed a child process of cdrecord
> >running with -99 priority!  Is that even possible, or is it a sign of
> >something wrong. cdrecord is version 1.1, but version 2.0 did the same
> >thing. kernels from both the 2.4 & 2.5 series have exactly the same
> >problem. The system becomes almost totally unresponsive. I have already
> >replace the scsi ribbon, and triple checked termination and adapter
> >settings. Any advice please!
>
> Your claim is partially right: cdrecord runs at a very high priority.
> This is by intention and _definitely_ does not hang a non-broken OS.
>
> Your problem is that the Linux "ps" command does not support the Linux kernel.
> Cdrecord runs at much much higher priority then ps shows up.
>
>
>
> J�rg
>
>  EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
>        [EMAIL PROTECTED]             (uni)  If you don't have iso-8859-1
>        [EMAIL PROTECTED]         (work) chars I am J"org Schilling
>  URL:  http://www.fokus.fhg.de/usr/schilling   ftp://ftp.berlios.de/pub/schily
>


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to