From: Corey Minyard <minyard@acm.org>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [PATCH] Serial 8250: Handle saving the clear-on-read bits from the LSR and MSR
Date: Fri, 04 May 2007 13:47:24 -0500 [thread overview]
Message-ID: <463B7FBC.3090907@acm.org> (raw)
In-Reply-To: <200705041304.02618.gene.heskett@gmail.com>
Gene Heskett wrote:
> On Friday 04 May 2007, Corey Minyard wrote:
>
>> I did think of one other thing: if you clear the MSR delta flags while
>> polling the serial console, you need to call the routine to check the
>> modem status since the interrupt will not happen. So here's the
>> patch...
>>
>> Subject: Serial 8250: Handle saving the clear-on-read bits from the LSR and
>> MSR
>>
>>
> I applied this patch because I was curious to see what effect if any it had on
> some serial based acessories I use here, like a cm11 x10 controller with
> heyu, and a belkin ups with its supplied software.
>
> But at first boot, its not 100% operationally safe, but please read on.
>
> 1) heyu (the x10 control program) is now stuck in a loop, repeating the last
> command issued, at about 40 second repeat intervals. AND it is using 90%+ of
> the cpu while it executes each loop, which takes about 7 to 10 seconds each
> time. heyu is interfacing to the world via /dev/ttyUSB0, through an FTDI
> adapter so I'm not able to make a mental connection here between this patch
> and that effect.
>
> 2) HOWEVER! The belkin upsd daemon, which started being a cpu hog, using 40%
> of the cpu continuously since something in the 2.6.20 to 2.6.21 time frame,
> and this was regardless of whether it was talking through a /dev/ttyUSB# port
> and either a pl2303, or an FTDI adaptor, or direct through /dev/ttyS0, is at
> least for /dev/ttyS0, now operating normally and apparently 100% stable. So
> I pulled out another FTDI adaptor, and reconfigured the daemon to
> use /dev/ttyUSB1, and that is also operating 100% normally now.
>
> Can someone explain 1) above? Even odder still, I'd killed and restarted heyu
> several times to no avail before I tried putting upsd on /dev/ttyUSB1, but
> after moving the upsd access from /dev/ttyS0 to /dev/ttyUSB1, then heyu,
> running through /dev/ttyUSB0, is now operating 100% normally. ???
>
> Does anyone have any idea what kind of bait I should put out to kill this
> nilmerg? I'm happy, its all working again for a change, but I'll be damned
> if I ain't totally bumfuzzled. And I wonder if it will survive a reboot...
>
>
I really doubt that this patch had anything to do with these issues,
especially
the ones over USB. However, if you can reliably remove the patch, test, and
reapply the patch, and test, and the issues remain the same, then it's
perhaps
something significant, though I would be at a loss to know what it was.
-corey
next prev parent reply other threads:[~2007-05-04 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 13:15 [PATCH] Serial 8250: Handle saving the clear-on-read bits from the LSR and MSR Corey Minyard
2007-05-04 17:04 ` Gene Heskett
2007-05-04 18:47 ` Corey Minyard [this message]
2007-05-06 16:58 ` Gene Heskett
2007-05-06 18:14 ` Russell King
2007-05-16 17:41 ` Corey Minyard
2007-05-17 2:10 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2007-07-07 0:38 Corey Minyard
2007-07-06 19:42 Corey Minyard
2007-07-06 20:09 ` Alan Cox
2007-07-06 21:32 ` Corey Minyard
2007-07-06 21:41 ` Alan Cox
2007-05-02 14:29 Corey Minyard
2007-05-02 19:08 ` Russell King
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=463B7FBC.3090907@acm.org \
--to=minyard@acm.org \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.