hi:
Know bug, for now use -dao . cdrecord uses tao by default, using tao,
kernel panic occurs
For example, I now use cdrecord -v dev=0,0,0 dao image_to_record
HTH
Regards
John P Verel <jverel@xxxxxxxxxxxxx>@redhat.com con fecha 22/07/2003
03:41:44 p.m.
Por favor, responda a shrike-list@xxxxxxxxxx
Enviado por: shrike-list-admin@xxxxxxxxxx
Destinatarios: Shrike List <shrike-list@xxxxxxxxxx>
CC:
Asunto: cdrecord, kernel panic
It appears that cdrecord-2.0-11.1, upgraded from Rawhide on 7/17,
is causing a kernel panic. I did the upgrade to fix the permissions bug
in the the stock Shrike cdrecord package. I'm running
kernel-2.4.20-18.9, glibc-2.3.2-27.9, both via Redhat up2date. Here are
selected entries from my /var/log/messages:
Jul 17 22:30:50 Verdi kernel: scsi : aborting command due to timeout :
pid 7578, scsi0, channel 0, id 0, lun 0
Read TOC 00 00 00 00 00 00 00 0c 40
Jul 17 22:32:56 Verdi kernel: scsi : aborting command due to timeout :
pid 10125, scsi0, channel 0, id 0, lun
0 Test Unit Ready 00 00 00 00 00
After these, the machine completely locks, with Cap Loc and Scroll Lock
lights blinking. Power off to fix.
I had 1) created an iso using mkisofs, 2) had burned the image and 3)
cdredord was 'fixating' when this occurred.
Does the kernel release of yesterday fix this?
John
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
