[lkml]   [2003]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PROBLEM: 2.4.21 crashes hard running cdrecord in X.
On Mon, 16 Jun 2003 10:22, Per Nystrom wrote:
> 2.4.21 crashes hard running cdrecord in X.
> I just compiled installed 2.4.21, and when I try to burn a cd in X,
> everything locks up hard. I've enabled kernel debugging and set up a
> serial console to try to capture anything I can, but I don't even get a
> panic or an oops message. The following line is the last dying gasp
> from syslogd:
> Jun 15 16:21:54 spike kernel: scsi : aborting command due to timeout :
> pid 569,
> scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00
> After that, everything is locked up hard. Even the SysRq keys won't
> work. The command I was running that particular time was
> cdrecord dev=0,0,0 blank=fast
> This only seems to happen when I'm running in X. I can use cdrecord to
> burn cds all day when X is not running. I haven't gotten any
> finer-grained with it than that; I don't know if it's X itself, the
> window manager, the desktop, nvidia's drivers, or any other bits that

Could you please try without the nvidia drivers. You will get no support here
with them running. There is no way of knowing what happens when these are
running. They have our source code, we don't have theirs.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:36    [W:0.040 / U:1.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site