public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Pat LaVarre <p.lavarre@ieee.org>, mpm@selenic.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5
Date: Sun, 14 Sep 2003 08:24:24 +0800	[thread overview]
Message-ID: <200309140824.25612.mhf@linuxmail.org> (raw)
In-Reply-To: <1063460312.2905.13.camel@patehci2>


> I ended by running the third variant script quoted below. Now my logs
> comfortingly end with 'switching to X'. I presume I'm catching the
> crash in the last sleep $wait.

Makes sense because the crash may (in your case does) happen later 
in the switching sequence at which time the "new" log already made 
it to disk - I'll use your variant from now on ;)

The qestion now is whether this is kernel or X related.
Have you had this problem with an earlier 2.6 or 2.4 kernel?

If it is specific to -test5, post (as tar.bz2)

- lspci -v  
- /var/log/dmesg
- X version and driver info from /var/log/XFree86.log 
- .config

Regards
Michael


  parent reply	other threads:[~2003-09-14  0:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1063378664.5059.19.camel@patehci2>
2003-09-12 18:19 ` console lost to Ctrl+Alt+F$n in 2.6.0-test5 Pat LaVarre
2003-09-12 23:06   ` Matt Mackall
2003-09-13  0:49     ` Pat LaVarre
2003-09-13  1:57       ` Matt Mackall
2003-09-13 13:38         ` Pat LaVarre
2003-09-13 14:49           ` Michael Frank
2003-09-13 15:47             ` Michael Frank
2003-09-13 23:12               ` Pat LaVarre
2003-09-14  9:32               ` console lost to Ctrl+Alt+F_n " Pavel Machek
2003-09-14  0:24           ` Michael Frank [this message]
2003-09-14 23:04             ` 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n " Pat LaVarre
2003-09-14 19:00 Pat LaVarre

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=200309140824.25612.mhf@linuxmail.org \
    --to=mhf@linuxmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox