Comment 4 for bug 28210

The bug report looks like it has been done against a cdrecord version from 2004.
No real cdrecord output has been attached, do it cannot be even called a confirmed bug.

Please test again with the new original cdrecord package from gutsy/multiverse

If the problem goes away, this was a problem that has been fixed in cdrecord..

If the problem goes away with cdrecord ts=30k, this is a Linux kernel bug as noted before.
If there is no report within some time from a recent cdrecord, I propose to close this bug