linux-kernel - Re: Linux 2.6.18-rc6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <200609042017.03515.gene.heskett@verizon.net>
Date:	Mon, 04 Sep 2006 20:17:03 -0400
From:	Gene Heskett <gene.heskett@...izon.net>
To:	Linus Torvalds <torvalds@...l.org>,
	Jeremy Roberson <jroberson@...ocalcomp.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.18-rc6

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
>
>If one looks at this patch it seems to be just a typo.
>The patch below fixes at least the warning.
>
>--- vanilla-2.6.18-rc6/drivers/usb/input/hid-core.c 2006-09-04
> 04:19:48.000000000 +0200 +++
> linux-2.6.18-rc6/drivers/usb/input/hid-core.c 2006-09-04
> 23:53:10.000000000 +0200 @@ -1444,7 +1444,7 @@
> #define USB_DEVICE_ID_GTCO_402  0x0402
> #define USB_DEVICE_ID_GTCO_403  0x0403
> #define USB_DEVICE_ID_GTCO_404  0x0404
>-#define USB_DEVICE_ID_GTCO_404  0x0405
>+#define USB_DEVICE_ID_GTCO_405  0x0405
> #define USB_DEVICE_ID_GTCO_500  0x0500
> #define USB_DEVICE_ID_GTCO_501  0x0501
> #define USB_DEVICE_ID_GTCO_502  0x0502
>@@ -1657,7 +1657,7 @@
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_402, HID_QUIRK_IGNORE },
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_403, HID_QUIRK_IGNORE },
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_404, HID_QUIRK_IGNORE },
>- { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_404, HID_QUIRK_IGNORE },
>+ { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_405, HID_QUIRK_IGNORE },
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_500, HID_QUIRK_IGNORE },
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_501, HID_QUIRK_IGNORE },
>  { USB_VENDOR_ID_GTCO, USB_DEVICE_ID_GTCO_502, HID_QUIRK_IGNORE },
>-

I did apply this patch, with vim as its only 2 characters that are actually 
changed.  But now I'm going to go back and look at the log from before I 
rebooted to this patch.  Yes, since 2.6.18-rc6, I'm getting these in the 
log, and this patch obviously has no effect on the below log entries.
--------------
Sep  3 15:20:10 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 15:33:14 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 15:47:25 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 15:56:45 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 16:08:05 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 16:17:24 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 16:37:13 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 16:48:12 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 17:19:10 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 17:26:16 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 17:36:22 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 17:42:18 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 17:51:46 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 18:03:08 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 18:16:52 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 18:35:08 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 18:43:34 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 18:52:31 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
Sep  3 19:10:15 coyote kernel: usb 3-2.1: reset low speed USB device using 
ohci_hcd and address 3
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
-----------

And they are being logged at times when I am nowhere near the mouse to move 
it, at varying intervals of 2-3 a minute as you can see above.

Is there a way to shut this up?  The mouse is working great, although its 
possible the battery is getting weak.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/