public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.18-rc6
Date: Fri, 22 Sep 2006 11:10:50 +0200	[thread overview]
Message-ID: <20060922091049.GA5218@anita.doom> (raw)
In-Reply-To: <200609051704.41576.s0348365@sms.ed.ac.uk>

Am 2006-09-05 17:04 +0100 schrieb Alistair John Strachan:

> Might not be a kernel problem, userspace might be using libusb and calling 
> usb_reset() on the device. Try dropping out of X11 and see if it still 
> happens.


I have this with 18_rc6 and 18_rc7 also:

Sep 22 11:01:50 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3
Sep 22 11:03:17 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3
Sep 22 11:04:04 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3
Sep 22 11:04:52 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3
Sep 22 11:05:46 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3
Sep 22 11:06:30 anita usb 1-3: reset low speed USB device using ohci_hcd
and address 3

In older Kernels or even 2.6.17 I never saw this.
So may be the initial report was barking at the wrong tree, this is a
plugged wired USB keyboard (daskeyboard.com).
The Keyboard is fully functional while typing on it and this happens
without being in X. It happens with nobody logged in local, the messages
are logged even only when logged in via ssh.

libusb and usbutils are not installed on this machine (should they?).

T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#=  3 Spd=1.5 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046a ProdID=0048 Rev= 0.26
S:  Product=Das Keyboard
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms


Regards, Konsti



-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  parent reply	other threads:[~2006-09-22  9:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04  2:42 Linux 2.6.18-rc6 Linus Torvalds
2006-09-04 11:05 ` Gene Heskett
2006-09-04 22:31   ` Steffen Klassert
2006-09-05  0:17     ` Gene Heskett
2006-09-05 16:04       ` Alistair John Strachan
2006-09-05 20:02         ` Gene Heskett
2006-09-22  9:10         ` Konstantin Kletschke [this message]
2006-09-05 12:26 ` Olaf Hering
2006-09-05 12:45   ` maximilian attems
2006-09-05 18:56     ` Greg KH
2006-09-05 19:01       ` maximilian attems
2006-09-05 21:50         ` Greg KH
2006-09-05 21:01   ` James Bottomley
2006-09-05 22:20     ` Benjamin Herrenschmidt
2006-09-05 23:22       ` James Bottomley
2006-09-06  0:47         ` Benjamin Herrenschmidt
2006-09-06 12:09         ` Olaf Hering
2006-09-06 11:01     ` Olaf Hering
2006-09-06 14:04       ` James Bottomley
2006-09-07  9:15         ` Olaf Hering
2006-09-07 14:04           ` James Bottomley
2006-09-16  3:47             ` Doug Ledford
2006-09-16  8:44               ` Olaf Hering
2006-09-17  5:38               ` Olaf Hering
2006-09-17 14:05                 ` James Bottomley
2006-09-17 18:17                   ` Doug Ledford
2006-09-17 18:20                 ` Doug Ledford
  -- strict thread matches above, loose matches on Subject: below --
2006-09-12 15:04 Jody Belka
2006-09-12 22:33 ` Greg KH
2006-09-12 23:11   ` Jody Belka
2006-09-13  0:42     ` Jody Belka

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=20060922091049.GA5218@anita.doom \
    --to=lists@ku-gbr.de \
    --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