mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: nut-upsuser@lists.alioth.debian.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups]
Date: Mon, 19 Oct 2009 11:14:03 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0910191112380.7710@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0910191100050.3899-100000@iolanthe.rowland.org>



On Mon, 19 Oct 2009, Alan Stern wrote:

> On Sun, 18 Oct 2009, Justin Piszcz wrote:
>
>> Thanks Alan,
>>
>> I have performed all of the steps you recommended, there is also a bug in
>> the docs, the directory seems to be different, or at least if you have
>> everything compiled into the kernel and not using modules.
>
>> Start nut:
>> # /etc/init.d/nut start
>> Starting Network UPS Tools: upsdrvctl upsd upsmon.
>>
>> Within ~20-30 seconds it already broke:
>> ============================================================================
>> Broadcast Message from nut@p34.internal.lan
>>          (somewhere) at 17:22 ...
>
> Well, the usbmon trace shows that wherever the problem lies, it isn't
> in the kernel.  There were a few problems in the device itself -- it
> was queried for a report and did not provide any data.  The nut program
> should be smart enough to retry when this happens, but it didn't.
>
> It did try to re-establish communcation with the device, but it appears
> that nut got caught in a loop during this attempt.  During this loop
> nut did nothing but transfer a bunch of string descriptors from the
> device, over and over again at 2-second intervals.  The loop lasted for
> almost a minute, until another device error occurred.  Then nut
> recovered properly -- until a third error happened and nut got stuck in
> its loop again.
>
> Alan Stern
>

Hi,

To the nut list, the last time nut changed was 2009-06-13:

2009-06-13 04:29:25 configure nut-cgi 2.4.1-3 2.4.1-3
2009-06-13 04:29:25 status unpacked nut-cgi 2.4.1-3
2009-06-13 04:29:25 status unpacked nut-cgi 2.4.1-3
2009-06-13 04:29:25 status unpacked nut-cgi 2.4.1-3
2009-06-13 04:29:25 status unpacked nut-cgi 2.4.1-3
2009-06-13 04:29:25 status unpacked nut-cgi 2.4.1-3
2009-06-13 04:29:25 status half-configured nut-cgi 2.4.1-3
2009-06-13 04:29:26 status installed nut-cgi 2.4.1-3

I made no changes to the nut configuration or install.

What did change was the motherboard.

From: Intel DG965WH -> Intel DP55KG

Then this problem began.

Justin.


      reply	other threads:[~2009-10-19 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 21:55 USB/UPS connectivity issue on Intel DP55KG Motherboard Justin Piszcz
2009-10-13 23:56 ` Justin Piszcz
2009-10-14  0:33 ` Robert Hancock
2009-10-14  7:59   ` Justin Piszcz
2009-10-14 13:25     ` [Nut-upsuser] USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups] Justin Piszcz
     [not found]       ` <alpine.DEB.2.00.0910140926560.19307@p34.internal.lan>
2009-10-18 20:23         ` 2.6.31.4: " Justin Piszcz
2009-10-18 20:42           ` Alan Stern
2009-10-18 21:40             ` Justin Piszcz
2009-10-19 14:23               ` Alan Stern
2009-10-19 14:55                 ` Justin Piszcz
2009-10-19 15:12                   ` Justin Piszcz
2009-10-19 15:13                   ` Alan Stern
2009-10-19 15:08               ` Alan Stern
2009-10-19 15:14                 ` Justin Piszcz [this message]

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=alpine.DEB.2.00.0910191112380.7710@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nut-upsuser@lists.alioth.debian.org \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®