I upgraded kernel to 2.6.34, and found that this kernel doesn't work correctly with my UPS USB->serial (cypress_m8 based). ttyUSB0 was successfully created, but nut can't read response from UPS. At startup I get such message: Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1) data receiving error (0 instead of 16 bytes) data receiving error (0 instead of 16 bytes) After compiling driver from 2.6.32.7 kernel for 2.6.34 - all works OK.
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Fri, 18 Jun 2010 10:31:12 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=16245 > > Summary: Powercom BNT-800AP (cypress_m8 usb->serial inside) > doesn't work with NUT on 2.6.34 kernel > Product: Drivers > Version: 2.5 > Kernel Version: 2.6.34 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Serial > AssignedTo: rmk@arm.linux.org.uk > ReportedBy: nitr0@seti.kr.ua > Regression: No > > > I upgraded kernel to 2.6.34, and found that this kernel doesn't work > correctly > with my UPS USB->serial (cypress_m8 based). ttyUSB0 was successfully created, > but nut can't read response from UPS. At startup I get such message: > > Network UPS Tools - UPS driver controller 2.4.1 > Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1) > data receiving error (0 instead of 16 bytes) > data receiving error (0 instead of 16 bytes) > > After compiling driver from 2.6.32.7 kernel for 2.6.34 - all works OK. > Looks like s 2.6.32 -> 2.6.34 USB regression.
Does 2.6.33.y work?
As I see in git, 2.6.33 haven't changes in cypress_m8 compared to 2.6.32, last commit in both trees - 2009-10-09 by Oliver Neukum...
On 2.6.35 kernel all seems to be OK.