onejeremias

I'm new to Linux. Linux had been running all day in the same session, (left the computer on) and when I came back to it, the mouse wasn't working. I rebooted, and that seemed to fix the problem. But then it stopped working again. Another reboot got me 15 to 20 minutes of use before it died again. I checked the system log, and I've posted what I believe to be the relevant info:

Sep 17 21:43:45 localhost atd: atd startup succeeded
Sep 17 21:43:45 localhost xfs: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
Sep 17 21:44:00 localhost gdm(pam_unix)[4906]: session opened for user jeremias by (uid=0)
Sep 17 21:44:01 localhost gconfd (jeremias-4964): starting (version 2.2.0), pid 4964 user 'jeremias'
Sep 17 21:44:01 localhost gconfd (jeremias-4964): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Sep 17 21:44:01 localhost gconfd (jeremias-4964): Resolved address "xml:readwrite:/home/jeremias/.gconf" to a writable config source at position 1
Sep 17 21:44:01 localhost gconfd (jeremias-4964): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Sep 17 22:03:42 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 476
Sep 17 22:03:47 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1396
Sep 17 22:03:53 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 268
Sep 17 22:03:58 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1188
Sep 17 22:04:03 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 60
Sep 17 22:04:08 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 980
Sep 17 22:04:13 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1900
Sep 17 22:04:18 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 772
Sep 17 22:04:23 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1692
Sep 17 22:04:28 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 564
Sep 17 22:04:33 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1484
Sep 17 22:04:38 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 356
Sep 17 22:04:43 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1276
Sep 17 22:04:48 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 148
Sep 17 22:04:53 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1068
Sep 17 22:04:58 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1988
Sep 17 22:05:03 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 860
Sep 17 22:05:08 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1780
Sep 17 22:05:13 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 652
Sep 17 22:05:18 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1572
Sep 17 22:05:23 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 444
Sep 17 22:05:28 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1364
Sep 17 22:05:33 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 236
Sep 17 22:05:38 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1156
Sep 17 22:05:43 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 28
Sep 17 22:05:48 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 948
Sep 17 22:05:53 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1868
Sep 17 22:05:58 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 740
Sep 17 22:06:03 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1660
Sep 17 22:06:08 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 532
Sep 17 22:06:13 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1452
Sep 17 22:06:18 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 324
Sep 17 22:06:23 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1244
Sep 17 22:06:24 localhost modprobe: modprobe: Can't locate module sound-slot-0
Sep 17 22:06:24 localhost modprobe: modprobe: Can't locate module sound-service-0-3
Sep 17 22:06:28 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 116
Sep 17 22:06:28 localhost shutdown: shutting down for system reboot

The system was working fine, then I got all those interrupts. Can anyone tell me how to fix this problem, or if I'm even on the right track? Thanks in advance for any help.

-onejeremias

onejeremias

Did I say something wrong? Or is there actually no one that can help me with this problem?

Cabhan

Hrm. Indeed, this seems to be an unfortunate problem.

One suggestion seems to be removing the USB module and reloading it. Run these commands from a terminal, as root:
Since your mouse won't be working, you can press Ctrl-Alt-F1 to get access to a console. Ctrl-Alt-F7 returns you to X.

It has also been suggested that changing the USB module in your kernel will help. I don't know if you're comfortable working with the kernel, but if you are, you might try that.

Finally, if none of that works, what model of mouse do you have? It is possible that this mouse simply does not work with the kernel, though that would be unfortunate.

__________________
DISTRO=Gentoo
Registered Linux User #388732
Gentoo Linux, 410 GB HD, 1.2 GB RAM, Fluxbox, These are a Few of my Favorite Things

onejeremias

Thanks for responding.

I've been using the mouse through the PS/2 port, and it has been working with no trouble, so I'm assuming the mouse is ok. I haven't tested any other USB devices, but do you think that my entire USB system is down in the OS when this happens? If so, would removing and reloading the module fix the problem for good, or just be temporary until it happened again?

Also, what does it mean to change the USB module? And what would I need to do to modify the kernel?

Thanks for your help in this. I am becoming an avid Linux user day by day.

-onejeremias

mystery99

OMG I KNOW HOW TO FIX GO PUT WINDOWS XP OR VISTA GO UPDATE UR BIOS srry caps lock was on and to lazy to restart, ok so update your bios to latest it works i did it i spent days putting these stupid codes in terminal and trying new linux it doesnt work just as easy as updating ur bios IT WORKS

MikeTbob

This thread is over 2 years old and probably that is not a fix for Linux either, thread closed.

__________________
I do not respond to private messages asking for help.
Please keep it on the forums only.