RE: usb hub is n't recognised during boot up(sometimes)

2012-07-10 Thread Sadasivan Shaiju
 No controller found.
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using NMI interrupt.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
ehci_hcd :00:1d.0: USBCMD = 00010021 USBSTS = 8008 USBINTR =
0037 FR
INDEX = 1bad CTRLDSSEGMENT =   PERIODICLISTBASE = 98006000
ASYNCLIS
TADDR  = 98004060 CONFIGFLAG = 0001
ehci_hcd :00:1d.0: PORTSC4096 = 0001
ehci_hcd :00:1d.0: PORTSC4096 = 0001
ehci_hcd :00:1d.0: PORTSC4101 = 0001
ehci_hcd :00:1d.0: IAA with nothing to reclaim?
usb 1-1: link qh256-0001/8801581afa00 start 1 [1/0 us]
Freeing unused kernel memory: 15100k freed
Write protecting the kernel read-only data: 4984k
ehci_hcd :00:1d.0: port 1 reset error -110
hub 2-0:1.0: hub_port_status failed (err = -32)
hub 2-0:1.0: port_wait_reset: err = -32
hub 2-0:1.0: port 1 not enabled, trying reset again...
ehci_hcd :00:1d.0: USBCMD = 00010001 USBSTS = 2008 USBINTR =
0037 FR
INDEX = 2d3a CTRLDSSEGMENT =   PERIODICLISTBASE = 98006000
ASYNCLIS
TADDR  = 98004000 CONFIGFLAG = 0001
ehci_hcd :00:1d.0: PORTSC4096 = 
ehci_hcd :00:1d.0: PORTSC4096 = 
ehci_hcd :00:1d.0: PORTSC4353 = 
ehci_hcd :00:1d.0: port 1 full speed --> companion
ehci_hcd :00:1d.0: GetStatus port 1 status 003801 POWER OWNER sig=j
CONNECT
hub 2-0:1.0: port 1 not reset yet, waiting 200ms
ehci_hcd :00:1d.0: GetStatus port 1 status 003002 POWER OWNER sig=se0
CSC
hub 1-1:1.0: state 7 ports 6 chg  evt 
hub 2-0:1.0: state 7 ports 3 chg  evt 0002
e1000e: Intel(R) PRO/1000 Network Driver - 1.9.5-NAPI
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
i801_smbus :00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ACPI: I/O resource :00:1f.3 [0x3000-0x301f] conflicts with ACPI region
SMBI
[0x3000-0x300f]
ACPI: This conflict may cause random problems and system instability
ACPI: If an ACPI driver is available for this device, you should use it
instead
of the native driver
iTCO_wdt: Enabling WDT ISR from init.
iTCO_wdt: Found a 3420 TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e :00:19.0: setting latency timer to 64
e1000e :00:19.0: irq 314 for MSI/MSI-X
e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1)
88:88:88:88:87:88
e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e :00:19.0: eth0: MAC: 10, PHY: 9, PBA No: FF-0FF
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
cpld_driver: cp_board_type = 16
cpld_driver: mstp_subtype = 6
cpld_driver: mstp_gbdtype = 10
cpld2kp_driver: cp_board_type = 16
cpld_driver: mstp_subtype = 6
cpld_driver: mstp_bdtype = 10
cpld_cpp_ecsr_base_p = c900100d6800
rmonbifo_mod: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
rmonbifo.ko loaded. 0.0.3 Date Jul  4 2012 10:20:22
Copyright (c) 2005-2012 by Cisco Systems, Inc.
rmonbifo.ko loaded. 0.0.3 Date Jul  4 2012 10:20:22
Copyright (c) 2005-2012 by Cisco Systems, Inc.


Regards,
Shaiju.

-Original Message-
From: Peter Chen [mailto:hzpeterc...@gmail.com]
Sent: Wednesday, July 04, 2012 6:08 PM
To: shaiju shaiju
Cc: Alan Stern; Sadasivan Shaiju; USB list
Subject: Re: usb hub is n't recognised during boot up(sometimes)

>> Is  a  port reset (once)  in hub_port_init()  will be  enough ?
>>
> Usually, there is a Reset pin at HUB, you can use a GPIO to control it.
>
> Here  I  am  attaching  the  spec I am using .  I  could n't  find  a
> pin Reset  the  hub .  I can  reset  the  controller  though.
>
Does your hub be in the CPU or out of CPU? It is out of CPU, it is an
external peripheral IC, its vendor should have its datasheet.

