From: Julien BLACHE <jb@jblache.org>
To: linux-mips@linux-mips.org
Subject: (Newport) console problems on IP22
Date: Sun, 22 Feb 2009 21:07:02 +0100 [thread overview]
Message-ID: <873ae6ck2h.fsf@sonic.technologeek.org> (raw)
Hi,
Martin Michlmayr offered a build of 2.6.29-rc5 for test to
debian-mips, and that kernel is showing console-related issues on my
IP22.
I'm not sure what's going, so here are my observations:
- the Newport console is not detected anymore
- getty process stuck
root 1226 98.7 0.0 0 0 tty1 Rs+ 19:48 9:22 [getty]
gettys on tty[2-6] might also be stuck somewhere. Can't strace the
getty on tty1 (operation not permitted) and strace on tty[2-6]
attaches to the process but doesn't print anything and is stuck from
here on. Cannot detach or anything. Processes are of course
unkillable.
- dmesg fills up with
tty_release_dev: tty1: read/write wait queue active!
No keyboard/screen attached, serial console only.
Does that ring any bell wrt recent tty changes? Any idea?
JB.
--
Julien BLACHE <http://www.jblache.org>
<jb@jblache.org> GPG KeyID 0xF5D65169
next reply other threads:[~2009-02-22 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 20:07 Julien BLACHE [this message]
2009-02-22 20:11 ` (Newport) console problems on IP22 Julien BLACHE
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=873ae6ck2h.fsf@sonic.technologeek.org \
--to=jb@jblache.org \
--cc=linux-mips@linux-mips.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