From: "Jiri Slaby" <jirislaby@gmail.com>
To: "Jan Yenya Kasprzak" <kas@fi.muni.cz>
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:23:48 +0200 [thread overview]
Message-ID: <4af2d03a0704141323qc97a822kc71f4f3fc92738b0@mail.gmail.com> (raw)
In-Reply-To: <20070414202050.GG20376@fi.muni.cz>
On 4/14/07, Jan Yenya Kasprzak <kas@fi.muni.cz> wrote:
> 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
I meant both lockup and EIO error -- I guess so from this line.
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2007-04-14 20:23 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
2007-04-14 20:23 ` Jiri Slaby [this message]
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=4af2d03a0704141323qc97a822kc71f4f3fc92738b0@mail.gmail.com \
--to=jirislaby@gmail.com \
--cc=kas@fi.muni.cz \
--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®