linux-kernel - MOXA I/O errors on 2.6.28+

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-next>] [day] [month] [year] [list]

Message-ID: <20090314213630.GA3375@fi.muni.cz>
Date:	Sat, 14 Mar 2009 22:36:30 +0100
From:	Jan Kasprzak <kas@...muni.cz>
To:	jirislaby@...il.com
Cc:	linux-kernel@...r.kernel.org
Subject: MOXA I/O errors on 2.6.28+

	Hello,

I have several servers with MOXA C320 serial boards. Starting with 2.6.28,
some ports on MOXA boards sometimes get to a state where open("/dev/ttyMX<n>")
returns -EIO. I use the servers with MOXA boards as serial console hubs,
and I think the EIO state is caused by the remote getty or the whole remote
server being restarted.

	After getting EIO, this particular port always returns EIO, until
the server is rebooted. The moxa module usage count is non-zero (even when
nobody has the board open), so reloading just the moxa.ko module is not
possible.

	2.6.27 is OK, 2.6.28 and 2.6.29-rc8 is faulty. I can git bisect
if you want (I have a spare server which I can reboot at will).

	My MOXA boards are

01:08.0 Serial controller: Moxa Technologies Co Ltd Intellio C320 Turbo PCI (rev 02)

	What can I do to have this problem fixed? Thanks,

-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/ |
>>  If you find yourself arguing with Alan Cox, you’re _probably_ wrong.  <<
>>     --James Morris in "How and Why You Should Become a Kernel Hacker"  <<
--
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/