On Wed, 7 Jul 2004, Gene Heskett wrote:
> Got that back up to 1600x1200x24 bits, and was reading the mail
> (darned near 4 megs of it) about 30 mins ago when it did it again.
> The leds in the mouse go completely out, and the pointer is
> frozen in place.
>
> There is no guarantee that the usb mouse is even plugged into the
> same usb port as it was before it was all torn down last night.
> And no guarantee that it isn't, its on of the two back of the mobo
> ports on this board
>
> In any event, here is the revelant piece of the /var/log/messages
> file covering the loss of the mouse.
>
> Jul 7 15:51:58 coyote kernel: usb 1-1: USB disconnect, address 2
> Jul 7 15:51:58 coyote kernel: Unable to handle kernel NULL pointer dereference at
> virtual
> address 0000002c
> Jul 7 15:51:58 coyote kernel: printing eip:
> Jul 7 15:51:58 coyote kernel: c0274290
> Jul 7 15:51:58 coyote kernel: *pde = 00000000
> Jul 7 15:51:58 coyote kernel: Oops: 0000 [#1]
> Jul 7 15:51:58 coyote kernel: PREEMPT
> Jul 7 15:51:58 coyote kernel: Modules linked in: st snd_seq_oss snd_seq_midi_event
> snd_se
> q snd_pcm_oss snd_mixer_oss snd_via82xx snd_ac97_codec snd_pcm snd_timer
> snd_page_alloc sn
> d_mpu401_uart snd_rawmidi snd_seq_device snd eth1394 ohci1394 ieee1394 sg
> Jul 7 15:51:58 coyote kernel: CPU: 0
> Jul 7 15:51:58 coyote kernel: EIP: 0060:[<c0274290>] Not tainted VLI
> Jul 7 15:51:58 coyote kernel: EFLAGS: 00010246 (2.6.7-mm6)
> Jul 7 15:51:58 coyote kernel: EIP is at usb_unlink_urb+0x0/0x40
> Jul 7 15:51:58 coyote kernel: eax: 00000000 ebx: dff82000 ecx: dfc0b26c edx:
> c15c57
> e8
> Jul 7 15:51:58 coyote kernel: esi: c03a2540 edi: dffd4c00 ebp: dffd87c0 esp:
> c1542e
> b0
> Jul 7 15:51:58 coyote kernel: ds: 007b es: 007b ss: 0068
> Jul 7 15:51:58 coyote kernel: Process khubd (pid: 23, threadinfo=c1542000
> task=c15696d0)
> Jul 7 15:51:58 coyote kernel: Stack: c0284dbc dffddc80 c026ed0e dffddc94 c03a2560
> c0207fa
> 6 dffddc94 dffd4cc4
> Jul 7 15:51:58 coyote kernel: c02081d2 dffddc94 dffd4cc4 c02071ba 00000001
> dffddc8
> 0 c02753ff dffd4e00
> Jul 7 15:51:58 coyote kernel: 00000010 dffd4c00 c0270ed8 c032c520 c03122da
> dffd4d1
> c 00000002 00000003
> Jul 7 15:51:58 coyote kernel: Call Trace:
> Jul 7 15:51:58 coyote kernel: [<c0284dbc>] hid_disconnect+0x2c/0xa0
> Jul 7 15:51:58 coyote kernel: [<c026ed0e>] usb_unbind_interface+0x6e/0x70
> Jul 7 15:51:58 coyote kernel: [<c0207fa6>] device_release_driver+0x56/0x60
For a temporary fix of the oops, apply this patch. It won't affect
whatever is causing your mouse to die, however. That might be a hardware
problem: faulty leads in the USB cable not making proper contact, so the
mouse doesn't receive any power.
Alan Stern
===== drivers/usb/core/urb.c 1.44 vs edited =====
--- 1.44/drivers/usb/core/urb.c Thu Jun 24 12:44:16 2004
+++ edited/drivers/usb/core/urb.c Tue Jul 6 16:01:47 2004
@@ -447,6 +447,8 @@
*/
int usb_unlink_urb(struct urb *urb)
{
+ if (!urb)
+ return -EINVAL;
if (!(urb->transfer_flags & URB_ASYNC_UNLINK)) {
usb_kill_urb(urb);
return 0;
@@ -477,6 +479,8 @@
*/
void usb_kill_urb(struct urb *urb)
{
+ if (!urb)
+ return;
if (!(urb->dev && urb->dev->bus && urb->dev->bus->op))
return;
spin_lock_irq(&urb->lock);
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
