linux-kernel - Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups]

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

Date:	Mon, 19 Oct 2009 11:08:56 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
cc:	nut-upsuser@...ts.alioth.debian.org, <linux-usb@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard
 [DEBUG logs included upsd/upsmon/usbhid-ups]

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@....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

--
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/