From: Josh Stone <jistone@redhat.com>
To: Chris Dunlop <chris@onthe.net.au>
Cc: systemtap@sourceware.org
Subject: Re: Error removing module: Device or resource busy
Date: Sat, 21 Jan 2012 01:18:00 -0000 [thread overview]
Message-ID: <4F1A1244.3010908@redhat.com> (raw)
In-Reply-To: <20111228080728.GA12001@onthe.net.au>
Hi Chris -- Sorry for my delayed reply, this fell to the back of my head
over the holidays and travel afterward.
On 12/28/2011 12:07 AM, Chris Dunlop wrote:
> On Mon, Dec 26, 2011 at 10:33:26AM -0800, Josh Stone wrote:
>> If only stap was working, so we could write some scripts to track down
>> why stap isn't working... :/
>
> :/
>
> ... on the other hand, it seems to be working up to the point of unloading. So perhaps?
If you're still having this issue, and willing to work on it, then I'll
whip up a script around module activity.
And if you can share your .config and which kernel tag you're building
from now, I'll try to reproduce the issue in one of my test VMs. I
guess you're probably building with some debian patches, but I'll want
to try a vanilla kernel first.
Josh
next prev parent reply other threads:[~2012-01-21 1:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 8:21 Chris Dunlop
2011-12-23 21:10 ` Josh Stone
2011-12-26 18:33 ` Chris Dunlop
2011-12-27 22:06 ` Josh Stone
2011-12-28 17:08 ` Chris Dunlop
2012-01-21 1:18 ` Josh Stone [this message]
2012-01-21 1:36 ` Chris Dunlop
2012-01-21 2:30 ` Chris Dunlop
2012-01-21 7:27 ` Josh Stone
2012-01-23 7:25 ` Chris Dunlop
2012-01-25 12:31 ` Frank Ch. Eigler
2012-01-26 0:30 ` Chris Dunlop
2012-01-26 1:34 ` Josh Stone
2012-01-26 2:28 ` Chris Dunlop
2012-01-26 18:47 ` Josh Stone
2012-01-26 23:32 ` Chris Dunlop
2012-01-21 1:40 ` Chris Dunlop
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=4F1A1244.3010908@redhat.com \
--to=jistone@redhat.com \
--cc=chris@onthe.net.au \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).