linux-kernel - Re: MOXA: mxser

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Apr 2007 08:51:25 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Jan Kasprzak <kas@...muni.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: MOXA: mxser_new lockup

Jan Kasprzak napsal(a):
> 	Hello,

Hello.

> I have a MOXA C168H card, and after the upgrade from 2.6.19 to 2.6.21-rc6
> (and from moxa.c to mxser_new.c) I get a system lockup after few seconds
> of communicating over the MOXA serial line. Noting is printed on the
> serial console at all. The system is SMP x86_64 (Fedora 5). I may be
> able to do a limited testing on request, but the system is in production
> use most of the time. For now, I will probably move back to the older
> driver.
> 
> 	Are you aware of any SMP or 64-bit issues in mxser_new.c?

No :(. I went through the locking again just now, but I can't see anything
wrong. Could you please enable CONFIG_PROVE_LOCKING and CONFIG_DEBUG_LOCKDEP and
retest?

And also post stty -a -F /dev/ttyMIXX or a setup passed to
tcsetattr/ioctl(TCSETA/S) if available. What do you use for communication?

thanks,
-- 
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/