From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-usb@vger.kernel.org, nut-upsuser@lists.alioth.debian.org
Subject: 2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue?
Date: Thu, 29 Oct 2009 10:58:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0910291047530.14066@p34.internal.lan> (raw)
Hello,
Problem: When I migrated from a DG965WH -> DP55KG motherboard, there were
quite a bit of issues, host still does not reboot without special flags,
e.g. reboot=a, the NIC driver is broken with the in-kernel version (the
one on e1000.sourceforge) fixes that and finally my UPS USB has driver
stale problems, with two issues already relating to the HW/drivers
themselves it would not be unrealistic to speculate that there could be an
issue with the USB chipset/driver with this P55 motherboard.
Is anyone else out there running an APC1500VA UPS on a P55 motherboard?
If so, what have been your results?
Motherboard: Intel P55KG
Kernel: 2.6.31.4 x86_64
Details from nut/kernel usb trace:
http://home.comcast.net/~jpiszcz/20091014/nut-problem.txt
The last thread petered out:
http://www.gossamer-threads.com/lists/linux/kernel/1143579
# From ups -D
Got 2 HID objects...
Quick update...
upsdrv_updateinfo...
Got 2 HID objects...
Quick update...
Can't retrieve Report 22: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
upsdrv_updateinfo...
Got to reconnect!
Can't retrieve Report 19: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
Can't retrieve Report 15: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
upsdrv_updateinfo...
# From the system logs:
Broadcast Message from nut@p34.internal.lan
(somewhere) at 6:01 ...
Communications with UPS apc@localhost lost
Broadcast Message from nut@p34.internal.lan
(somewhere) at 6:02 ...
Communications with UPS apc@localhost established
Broadcast Message from nut@p34.internal.lan
(somewhere) at 6:03 ...
# From ups.conf:
[apc]
driver = usbhid-ups
port = auto
desc = "APC 1500VA"
All other USB devices work properly, USB CD/DVD writer, keyboard, mouse,
etc. The same UPS (APC 1500VA) worked fine on the last board, same cable,
etc. I have tried power cycling the UPS and using a different port on the
motherboard, to no avail.
Aside from purchasing a different UPS (if I wanted to use nut)- is it
possible there is a bug in the chipset on these P55 boards in the way the
driver communicates with it?
Since this problem is 100% reproducible every time, is there anyway to
look into this issue any further?
Justin.
next reply other threads:[~2009-10-29 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 14:58 Justin Piszcz [this message]
2009-10-31 11:59 ` 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS'] Justin Piszcz
2009-10-31 15:18 ` Alan Stern
2009-10-31 23:43 ` Justin Piszcz
2009-11-01 0:07 ` Arjan van de Ven
2009-11-01 8:55 ` Justin Piszcz
2009-11-01 17:11 ` Alan Stern
2009-11-01 17:52 ` Matthew Dharm
2009-11-01 21:18 ` Justin Piszcz
2009-11-01 21:25 ` Justin Piszcz
2009-11-02 0:49 ` Matthew Dharm
2009-11-02 13:43 ` Henrique de Moraes Holschuh
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.0910291047530.14066@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 \
/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®