From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups]
Date: Mon, 19 Oct 2009 10:55:46 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0910191048000.7710@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0910191016370.3899-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2215 bytes --]
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
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/x-diff; name=usbmon-documentation-fix.patch, Size: 1168 bytes --]
Binary files linux-2.6.31.1/Documentation/.SubmittingPatches.swp and linux-2.6.31.1.patch/Documentation/.SubmittingPatches.swp differ
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
next prev parent reply other threads:[~2009-10-19 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 21:55 USB/UPS connectivity issue on Intel DP55KG Motherboard Justin Piszcz
2009-10-13 23:56 ` Justin Piszcz
2009-10-14 0:33 ` Robert Hancock
2009-10-14 7:59 ` Justin Piszcz
2009-10-14 13:25 ` [Nut-upsuser] USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups] Justin Piszcz
[not found] ` <alpine.DEB.2.00.0910140926560.19307@p34.internal.lan>
2009-10-18 20:23 ` 2.6.31.4: " Justin Piszcz
2009-10-18 20:42 ` Alan Stern
2009-10-18 21:40 ` Justin Piszcz
2009-10-19 14:23 ` Alan Stern
2009-10-19 14:55 ` Justin Piszcz [this message]
2009-10-19 15:12 ` Justin Piszcz
2009-10-19 15:13 ` Alan Stern
2009-10-19 15:08 ` Alan Stern
2009-10-19 15:14 ` Justin Piszcz
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=alpine.DEB.2.00.0910191048000.7710@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®