From: Julien BLACHE <jblache@debian.org>
To: Kumba <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] IP22: fix serial console hangs
Date: Sun, 09 Jul 2006 20:37:21 +0200 [thread overview]
Message-ID: <877j2mmxpa.fsf@frigate.technologeek.org> (raw)
In-Reply-To: <44B13F02.5020002@gentoo.org> (kumba@gentoo.org's message of "Sun, 09 Jul 2006 13:38:10 -0400")
Kumba <kumba@gentoo.org> wrote:
Hi,
> Out of curiosity, don't suppose you've seen the oops on IP22 that can
> sometimes be triggered by closing the serial client on another box?
Haven't seen this one, no. I'm using a hardware console on the serial
line most of the time (though I still haven't found the proper
configuration and it's hardly usable for anything advanced making use
of terminal features).
> Haven't investigated it too much, but I've seen the odd case on Indy
> and IP28 (which also uses the zilog driver) where shutting down my
> serial client or sometimes rebooting the system running the client
> oopses the driver. I suspect some rogue data gets passed that zilog
> doesn't know how to handle properly.
It looks a bit like the serial driver crash on reboot which Martin
Michlmayr fixed a couple of months back by backporting fixes from the
sunzilog driver. But I think this one made its way into the kernel, so
it must be something else.
JB.
--
Julien BLACHE <jblache@debian.org> | Debian, because code matters more
Debian & GNU/Linux Developer | <http://www.debian.org>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
next prev parent reply other threads:[~2006-07-09 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 13:51 [PATCH] IP22: fix serial console hangs Julien BLACHE
2006-07-09 17:38 ` Kumba
2006-07-09 18:37 ` Julien BLACHE [this message]
2006-07-09 17:58 ` Martin Michlmayr
2006-07-09 18:40 ` 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=877j2mmxpa.fsf@frigate.technologeek.org \
--to=jblache@debian.org \
--cc=kumba@gentoo.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