All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharath Ramesh <krosswindz@gmail.com>
To: "Hodle, Brian" <BHodle@harcroschem.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.12] System becomes unresponsive with USB errors
Date: Thu, 23 Jun 2005 10:44:12 -0400	[thread overview]
Message-ID: <c775eb9b050623074431056898@mail.gmail.com> (raw)
In-Reply-To: <D9A1161581BD7541BC59D143B4A06294021FAA7C@KCDC1>

USB legacy support is already disabled in my BIOS. I still get these
errors in my dmesg.

-Bharath

On 6/23/05, Hodle, Brian <BHodle@harcroschem.com> wrote:
> Bharath,
>    I also have an Athlon 64 workstation, and had the same problem. You need
> to disable legacy USB support in your BIOS.
> 
> -Brian
> 
> -----Original Message-----
> From: Bharath Ramesh [mailto:krosswindz@gmail.com]
> Sent: Wednesday, June 22, 2005 7:21 PM
> To: linux-kernel@vger.kernel.org
> Subject: [2.6.12] System becomes unresponsive with USB errors
> 
> 
> I am running the 2.6.12 kernel on my Athlon64 workstation. I am using
> the Microsoft Wireless Optical Desktop keyboard and mice. Every now
> and then my system becomes unresponsive to the input devices. I can
> still login remotely and my dmesg is full of the following message:
> 
> drivers/usb/input/hid-core.c: input irq status -75 received
> 
> I have filed this bug at bugme.osdl.org the bug number is 4724.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=4724
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2005-06-23 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 13:05 [2.6.12] System becomes unresponsive with USB errors Hodle, Brian
2005-06-23 14:44 ` Bharath Ramesh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-23  0:20 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=c775eb9b050623074431056898@mail.gmail.com \
    --to=krosswindz@gmail.com \
    --cc=BHodle@harcroschem.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.