Andrew, Interresting VT/X switching issue which does not happen with 2.4 Regards Michael ---------- Forwarded Message ---------- Subject: Re: 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5 Date: Monday 15 September 2003 07:04 From: Pat LaVarre To: mhf@linuxmail.org Cc: mpm@selenic.com, linux-kernel@vger.kernel.org > qestion now is whether this is kernel or X related. Oh. > > echo ... | tee -a $log > > sync > > sleep $wait > > chvt ... > > sleep $wait > > the crash may (in your case does) happen later In repeating those five commands, is there any purpose to the first sleep? I left the first sleep in place to match the original, but once I assume sync leaves no writes unflushed then now I do not see what the first sleep accomplishes, if anything. > Have you had this problem with an earlier 2.6 or 2.4 kernel? Today 2.4.21-xfs Knoppix booted via cd: in over 75 cycles I saw no crash so I gave up. Today 2.4.22 with a near default .config: "in over 75 cycles I saw no crash so I gave up". Today 2.6.0-test4 with a near default .config: Counting cycles before crash per boot I saw: 3 2 16 ... Yester/today 2.6.0-test5 with a near default .config: "I saw: 1 18 20 20 ... 4 16 ..." 3 ... > -test5, post (as tar.bz2) ... After that last -test5 crash I rebooted and then produced the attached via: #!/bin/bash # rm -r chvtx mkdir chvtx sudo /sbin/lspci -v >>chvtx/v.lspci sudo cat /var/log/dmesg >>chvtx/var.log.dmesg egrep -i 'version|release|driver' /var/log/XFree86.*.log >>chvtx/var.log.XFree86.log # cp -ip /var/log/XFree86.*.log chvtx/ cp -ip .config chvtx/config tar -c chvtx | bzip2 -zc >chvtx.2.6.0-test5.tar.bz2 # Pat LaVarre -------------------------------------------------------