From: Russell Neches <russell@ccs.neu.edu>
To: Brad Midgley <bmidgley@xmission.com>, bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] crash on remove
Date: Wed, 10 Mar 2004 21:47:20 -0500 [thread overview]
Message-ID: <20040311024720.GA3297@omocha.vort.org> (raw)
In-Reply-To: <404FB5D1.5030104@xmission.com>
> yes, i enabled force remove because the module shows up as in use. i
> think it's unsafe, but how much worse can it be than crashing the kernel?
Indeed.
> i am compiling the modules without SCO support right now to see if that
> helps.
Now, by SCO support, do we mean the module (CONFIG_BT_SCO) or
CONFIG_BT_HCIUSB_SCO? I'm actually getting the crash without the sco
module loaded, and I have my kernel built with CONFIG_BT_HCIUSB_SCO not
set. I don't think SCO shows up anywhere else in the kernel. Sorry if
I'm beginning to sound pedantic.
Maybe I should figure out how to use SysReq after all...
Russell
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-11 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:21 [Bluez-users] crash on remove Russell Neches
2004-03-10 21:12 ` Brad Midgley
2004-03-10 22:35 ` Russell Neches
2004-03-10 22:46 ` Simone Gotti
2004-03-10 23:41 ` Russell Neches
2004-03-11 0:11 ` Simone Gotti
2004-03-11 0:38 ` Russell Neches
2004-03-11 0:41 ` Brad Midgley
2004-03-11 2:47 ` Russell Neches [this message]
2004-03-11 9:32 ` Matthias Thomae
2004-03-13 15:26 ` Simone Gotti
2004-03-15 13:21 ` [Bluez-devel] " Dirk Husemann
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=20040311024720.GA3297@omocha.vort.org \
--to=russell@ccs.neu.edu \
--cc=bluez-users@lists.sourceforge.net \
--cc=bmidgley@xmission.com \
/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