From: Sergei Organov <osv@javad.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: moxa serial driver testing
Date: Mon, 25 Dec 2006 16:41:56 +0300 [thread overview]
Message-ID: <871wmom6sb.fsf@javad.com> (raw)
In-Reply-To: <552766292581216610@wsc.cz> (Jiri Slaby's message of "Sat, 23 Dec 2006 02:35:46 +0100 (CET)")
Jiri Slaby <jirislaby@gmail.com> writes:
> osv@javad.com wrote:
>> Hi Jiri,
>>
>> I've figured out that both old and new mxser drivers have two similar
>> problems:
>>
>> 1. When there are data coming to a port, sometimes opening of the port
>> entirely locks the box. This is quite reproducible. Any idea what's
>> wrong and how can I help to debug it?
>
> Could you test the patch below, if something changes?
Something did change. Now it becomes rather difficult to get the box to
hang, though not impossible. Another thing that changed is that now I
can see [parts of] oopses on screen. I've got two pictures of the screen
with different oopses. If you need them, let me know and I'll send them
to you in a separate mail not to pollute lkml with JPEGs.
One of these oopses happened on kernel with lock debugging enabled, but
I can't see anything relevant in dmesg log after resetting the box.
SysRq magic still doesn't work after hang.
As for the problem with module unloading when port is open, your another
patch does fix it indeed.
-- Sergei.
next prev parent reply other threads:[~2006-12-25 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45222E7E.3040904@gmail.com>
[not found] ` <87wt7hw97c.fsf@javad.com>
[not found] ` <4522ABC3.2000604@gmail.com>
[not found] ` <878xjx6xtf.fsf@javad.com>
[not found] ` <4522B5C2.3050004@gmail.com>
[not found] ` <87mz8borl2.fsf@javad.com>
[not found] ` <45251211.7010604@gmail.com>
[not found] ` <87zmcaokys.fsf@javad.com>
[not found] ` <45254F61.1080502@gmail.com>
[not found] ` <87vemyo9ck.fsf@javad.com>
[not found] ` <4af2d03a0610061355p5940a538pdcbd2cda249161e8@mail.gmail.com>
[not found] ` <87vemtnbyg.fsf@javad.com>
[not found] ` <452A1862.9030502@gmail.com>
[not found] ` <87r6urket6.fsf@javad.com>
2006-12-22 19:54 ` moxa serial driver testing Jiri Slaby
2006-12-23 1:09 ` Jiri Slaby
2006-12-23 1:35 ` Jiri Slaby
2006-12-23 9:09 ` Sergei Organov
2006-12-25 11:26 ` Sergei Organov
2006-12-25 13:41 ` Sergei Organov [this message]
2006-12-25 18:39 ` Jiri Slaby
2006-12-25 18:49 ` Sergei Organov
2006-12-25 16:17 ` moxa serial driver testing (oopses) Sergei Organov
2006-12-27 11:09 ` moxa serial driver testing Sergei Organov
2006-12-27 11:48 ` Sergei Organov
2006-12-27 13:36 ` Jiri Slaby
2006-12-27 14:00 ` Sergei Organov
2006-12-27 15:29 ` Sergei Organov
2006-12-28 17:14 ` Sergei Organov
2006-12-28 23:32 ` Jiri Slaby
2006-12-29 8:56 ` Sergei Organov
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=871wmom6sb.fsf@javad.com \
--to=osv@javad.com \
--cc=akpm@osdl.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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