All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:57:47 -0500	[thread overview]
Message-ID: <20030913015747.GC4489@waste.org> (raw)
In-Reply-To: <1063414148.2892.26.camel@patehci2>

On Fri, Sep 12, 2003 at 06:49:08PM -0600, Pat LaVarre wrote:
> 
> > 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.
> 
> Yes, thank you, Ctrl+Alt+F$n now works if only I
> CONFIG_DEBUG_SPINLOCK_SLEEP=n.
> 
> Also `sudo cat /proc/kmsg | tee ...` also suddenly starts working.
> 
> I wonder if somehow /proc/kmsg now working is a clue?  Back with =y, my
> `dmesg` was clean but via /proc/kmsg I was seeing garbage like
> 
> mmae t itbl
> 
> or:
> 
> mmae t itle

What video are you using? I'm guessing you've got a framebuffer console?
VESA by any chance?

> for what now again is such reassuring chatter as:
> 
> <6>scsi2 : SCSI emulation for USB Mass Storage devices
> <5>  Vendor: Iomega    Model: RRD               Rev: 23.D
> <5>  Type:   CD-ROM                             ANSI SCSI revision: 02
> <7>WARNING: USB Mass Storage data integrity not assured
> <7>USB Mass Storage device found at 3
> <4>sr1: scsi3-mmc drive: 125x/125x caddy
> <4>sr1: scsi3-mmc maybe not writeable
> <4>sr1: scsi3-mmc writable profile: 0x0002
> <7>Attached scsi CD-ROM sr1 at scsi2, channel 0, id 0, lun 0
> 
> Pat LaVarre
> 
> P.S. I could easily check to see if =y kills an ssh session or just the
> display, if that helps.

That might help track down a bug in the console, sure. Not sure what's
going on with /proc/kmsg though.
 
> P.P.S.
> 
> Tentatively I conclude "sleep debugging ... off" meant this .config
> change because I see:

Yep, that's the one.

-- 
Matt Mackall : http://www.selenic.com : of or relating to the moon

  reply	other threads:[~2003-09-13  1:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 14:57 oops if unplug dd of=/dev/scd$n Pat LaVarre
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 [this message]
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
2003-09-12 19:44 ` oops if unplug dd of=/dev/scd$n 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=20030913015747.GC4489@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 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.