I have recently upgraded my 2.6.28 gentoo-sources from another version and I noticed today that no 2303 dongle is working anymore (I have 6 so probably no hardware failure.) Thus I tried the dongles using my iBook that is running a 2.6.29-rc. Surprisingly connecting to that machine doesn't give the error. The URL describes the error; but reading that, the fix Alan suggests is in the current 2.6.28 gentoo sources and obviously does not fix it. Now I can upgrade to .29 on my amd64 system, to verify, but I guess there is something wrongly applied to the gentoo tree since (iirc) -r1 did not fail. Reproducible: Always Steps to Reproduce: 1. connect pl2303 2. cat /dev/ttyUSB0 Actual Results: i/o error. Expected Results: Just something that waits for input from the device. paludis 0.34.5 Paludis build information: Compiler: CXX: x86_64-pc-linux-gnu-g++ 4.3.3 CXXFLAGS: -march=athlon64 -O2 -pipe -msse3 LDFLAGS: DATE: 2009-02-27T21:55:43+0100 Libraries: C++ Library: GNU libstdc++ 20090124 Reduced Privs: reduced_uid: 105 reduced_uid->name: paludisbuild reduced_uid->dir: /dev/null reduced_gid: 1007 reduced_gid->name: paludisbuild Paths: DATADIR: /usr/share LIBDIR: /usr/lib64 LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc PYTHONINSTALLDIR: RUBYINSTALLDIR: Environment: Format: paludis Config dir: /etc/paludis World file: /var/db/pkg/world
Please extend to general serial usb layer; .29 still seems to fix issues, also on the affected system.
Can you tell me if vanilla sources 2.6.28.7 has the problem?
(In reply to comment #2) > Can you tell me if vanilla sources 2.6.28.7 has the problem? I'll give it a shot.
This should be resolved in 2.6.28, if not, please let the upstream kernel developers (i.e. me in this case), know about it.
(In reply to comment #4) > This should be resolved in 2.6.28, if not, please let the upstream kernel > developers (i.e. me in this case), know about it. Tested 2.6.28.8 that gives a working USB thing. Strangely I have no reason to assume that the reported kernel did consistently fail. Because within that kernel I did have a working USB Serial port. But as reported out of the blue the i/o error was there. (I can say there were a lot of insmods and actually two different usb serial drivers). Tested them now too, both work.
Ok, closing out as not a bug, thanks for retesting.