[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-pm] [dm-devel] dm-crypt low performance



Hi Alan,


On Wednesday 14 Jan 2009 01:30:59 Alan Stern wrote:
> >
> > rrs learner:~$ cat /tmp/lsusb.suspend
> > Bus 005 Device 005: ID 046d:08c6 Logitech, Inc. QuickCam for DELL
> > Notebooks Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 004 Device 007: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 001 Device 005: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
> > Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Notice that the IDE Adapter is now attached to a 1.1 bus rather than a
> 2.0 bus.  That's why it's running so much slower.
>
> > And here's the usb device listing after a fresh boot.
> >
> > rrs learner:~$ lsusb
> > Bus 005 Device 004: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter
> > Bus 005 Device 003: ID 046d:08c6 Logitech, Inc. QuickCam for DELL
> > Notebooks Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 001 Device 004: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
> > Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Try building a kernel with CONFIG_USB_DEBUG enabled, and post the dmesg
> log showing what happens during the disconnect, hibernate, resume, and
> reconnect.
>
> You could also try the same thing with no disconnect/reconnect.  Just
> leave the IDE adapter plugged in the whole time.
>

I've been testing the same hardware but unfortunately wasn't able to see the 
issue back again. One thing to notice is that the laptop has 4 USB ports out 
of which 3 are 1.1 and only 1 is 2.0.
The suspected faulty USB HDD Enclosure has 2 cables that I was connecting to, 
thus ending up connecting them to a 2.0 and 1.1 USB port.

I tried with just 1 port connected to USB 2.0 port and haven't been able to 
reproduce the issue back again yet. :-(
I also wasn't able to reproduce back the old issue with the pattern I 
mentioned in the previous post (1 cable connected to 1.1 and the other 
connected to 2.0 port)

I'll keep testing and post to this thread if I find something useful.

Thanks,
Ritesh
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

Attachment: signature.asc
Description: This is a digitally signed message part.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]