From: Bharath Ramesh <krosswindz@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: USB errors causes system to become unresponsive
Date: Wed, 8 Jun 2005 13:27:42 -0400 [thread overview]
Message-ID: <c775eb9b0506081027d0cc6b9@mail.gmail.com> (raw)
I am running the 2.6 kernel and I notice that every now and then my
system stops responding but is still accessible remotely through ssh.
I can not work on the console. The only way out is to reboot either
remotely or by hitting the reset button. When the system comes up
again I get the following message in my dmesg and I need to actually
reboot it once or twice before this error goes. of I get a spew of
following messages. These messages don't stop till I reboot the
machine.
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
drivers/usb/input/hid-core.c: input irq status -75 received
next reply other threads:[~2005-06-08 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 17:27 Bharath Ramesh [this message]
2005-06-08 17:38 ` USB errors causes system to become unresponsive Duncan Sands
2005-06-08 18:27 ` Bharath Ramesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c775eb9b0506081027d0cc6b9@mail.gmail.com \
--to=krosswindz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox