From: Pete Zaitcev <zaitcev@redhat.com>
To: Joseph Carter <knghtbrd@debian.org>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
nicholas@petreley.com, linux-kernel@vger.kernel.org
Subject: Re: usb-uhci.c problems in latest kernels?
Date: Sun, 15 Apr 2001 23:29:09 -0400 [thread overview]
Message-ID: <20010415232909.A28478@devserv.devel.redhat.com> (raw)
In-Reply-To: <20010414213546.A1590@devserv.devel.redhat.com> <20010415043836.C15118@debian.org>
In-Reply-To: <20010415043836.C15118@debian.org>; from knghtbrd@debian.org on Sun, Apr 15, 2001 at 04:38:37AM -0700
> Date: Sun, 15 Apr 2001 04:38:37 -0700
> From: Joseph Carter <knghtbrd@debian.org>
> To: Pete Zaitcev <zaitcev@redhat.com>
> Cc: nicholas@petreley.com, linux-kernel@vger.kernel.org
> > > usb-uhci.c: interrupt, status 3, frame# 1876
> >
> > This is a known problem, here is the discussion that I initiated
> > on linux-usb-devel:
> >
> > http://marc.theaimsgroup.com/?t=98609508500001&w=2&r=1
> >
> > The right fix is to comment that printout out.
> > In fact, that is what I commited for Red Hat 7.1 release.
>
> I'm not sure of that. Sometimes keys get "stuck" in the down position
> with my USB keyboard (mechanical switches, so the keys themselves are not
> sticking) and usually when that happens I can find a line like the one
> quoted above in the logs. [...]
The printout is a valuable diagnostic tool for hacking but
is useless for a user (actually dangerous, as it brings computers
down with /var overflow). The best option would be to have
it configurable with a module parameter.
-- Pete
next prev parent reply other threads:[~2001-04-16 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 1:35 usb-uhci.c problems in latest kernels? Pete Zaitcev
2001-04-15 11:38 ` Joseph Carter
2001-04-16 3:29 ` Pete Zaitcev [this message]
2001-04-16 11:29 ` Joseph Carter
-- strict thread matches above, loose matches on Subject: below --
2001-04-13 20:06 Nicholas Petreley
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=20010415232909.A28478@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=knghtbrd@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicholas@petreley.com \
/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.