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

[Jiri Slaby]

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.

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
-
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/