Meanwhile, try to disable your usb1 and try to disable CONFIG_USB_SUSPEND.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: usb hub is n't recognised during boot up(sometimes)

2012-07-27 Thread Sadasivan Shaiju
Hi  Peter,

I  see  the  following  error in  our  system .  Any  idea  why  this  is
happening  ?

.

[   87.929163] hub 1-0:1.0: state 7 ports 6 chg  evt 0004
[   87.929178] ehci_hcd :00:1a.7: GetStatus port 2 status 001002 POWER
sig=se0 CSC
[   87.929187] hub 1-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
[   87.929191] usb 1-2: USB disconnect, address 2
[   87.929193] usb 1-2: unregistering device
[   87.929195] usb 1-2: unregistering interface 1-2:1.0

..
.
..

[  139.717154] Pid: 265, comm: khubd Tainted: P   2.6.32.39 #3
[  139.717157] Call Trace:
[  139.717165]  [] ? warn_slowpath_common+0x76/0x8c
[  139.717169]  [] ? mark_buffer_dirty+0x23/0x80
[  139.717175]  [] ? ext2_sync_fs+0x7e/0xa4
[  139.717178]  [] ? __sync_filesystem+0x3f/0x50
[  139.717182]  [] ? fsync_bdev+0x1e/0x43
[  139.717187]  [] ? bdget_disk+0x2d/0x38
[  139.717190]  [] ? invalidate_partition+0x1c/0x39
[  139.717194]  [] ? del_gendisk+0x2d/0x10c
[  139.717198]  [] ? kobject_del+0x23/0x2d
[  139.717203]  [] ? sd_remove+0x43/0x7c
[  139.717207]  [] ? __device_release_driver+0x65/0xb0
[  139.717211]  [] ? device_release_driver+0x1d/0x28
[  139.717214]  [] ? bus_remove_device+0xa8/0xbd
[  139.717218]  [] ? device_del+0x120/0x15e
[  139.717223]  [] ? __scsi_remove_device+0x4c/0x9b
[  139.717226]  [] ? scsi_forget_host+0x3e/0x5c
[  139.717230]  [] ? scsi_remove_host+0x70/0xf0
[  139.717234]  [] ? quiesce_and_remove_host+0x51/0x86
[  139.717237]  [] ? usb_stor_disconnect+0x15/0x1e
[  139.717242]  [] ? usb_unbind_interface+0x45/0xb4
[  139.717245]  [] ? __device_release_driver+0x65/0xb0
[  139.717249]  [] ? device_release_driver+0x1d/0x28
[  139.717252]  [] ? bus_remove_device+0xa8/0xbd
[  139.717255]  [] ? device_del+0x120/0x15e
[  139.717259]  [] ? usb_disable_device+0x8a/0x17e
[  139.717263]  [] ? usb_disconnect+0xd8/0x165
[  139.717266]  [] ? hub_thread+0x61d/0x1161
[  139.717272]  [] ? autoremove_wake_function+0x0/0x2a
[  139.717275]  [] ? hub_thread+0x0/0x1161
[  139.717278]  [] ? hub_thread+0x0/0x1161
[  139.717281]  [] ? kthread+0x75/0x7d
[  139.717284]  [] ? kthread+0x0/0x7d
[  139.717288]  [] ? child_rip+0xa/0x20
[  139.717291]  [] ? kthread+0x0/0x7d
[  139.717295]  [] ? kthread+0x0/0x7d
[  139.717297]  [] ? child_rip+0x0/0x20
[  139.717300] ---[ end trace 6a5c8dd3186057de ]---
[  139.773331] EXT2-fs error (device sda1): ext2_readdir: bad page in #11
[  139.998662] usb 1-2: usb_disable_device nuking all URBs
[  140.008331] ehci_hcd :00:1a.7: GetStatus port 2 status 001803 POWER
sig=j CSC CONNECT
[  140.114873] hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms
status 0x501
[  140.165496] ehci_hcd :00:1a.7: port 2 high speed
[  140.165503] ehci_hcd :00:1a.7: GetStatus port 2 status 001005 POWER
sig=se0 PE CONNECT
[  140.216640] usb 1-2: new high speed USB device using ehci_hcd and
address 3
[  140.232833] lsmpi_open: device opened by pid 28084 instance 0
[  140.233071] lsmpi_vopen: vma 0x8801feec0a50 area 0x88027080
region #1 mapped for instance 0
[  140.234372] lsmpi_vopen: vma 0x8801feec0420 area 0x88027080
region #2 mapped for instance 0
[  140.234396] lsmpi_vopen: vma 0x8801feec04d0 area 0x88027080
region #3 mapped for instance 0
[  140.234410] lsmpi_vopen: vma 0x8801feec0d10 area 0x88027080
region #4 mapped for instance 0
[  140.234427] LSMPI: Register dual stack diverter
[  140.236414] lsmpi_vopen: vma 0x8801feec0b00 area 0x88027080
region #5 mapped for instance 0
[  140.269495] ehci_hcd :00:1a.7: port 2 high speed
[  140.269502] ehci_hcd :00:1a.7: GetStatus port 2 status 001005 POWER
sig=se0 PE CONNECT
[  140.334619] usb 1-2: default language 0x0409
[  140.336574] usb 1-2: udev 3, busnum 1, minor = 2
[  140.336578] usb 1-2: New USB device found, idVendor=0e39,
idProduct=2b00
[  140.336581] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[  140.336584] usb 1-2: Product: eUSB
[  140.336587] usb 1-2: Manufacturer: SMART
[  140.336588] usb 1-2: SerialNumber: 23156507103421210411
[  140.356995] usb 1-2: usb_probe_device
[  140.357000] usb 1-2: configuration #1 chosen from 1 choice
[  140.357266] usb 1-2: adding 1-2:1.0 (config #1, interface 0)
[  140.365815] usb-storage 1-2:1.0: usb_probe_interface
[  140.365823] usb-storage 1-2:1.0: usb_probe_interface - got id
[  140.365880] scsi5 : SCSI emulation for USB Mass Storage devices
[  140.392510]



Regards,
shaiju


-Original Message-
From: Peter Chen [mailto:hzpeterc...@gmail.com]
Sent: Tuesday, July 10, 2012 6:17 PM
To: Sadasivan Shaiju
Cc: shaiju shaiju; Alan Stern; USB list
Subject: Re: usb hub is n't recognised during boot up(sometimes)

> ehci_hcd :00:1d.0: port 1 reset error -110
It stands for software wants bus reset to complete, but hardware

RE: usb device getting disconnected

2012-08-07 Thread Sadasivan Shaiju
Hi  Alen/Peter ,

I  do  get  the  following error   while   the  system  is  up  and
running  .  Basically  the  USB  device   get  disconnected  .  Any
insight  into  the  problem ?


[160549.977172] hub 2-1:1.0: state 7 ports 6 chg  evt 0010^M
[160549.977275] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
1^M
[160549.977400] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
2^M
[160549.977524] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
3^M
[160549.977528] hub 2-1:1.0: port 4, status 0100, change 0001, 12 Mb/s^M
[160549.977650] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
4^M
[160549.977652] usb 2-1.4: USB disconnect, address 3^M
[160549.977654] usb 2-1.4: unregistering device^M
[160549.977656] usb 2-1.4: unregistering interface 2-1.4:1.0^M
[160549.92] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
5^M
[160549.977897] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
6^M
[160549.978020] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
7^M
[160549.978146] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
8^M
[160549.978269] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
9^M
[160549.978394] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
10^M
[160549.978519] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
11^M
[160549.978644] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
12^M
[160549.978770] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
13^M
[160549.978894] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
14^M
[160549.979018] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
15^M
[160549.979144] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
16^M
[160549.979269] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
17^M
[160549.979393] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
18^M
[160549.979517] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
19^M
[160549.979642] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
20^M
[160549.979768] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
21^M
[160549.979892] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
22^M
[160549.980016] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
23^M
[160549.980142] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
24^M
[160549.980266] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
25^M
[160549.980391] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
26^M
[160549.980516] ehci_hcd :00:1d.0: detected XactErr len 0/4096 retry
27^M


Regards,
Shaiju.


-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Sunday, July 29, 2012 2:54 PM
To: shaiju shaiju
Cc: 'Sadasivan Shaiju'; 'Peter Chen'; 'USB list'
Subject: RE: usb device getting disconnected and connect back again.

On Sun, 29 Jul 2012, shaiju shaiju wrote:

> Hi  Alen,
>
> This  error  is  intermittent  .  It  doesn't  happen  always .

Then there may not be any way to determine the cause.  Perhaps the
firmware in the USB device intermittently crashes.

Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html