mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pat LaVarre <p_lavarre@yahoo.com>
To: mhf@linuxmail.org
Cc: mpm@selenic.com, p.lavarre@ieee.org, linux-kernel@vger.kernel.org
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: Sun, 14 Sep 2003 12:00:15 -0700 (PDT)	[thread overview]
Message-ID: <20030914190015.49006.qmail@web21106.mail.yahoo.com> (raw)


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

Definitely not specific to 2.6.0-test5: I have
repeatedly seen 2.6.0-test4 crash this way too.

Whether I have had this vulnerability for days or
weeks or months or years I am not yet sure, I do not
customarily make a point of trying chvt much with each
new kernel.  

Unless I hear otherwise, hopefully within hours, when
next I manage to visit my console in person:

1) I will test to see if the script can crash:

2.6.0-test4 with my near default .config
2.4.22 with my near default .config
2.4.21-xfs Knoppix booted via cd

2) After the reboot following a crash of 2.6.0-test5 I
will sample:

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

3) I will report back here, attaching (2) as .tar.bz2.

Pat LaVarre



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

             reply	other threads:[~2003-09-14 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-14 19:00 Pat LaVarre [this message]
     [not found] <1063378664.5059.19.camel@patehci2>
2003-09-13  1:57 ` Matt Mackall
2003-09-13 13:38   ` Pat LaVarre
2003-09-14  0:24     ` 2.6.0-test5: intermittent crash on chvt to X; was " Michael Frank
2003-09-14 23:04       ` 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=20030914190015.49006.qmail@web21106.mail.yahoo.com \
    --to=p_lavarre@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.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

all inboxes | Powered by JetHome®