From: Michael Frank <mhf@linuxmail.org>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Cc: Pat LaVarre <p.lavarre@ieee.org>, mpm@selenic.com
Subject: Fwd: 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: Mon, 15 Sep 2003 09:15:09 +0800 [thread overview]
Message-ID: <200309150915.11181.mhf@linuxmail.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
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 <p.lavarre@ieee.org>
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
-------------------------------------------------------
[-- Attachment #2: chvtx.2.6.0-test5.tar.bz2 --]
[-- Type: application/x-bzip, Size: 12515 bytes --]
reply other threads:[~2003-09-15 1:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309150915.11181.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=p.lavarre@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.