mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
	"Nick Pasich" <NewsLetters@NickAndBarb.net>,
	<linux-usb-devel@lists.sourceforge.net>
Cc: "Greg Kroah-Hartman" <greg@kroah.com>,
	"Al Borchers" <alborchers@steinerpoint.com>,
	<linux-kernel@vger.kernel.org>,
	"Peter Berger" <pberger@brimson.com>
Subject: Re: [linux-usb-devel] Edgeport UPS Monitoring Problems
Date: Sat, 28 Jul 2007 19:10:54 -0400	[thread overview]
Message-ID: <003701c7d16c$8c72b7b0$03c8a8c0@kroptech.com> (raw)
In-Reply-To: <20070727152254.202959c1.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Fri, 27 Jul 2007 13:37:08 -0700
> Nick Pasich <NewsLetters@NickAndBarb.net> wrote:
>
>>
>> Greg/Peter/Al,
>
> added linux-usb-devel.
>
>> I've been using the edgeport 4 port USB to Serial Converter
>> to monitor APC Smart UPS's via apcupsd for quite awhile on
>> various Linux boxes.
>>
>> I just upgraded to Kernel Version 2.6.22.1 from 2.6.20.6 on a
>> couple of systems and both the edgeports stopped communicating.
>>
>> I tried applying various patches, "PATCH 026/149" and "PATCH 082/149"
>> and one by Alan Cox..  but they didn't fix the problem.
>>
>> I copied the 2.6.20.6 edgeport module sources to the new
>> 2.6.22.1 tree and everything works again.
>>
>>           linux/drivers/usb/serial/io_edgeport.c
>>           linux/drivers/usb/serial/io_edgeport.h
>>           linux/drivers/usb/serial/io_edgeport.mod.c
>>           linux/drivers/usb/serial/io_tables.h
>
> Straightforward regression, most serious.  Thanks for reporting it.

I don't know much of anything about usb-serial, but I'll take a whack at 
it. Could you enable debug for that driver, launch apcupsd, and report 
any intersting messages that show up in dmesg? I'd be especially 
interested in any "Not setting..." or "Not writing..." messages, because 
some critical-looking code for baud rate setting and similar became 
conditional in 2.6.22.1 whereas it was always executed before. Apcupsd 
is going to be rather unhappy if the baud rate doesn't change when it 
asks. The debug should show if the these operations are being ignored on 
your hw.

--Adam


  reply	other threads:[~2007-07-29  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 20:37 Nick Pasich
2007-07-27 22:22 ` Andrew Morton
2007-07-28 23:10   ` Adam Kropelin [this message]
2007-07-29 12:48     ` [linux-usb-devel] " Nick Pasich
2007-07-29 14:04       ` Adam Kropelin
2007-07-29 14:36         ` Nick Pasich

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='003701c7d16c$8c72b7b0$03c8a8c0@kroptech.com' \
    --to=akropel1@rochester.rr.com \
    --cc=NewsLetters@NickAndBarb.net \
    --cc=akpm@linux-foundation.org \
    --cc=alborchers@steinerpoint.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=pberger@brimson.com \
    /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

Powered by JetHome