| View previous topic :: View next topic |
| Author |
Message |
catalYst
Tux's lil' helper
Joined: 02 May 2002
Posts: 119
Location: Appleton, WI USA
|
 Posted: Sun Jun 20, 2004 8:03 am Post subject: USB Detected, but no power |
 |
|
Alright, as all my posts begin: I've scoured the forums, but can't find a solution to this problem.
I have a mobo with the VIA Apollo Pro 133 chipset with the 2.6.5 kernel. In the dmesg everything looks fine; it finds my the USB hub on the motherboard with no issues, but no devices get detected when they're plugged in. That is, about four hours ago I could plug a device in, and, whether it worked or not, I could do a little 'cat /proc/bus/usb/devices' and see it there. Now, I'm not sure what changed over the last four hours, certainly nothing dramatic, but when something is plugged in it does not show up on the bus. I've tried webcams, joysticks and even a generic little four port usb hub but to no avail. I assume there is a reason this is happening . . . but what?
- colin |
|
| Back to top |
|
 |
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
| Posted: Sun Jun 20, 2004 8:18 am Post subject: |
|
|
does anything show up at the end of "dmesg" when you plug/unplug devices?
_________________
http://dev.gentoo.org/~dsd |
|
| Back to top |
|
|
catalYst
Tux's lil' helper
Joined: 02 May 2002
Posts: 119
Location: Appleton, WI USA
|
| Posted: Sun Jun 20, 2004 9:08 am Post subject: |
|
|
no, actually I'm going to admit something that will make me look like a right moron, but I hadn't checked all of dmesg's output. I was simply doing a dmesg | grep USB to see the bus detection.
As I look at the bottom of my dmesg, something is certainly not right:
| Code: | . . .
journal-1206: Starting replay from offset 3026, trans_id 19124
journal-1299: Setting newest_mount_id to 26
Using r5 hash to sort names
Debug: sleeping function called from invalid context at mm/slab.c:1931
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011668c>] __might_sleep+0xac/0xe0
[<c0138dbd>] kmem_cache_alloc+0x6d/0x70
[<c0147bf5>] __get_vm_area+0x25/0x100
[<c0147d03>] get_vm_area+0x33/0x40
[<c01138bd>] __ioremap+0xbd/0x120
[<c0135481>] buffered_rmqueue+0xf1/0x1d0
[<c011394c>] ioremap_nocache+0x2c/0xc0
[<f0be7444>] os_map_kernel_space+0x68/0x6c [nvidia]
[<f0bf9a37>] __nvsym00568+0x1f/0x2c [nvidia]
[<f0bfbb56>] __nvsym00775+0x6e/0xe0 [nvidia]
[<f0bfbbe6>] __nvsym00781+0x1e/0x190 [nvidia]
[<c015bede>] link_path_walk+0x62e/0x950
[<f0bfd66c>] rm_init_adapter+0xc/0x10 [nvidia]
[<f0be3ed7>] nv_kern_open+0xf3/0x228 [nvidia]
[<f0be3de4>] nv_kern_open+0x0/0x228 [nvidia]
[<c0156e50>] chrdev_open+0xb0/0x1d0
[<c014cab0>] dentry_open+0x120/0x180
[<c014c988>] filp_open+0x68/0x70
[<c014cd9b>] sys_open+0x5b/0x90
[<c01070db>] syscall_call+0x7/0xb
Debug: sleeping function called from invalid context at mm/slab.c:1931
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011668c>] __might_sleep+0xac/0xe0
[<c0138dbd>] kmem_cache_alloc+0x6d/0x70
[<c0147bf5>] __get_vm_area+0x25/0x100
[<c0147d03>] get_vm_area+0x33/0x40
[<c01138bd>] __ioremap+0xbd/0x120
[<c0135481>] buffered_rmqueue+0xf1/0x1d0
[<c011394c>] ioremap_nocache+0x2c/0xc0
[<f0be7444>] os_map_kernel_space+0x68/0x6c [nvidia]
[<f0bf9a37>] __nvsym00568+0x1f/0x2c [nvidia]
[<f0bfbb56>] __nvsym00775+0x6e/0xe0 [nvidia]
[<f0bfbbe6>] __nvsym00781+0x1e/0x190 [nvidia]
[<c015bede>] link_path_walk+0x62e/0x950
[<f0bfd66c>] rm_init_adapter+0xc/0x10 [nvidia]
[<f0be3ed7>] nv_kern_open+0xf3/0x228 [nvidia]
[<f0be3de4>] nv_kern_open+0x0/0x228 [nvidia]
[<c0156e50>] chrdev_open+0xb0/0x1d0
[<c014cab0>] dentry_open+0x120/0x180
[<c014c988>] filp_open+0x68/0x70
[<c014cd9b>] sys_open+0x5b/0x90
[<c01070db>] syscall_call+0x7/0xb
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
drivers/input/joystick/sidewinder.c: Init 0: Opened pci0000:00:0b.1/gameport0, io 0xe000, speed 1325
sidewinder.c: Read 0 triplets. []
drivers/input/joystick/sidewinder.c: Init 1: Mode 1. Length 0.
sidewinder.c: Read 0 triplets. []
drivers/input/joystick/sidewinder.c: Init 1b: Length 0.
Debug: sleeping function called from invalid context at mm/slab.c:1931
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011668c>] __might_sleep+0xac/0xe0
[<c0138dbd>] kmem_cache_alloc+0x6d/0x70
[<c0147bf5>] __get_vm_area+0x25/0x100
[<c0147d03>] get_vm_area+0x33/0x40
[<c01138bd>] __ioremap+0xbd/0x120
[<c0135481>] buffered_rmqueue+0xf1/0x1d0
[<c011394c>] ioremap_nocache+0x2c/0xc0
[<f0be7444>] os_map_kernel_space+0x68/0x6c [nvidia]
[<f0bf9a37>] __nvsym00568+0x1f/0x2c [nvidia]
[<f0bfbb56>] __nvsym00775+0x6e/0xe0 [nvidia]
[<f0bfbbe6>] __nvsym00781+0x1e/0x190 [nvidia]
[<c015bede>] link_path_walk+0x62e/0x950
[<f0bfd66c>] rm_init_adapter+0xc/0x10 [nvidia]
[<f0be3ed7>] nv_kern_open+0xf3/0x228 [nvidia]
[<f0be3de4>] nv_kern_open+0x0/0x228 [nvidia]
[<c0156e50>] chrdev_open+0xb0/0x1d0
[<c014cab0>] dentry_open+0x120/0x180
[<c014c988>] filp_open+0x68/0x70
[<c014cd9b>] sys_open+0x5b/0x90
[<c01070db>] syscall_call+0x7/0xb
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
|
This might go beyond a USB problem . . . though I still don't know what to do. By the way, thanks for the prompt reply. |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
| Posted: Sun Jun 20, 2004 1:59 pm Post subject: |
|
|
doesnt look good. which kernel are you running?
_________________
http://dev.gentoo.org/~dsd |
|
| Back to top |
|
|
catalYst
Tux's lil' helper
Joined: 02 May 2002
Posts: 119
Location: Appleton, WI USA
|
| Posted: Sun Jun 20, 2004 5:48 pm Post subject: |
|
|
| Currently I have the gentoo-dev-sources-2.6.5 kernel. |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
|
| Back to top |
|
|
catalYst
Tux's lil' helper
Joined: 02 May 2002
Posts: 119
Location: Appleton, WI USA
|
| Posted: Sun Jun 20, 2004 6:46 pm Post subject: |
|
|
| That elimnates all the dmesg garbage, but 'cat /proc/bus/usb/devices' still doesn't turn up any devices other than the root hub. That, and the 4-port usb hub I have plugged in doesn't recieve any power (the lights aren't on). crap. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
