linux-kernel - Re: USB/UPS connectivity issue on Intel DP55KG Motherboard

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]

Message-ID: <alpine.DEB.2.00.0910140359070.15961@p34.internal.lan>
Date:	Wed, 14 Oct 2009 03:59:54 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Robert Hancock <hancockrwd@...il.com>
cc:	nut-upsuser@...ts.alioth.debian.org, linux-kernel@...r.kernel.org
Subject: Re: USB/UPS connectivity issue on Intel DP55KG Motherboard



On Tue, 13 Oct 2009, Robert Hancock wrote:

> On 10/13/2009 03:55 PM, Justin Piszcz wrote:
>> Hello,
>> 
>> I use the following in my ups.conf:
>> 
>> # USB:
>> [apc]
>> driver = usbhid-ups
>> port = auto
>> desc = "APC 1500VA"
>> pollfreq = 5
>> 
>> On my new motherboard (an Intel DP55KG), every once and awhile I get this:
>> 
>> Broadcast Message from nut@....com
>> (somewhere) at 17:48 ...
>> 
>> Communications with UPS apc@...alhost lost
>> 
>> 
>> Broadcast Message from nut@....com
>> (somewhere) at 17:48 ...
>> 
>> Communications with UPS apc@...alhost established
>> 
>> On my previous motherboard (a DG965WH), the exact same configuration was
>> used
>> and I never had this issue.
>> 
>> Any hints?
>> 
>> Should I increase the pollfreq to say 30 seconds?
>> 
>> Would this 'workaround' the problem?
>> 
>> Is this a known bug on this chipset?
>
> Anything unusual showing up in dmesg?
>

Hi Robert,

Nothing abormal..

[10729.035092] 3w-9xxx: scsi1: AEN: INFO (0x04:0x004E): Battery capacity 
test started:.
[10729.035485] 3w-9xxx: scsi1: AEN: INFO (0x04:0x0055): Battery charging 
started:.
[10730.253460] 3w-9xxx: scsi1: AEN: INFO (0x04:0x0056): Battery charging 
completed:.

Should I run the upsmon/etc with maximum debug/to get a trace?

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