> I've managed to reproduce the problem despite cutting the link between 4
> and 1,6 in both directions on my null modem cables.
> usb 1-1.1: uhci_result_common: failed with status 44
> usb 1-1.2: uhci_result_common: failed with status 44
> hub 1-1:1.0: state 7 ports 4 chg evt 0006
>
Am Freitag, 25. Mai 2007 16:11 schrieb Alan Stern:
> On Fri, 25 May 2007, Sam Liddicott wrote:
>
> > I removed the USB keyboard and mouse to make things simpler.
> >
> > Still no joy, not even with any_ports_active returning 1 (and printk
> > added there to be sure).
> >
> > Looks like a usbmon
On Fri, 25 May 2007, Sam Liddicott wrote:
> I removed the USB keyboard and mouse to make things simpler.
>
> Still no joy, not even with any_ports_active returning 1 (and printk
> added there to be sure).
>
> Looks like a usbmon trace is needed; I'll get that to you as soon as the
> kernel rebui
Am Freitag, 25. Mai 2007 11:27 schrieb Sam Liddicott:
> de847900 337684980 C Bi:003:01 0 2 = 0160
> de847900 337684982 S Bi:003:01 -115 512 <
> dd660380 337812432 S Ci:003:00 s c0 05 0002 2 <
> df65b240 337864414 C Ii:001:01 0 1 = 04
> df65b240 337864422 S Ii:001:01 -115 2 <
> dd660ce0 33
I think it maybe the carrier detect handling that is causing the
problem, I'm investigating this.
Sam
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control o
Here is usbmon output.
The first cluster of traffic is (I believe) when minicom starts.
The final cluster of traffic is (I believe) when everythnig breaks.
Sam
dd660740 334756980 S Co:003:00 s 40 00 0
dd660740 334759010 C Co:003:00 0 0
dd660740 334759057 S Co:003:00 s 40 04 0008 0
Am Donnerstag, 24. Mai 2007 16:13 schrieb Alan Stern:
> On Thu, 24 May 2007, Oliver Neukum wrote:
>
> > > Am Donnerstag, 24. Mai 2007 14:25 schrieb Sam Liddicott:
> > > Recompiled and:
> > > # CONFIG_USB_SUSPEND is not set
> > >
> > > Same problem, and still get the:
> > >
> > > usb usb2: suspen
On Thu, 24 May 2007, Oliver Neukum wrote:
> > Am Donnerstag, 24. Mai 2007 14:25 schrieb Sam Liddicott:
> > Recompiled and:
> > # CONFIG_USB_SUSPEND is not set
> >
> > Same problem, and still get the:
> >
> > usb usb2: suspend_rh (auto-stop)
>
> Odd, even impossible. Did you replace all USB modu
Am Donnerstag, 24. Mai 2007 14:25 schrieb Sam Liddicott:
> Recompiled and:
> # CONFIG_USB_SUSPEND is not set
>
> Same problem, and still get the:
>
> usb usb2: suspend_rh (auto-stop)
Odd, even impossible. Did you replace all USB modules?
Regards
Oliver
--
SUSE LINUX Pro
> usbserial_generic 1-2.2:1.0: usb_probe_interface
> usbserial_generic 1-2.2:1.0: usb_probe_interface - got id
> ftdi_sio 1-2.2:1.0: usb_probe_interface
> ftdi_sio 1-2.2:1.0: usb_probe_interface - got id
> ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected
> drivers/usb/serial/ftdi_sio.
For some reason usb-devel is bouncing these messages saying:
Message rejected by filter rule match
Anyway, kernel 2.6.18 compiled with
CONFIG_USB_DEBUG=y
dmesg seems more detailed but /var/log/messages is not, so I have both:
Anyway, here goes:
Here we have /var/log/messages of the modprobe
M
* Oliver Neukum wrote, On 23/05/07 15:03:
>
> Sorry for the harsh words.
>
Your attention more than compensates, I thank you.
> Please recompile with USB_DEBUG. This may yield more info.
>
The build will probably take all night, but I'll have details first
thing tomorrow.
Sam
--
Am Mittwoch, 23. Mai 2007 15:55 schrieb Sam Liddicott:
> * Oliver Neukum wrote, On 23/05/07 14:46:
> > Am Mittwoch, 23. Mai 2007 15:42 schrieb Sam Liddicott:
> >
> >> May 23 14:32:48 shep kernel: drivers/usb/serial/ftdi_sio.c: Detected
> >> FT232BM
> >> May 23 14:32:48 shep kernel: usb 1-2.2: F
Am Mittwoch, 23. Mai 2007 15:42 schrieb Sam Liddicott:
> May 23 14:32:48 shep kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM
> May 23 14:32:48 shep kernel: usb 1-2.2: FTDI USB Serial Device converter
> now attached to ttyUSB1
>
> Here I power up the remote device
>
> May 23 14:33:32 shep
Am Mittwoch, 23. Mai 2007 15:13 schrieb Sam Liddicott:
> and here is where the handshake line changes to make the serial port
> "online"
>
> May 23 12:04:33 shep kernel: usb 1-2.2: USB disconnect, address 5
> May 23 12:04:33 shep kernel: ftdi_sio 1-2.2:1.0: device disconnected
> May 23 12:04:33 sh
Am Mittwoch, 23. Mai 2007 14:20 schrieb Sam Liddicott:
> Sorry, I thought I'd said: 2.4.20-8 (rh9) , 2.6.18-4-686 (debian 4),
> 2.6.20-15 (ubuntu feisty)
> I tried a 2.6.22rc2 build based on the debian .config file but it
> wouldn't boot, so I got something wrong.
Please try a vanilla kernel.
> >
Am Mittwoch, 23. Mai 2007 13:07 schrieb Sam Liddicott:
> I've got some ftdi usb-serial devices causing mass USB hanging on SOME
> hardware often; it seems when the remote serial device asserts DSR or
> some such handshaking line.
Which kernel version?
Can you provide a dmesg with timestamps?
17 matches
Mail list logo
