mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Jeremy Roberson <jroberson@gtcocalcomp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.18-rc6
Date: Tue, 5 Sep 2006 17:04:41 +0100	[thread overview]
Message-ID: <200609051704.41576.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200609042017.03515.gene.heskett@verizon.net>

On Tuesday 05 September 2006 01:17, Gene Heskett wrote:
> On Monday 04 September 2006 18:31, Steffen Klassert wrote:
> >On Mon, Sep 04, 2006 at 07:05:53AM -0400, Gene Heskett wrote:
> >> On Sunday 03 September 2006 22:42, Linus Torvalds wrote:
> >> >Things are definitely calming down, and while I'm not ready to call it
> >> > a final 2.6.18 yet, this migt be the last -rc.
> >>
> >> It has one new build warning, no idea if show stopper or not:
> >> ----------
> >> drivers/usb/input/hid-core.c:1447:1: warning: "USB_DEVICE_ID_GTCO_404"
> >> redefined
> >> drivers/usb/input/hid-core.c:1446:1: warning: this is the location of
> >> the previous definition
> >> ----------
> >> until after I boot to it...
> >>
> >> And that didn't seem to effect the mouse.  Other usb stuff has not been
> >> exersized yet.
> >
> >The offending patch is
> >hid-core.c: Adds all GTCO CalComp Digitizers and InterWrite School
> > Products to blacklist
[snip]
> Sep  3 19:27:17 coyote kernel: usb 3-2.1: reset low speed USB device using
> ohci_hcd and address 3
> Sep  3 19:35:45 coyote kernel: usb 3-2.1: reset low speed USB device using
> ohci_hcd and address 3

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.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-09-05 16:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04  2:42 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 [this message]
2006-09-05 20:02         ` Gene Heskett
2006-09-22  9:10         ` Konstantin Kletschke
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
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=200609051704.41576.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=gene.heskett@verizon.net \
    --cc=jroberson@gtcocalcomp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®