This is something Gerard will probably have to look at. Basically, the driver
is renegotiating the transfer rate with the CD-ROM an inordinately large number
of times, and it is logging those negotiations. Normally, those aren't logged,
so I'm not sure what's up with that. I'll look into the kernel config files to
see if there is anything in there that could be causing this as well. Nothing
in the config files looked like it would cause this to me...time to email
Gerard...

Hi
Tried to burn two cd of wolfverine with the burner attached on my tekram just
seem to work but doing after burning md5sum /dev/cdrom on the CDs give me bad
results.... I will try to install RH7 again and make a new try to see if it
works better with kernel 2.2...
PS : My Burner is a TEAC CD 58s
Regards
JYL

I've got confirmation that the problem with the log files was simply that a
debug flag was turned on in the driver. The reason for renegotiating every two
seconds is likely magicdev or some other program checking the CD-ROM to see if
it has a CD in it every two seconds, and the check resulting in a
CHECK_CONDITION return from the CD-ROM, which signals a need to renegotiate
speed settings in the driver. This has been resolved by the latest sym/ncr
driver pair which is currently undergoing final QA at Symbios and then will be
released via Gerard to the mainstream linux kernel. Hence, it will be resolved
shortly. Since the driver maintainer is taking care of this (and since I
checked our internal tree and I can't see where the debug flag is still being
set), I'm closing this as wontfix and waiting for the driver update to come
through. In the meantime, you can load your sym53c8xx module with the option
sym53c8xx=debug:0 to disable the debug messages.