linux-kernel - Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups]

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0910191048000.7710@p34.internal.lan>
Date:	Mon, 19 Oct 2009 10:55:46 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Alan Stern <stern@...land.harvard.edu>
cc:	USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard
 [DEBUG logs included upsd/upsmon/usbhid-ups]



On Mon, 19 Oct 2009, Alan Stern wrote:

> On Sun, 18 Oct 2009, Justin Piszcz wrote:
>
>> I have performed all of the steps you recommended, there is also a bug in
>> the docs, the directory seems to be different, or at least if you have
>> everything compiled into the kernel and not using modules.
>
>> Steps from the USB documentation:
>>
>> # mount -t debugfs none_debugs /sys/kernel/debug
>> #
>>
>> The kernel documentation is outdated:
>>
>> # ls /sys/kernel/debug/usbmon
>> 0s  0u  1s  1t  1u  2s  2t  2u  3s  3t  3u  4s  4t  4u
>> #
>>
>> The directory is:
>> # ls /sys/kernel/debug/usb/usbmon
>> 0s  0u  1s  1t  1u  2s  2t  2u
>
> This has already been corrected in the 2.6.32-rc kernels.
Great to hear, I will try the latest 2.6.31-rcX kernel!

>
> However there is another respect in which the documentation is
> outdated: It mentions /proc/bus/usb/devices.  That file has moved; it
> is now named /sys/kernel/debug/usb/devices.  Would you like to submit a
> patch fixing this?
>
> Alan Stern
>

Hi,

Sure, what I meant is:

usbmon.txt states:
/sys/kernel/debug/usbmon/3u
             ^^^^^

Actual location:
/sys/kernel/debug/usb/usbmon/3u
             ^^^^^^^^^

Patch below (and attached):

diff -uprN linux-2.6.31.1/Documentation/usb/usbmon.txt linux-2.6.31.1.patch/Documentation/usb/usbmon.txt
--- linux-2.6.31.1/Documentation/usb/usbmon.txt 2009-09-24 11:45:25.000000000 -0400
+++ linux-2.6.31.1.patch/Documentation/usb/usbmon.txt   2009-10-19 10:51:06.725516874 -0400
@@ -33,7 +33,7 @@ if usbmon is built into the kernel.

  Verify that bus sockets are present.

-# ls /sys/kernel/debug/usbmon
+# ls /sys/kernel/debug/usb/usbmon
  0s  0u  1s  1t  1u  2s  2t  2u  3s  3t  3u  4s  4t  4u
  #

@@ -58,11 +58,11 @@ Bus=03 means it's bus 3.

  3. Start 'cat'

-# cat /sys/kernel/debug/usbmon/3u > /tmp/1.mon.out
+# cat /sys/kernel/debug/usb/usbmon/3u > /tmp/1.mon.out

  to listen on a single bus, otherwise, to listen on all buses, type:

-# cat /sys/kernel/debug/usbmon/0u > /tmp/1.mon.out
+# cat /sys/kernel/debug/usb/usbmon/0u > /tmp/1.mon.out

  This process will be reading until killed. Naturally, the output can be
  redirected to a desirable location. This is preferred, because it is going

View attachment "usbmon-documentation-fix.patch" of type "TEXT/x-diff" (1168 bytes)