From: Chris Dunlop <chris@onthe.net.au>
To: Josh Stone <jistone@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Error removing module: Device or resource busy
Date: Sat, 21 Jan 2012 02:30:00 -0000 [thread overview]
Message-ID: <20120121023012.GA8844@onthe.net.au> (raw)
In-Reply-To: <20120121013535.GA8165@onthe.net.au>
On Sat, Jan 21, 2012 at 12:35:35PM +1100, Chris Dunlop wrote:
> I'm building from vanilla linux-3.1.10 (9bb1282), .config below.
Oh, this is probably worth mentioning: whilst the problem is
occuring on debian wheezy/sid, both the kernel and systemtap are
being built on a different machine running Ubuntu 10.04.
Chris
next prev parent reply other threads:[~2012-01-21 2:30 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
2012-01-21 1:36 ` Chris Dunlop
2012-01-21 2:30 ` Chris Dunlop [this message]
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=20120121023012.GA8844@onthe.net.au \
--to=chris@onthe.net.au \
--cc=jistone@redhat.com \
--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).