From: Matt Mackall <mpm@selenic.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: console lost to Ctrl+Alt+F$n in 2.6.0-test5
Date: Fri, 12 Sep 2003 18:06:37 -0500 [thread overview]
Message-ID: <20030912230637.GB4489@waste.org> (raw)
In-Reply-To: <1063390768.2898.15.camel@patehci2>
On Fri, Sep 12, 2003 at 12:19:28PM -0600, Pat LaVarre wrote:
>
> > ... always ... an oops ... Must be fixed.
>
> Once upon a time Ctrl+Alt+F1 gave me a plain text console, Ctrl+Alt+F7
> returned me to me X Windows console.
>
> Much has changed, the last thing I changed was upgrading to 2.6.0-test5
> from 2.6.0-test4, and now I find that toggling back and forth a few
> times leaves my display permanently dark. Recovered from my ext3
> journal are the following two examples of `cat /proc/kmsg | tee ...`
> output.
>
> This report differs slightly, e.g. by severity, repeatability, and
> mention of handle_vm86_fault, from much of:
> http://groups.google.com/groups?q=__might_sleep&scoring=d
>
> Example #1:
>
> ...
> <4>sr0: scsi3-mmc drive: 0x/48x writer cd/rw xa/form2 cdda tray
> <4>sr0: scsi3-mmc maybe not writeable
> <6>Uniform CD-ROM driver Revision: 3.12
> <7>Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
> <4>sr1: scsi3-mmc writable profile: 0x0002
> <7>Attached scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 0
> <3>Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
> <4>Call Trace:
> <4> [<c0121f16>] __might_sleep+0x5f/0x72
> <4> [<c010e76a>] save_v86_state+0x6a/0x20f
> <4> [<c010f32d>] handle_vm86_fault+0xa7/0x8fb
> <4> [<c010cc8f>] do_general_protection+0x0/0x93
> <4> [<c010bf49>] error_code+0x2d/0x38
> <4> [<c010b4bf>] syscall_call+0x7/0xb
> <4>
>
> Example #2:
>
> ...
> <3>Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
> <4>Call Trace:
> <4> [<c0121f16>] __might_sleep+0x5f/0x72
> <4> [<c010e76a>] save_v86_state+0x6a/0x20f
> <4> [<c010f32d>] handle_vm86_fault+0xa7/0x8fb
> <4> [<c02323aa>] ipi_handler+0x0/0x7
> <4> [<c010cc8f>] do_general_protection+0x0/0x93
> <4> [<c010bf49>] error_code+0x2d/0x38
> <4> [<c010b4bf>] syscall_call+0x7/0xb
> <4>
> ...
>
> Pat LaVarre
I'm working on this, it's rather messy. Your lockup might be caused by
printk spew during console switch, see if it still locks up with the
sleep debugging turned off.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-09-12 23:06 UTC|newest]
Thread overview: 11+ 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 [this message]
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 ` 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n " 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=20030912230637.GB4489@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--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