From: Jan Yenya Kasprzak <kas@fi.muni.cz>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, osv@javad.com
Subject: Re: [RFC 1/1] Char: mxser_new, fix recursive locking
Date: Sat, 14 Apr 2007 22:20:50 +0200 [thread overview]
Message-ID: <20070414202050.GG20376@fi.muni.cz> (raw)
In-Reply-To: <4af2d03a0704141311q61931b98wb613b4ee4c580b02@mail.gmail.com>
Jiri Slaby wrote:
: On 4/14/07, Jan Yenya Kasprzak <kas@fi.muni.cz> wrote:
: >~BUG: spinlock lockup on CPU#0, sshd/1671, ffffffff80557780
: [...]
: >the write(1, "/file/name/...", ...) call returned -EIO.
:
: Just a question: both with mxser_new, right?
No. One side has a multiport C168H with mxser_new, and the other
one (the one from which the above strace is) is an ordinary server with
console on ttyS0. So the above write(1,...) has fd#1 on ttyS0.
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ |
> I will never go to meetings again because I think face to face meetings <
> are the biggest waste of time you can ever have. --Linus Torvalds <
next prev parent reply other threads:[~2007-04-14 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 4:27 MOXA: mxser_new lockup Jan Kasprzak
2007-04-14 6:51 ` Jiri Slaby
2007-04-14 10:25 ` Jan Kasprzak
2007-04-14 12:43 ` [RFC 1/1] Char: mxser_new, fix recursive locking, " Jiri Slaby
2007-04-14 14:37 ` [RFC 1/1] Char: mxser_new, fix recursive locking Jan Yenya Kasprzak
2007-04-14 16:52 ` Jiri Slaby
2007-04-14 19:55 ` Jan Yenya Kasprzak
2007-04-14 20:11 ` Jiri Slaby
2007-04-14 20:20 ` Jan Yenya Kasprzak [this message]
2007-04-14 20:23 ` Jiri Slaby
2007-04-14 20:24 ` Jan Yenya Kasprzak
2007-04-14 22:36 ` Jiri Slaby
2007-04-15 17:45 ` [RFC 1/1] Char: mxser_new, fix TIOCMIWAIT Jiri Slaby
2007-04-20 15:02 ` [RFC 1/1] Char: mxser_new, fix recursive locking Jan Yenya Kasprzak
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=20070414202050.GG20376@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osv@javad.com \
/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®