From: "J.R. Mauro" <jrm8005@gmail.com>
To: Jon Grant <jg@jguk.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: USB disconnect, address 6
Date: Mon, 6 Apr 2009 16:08:50 -0400 [thread overview]
Message-ID: <3aaafc130904061308oc8a40bfwefe7199cfb9369aa@mail.gmail.com> (raw)
In-Reply-To: <19ac3f7a0904061233i7a889cebr86a73fe02cb34421@mail.gmail.com>
On Mon, Apr 6, 2009 at 3:33 PM, Jon Grant <jg@jguk.org> wrote:
> Hi
>
> 2009/4/6 Greg KH <greg@kroah.com>:
>> On Mon, Apr 06, 2009 at 11:11:55AM +0200, Jon Grant wrote:
> [..]
>>> The idea was that the disconnect could give more information.
>>> Otherwise it's necessary to go hunting back up the log to track down
>>> which USB device was the one disconnected (which works fine, but isn't
>>> ideal for time consumed doing this regularly).
>>
>> As you yanked the device out, don't you know which one it was?
>
> I do get devices disappear without me disconnecting them, various
> different PCs, and laptops.
>
> [..]
>>> Apr 5 18:56:58 data-laptop kernel: usb 5-1: USB disconnect, address 6
>>> (Samsung Mighty Drive)
>>>
>>> Would this not be clearer?
>>
>> That might be nice, but note that the kernel doesn't even know the
>> strings after a device is gone, as it had to read them from the device
>> :)
>
> Yeah, would need to cache the names, perhaps you don't want to bloat
> the kernel that way.
>
>> Also, lots of devices don't have strings describing them, and some of
>> them are just flat out wrong. And, if you have multiple devices of the
>> same type, it wouldn't really help out any either.
>
> Well personally I would rather at least know the class of the device
> which went, and would put up with incorrect info in preference to no
> info.
You could perhaps write a script that could look through the logs and
infer which device it was without touching the kernel at all.
>
>> So it would be a bit difficult to do this, sorry.
>
> Thanks anyway for considering it.
>
> Best regards, Jon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-04-06 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 18:04 USB disconnect, address 6 Jon Grant
2009-04-06 2:23 ` Greg KH
2009-04-06 9:11 ` Jon Grant
2009-04-06 15:04 ` Greg KH
2009-04-06 19:33 ` Jon Grant
2009-04-06 20:08 ` J.R. Mauro [this message]
2009-04-07 15:11 ` Stefan Richter
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=3aaafc130904061308oc8a40bfwefe7199cfb9369aa@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=greg@kroah.com \
--cc=jg@jguk.org \
--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