Re: [RFC 1/1] Char: mxser_new, fix recursive locking

From: Jan Yenya Kasprzak
Date: Sat Apr 14 2007 - 16:25:20 EST


Jiri Slaby wrote:
: On 4/14/07, Jan Yenya Kasprzak <kas@xxxxxxxxxx> wrote:
: >Jiri Slaby wrote:
: >: On 4/14/07, Jan Yenya Kasprzak <kas@xxxxxxxxxx> 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.

Yes.

-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 <
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/