From: Chuck Ebbert <cebbert@redhat.com>
To: Pierre-Yves Paulus <py@idlum.be>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [Bluez-devel] Warnings and Oops on 2.6.23-rc6 while activily using rfcomm links (mm/slab.c)
Date: Tue, 25 Sep 2007 14:26:05 -0400 [thread overview]
Message-ID: <46F952BD.4010009@redhat.com> (raw)
In-Reply-To: <46F92364.3080603@idlum.be>
On 09/25/2007 11:04 AM, Pierre-Yves Paulus wrote:
> Hello,
>
> Putting the bluetooth system under load (opening and closing several
> rfcomm links off several USB adapters, and transmitting data over them),
> I got the Oops below. The computer hung completely, as you can see. Just
> before, I also got those warnings.
>
> I'm not sure if I'm providing the right and useful informations to allow
> fixing of those problems, as I'm definitely no expert. Please tell me if
> I do something the wrong way.
>
>
Please use CONFIG_SLUB and turn on SLUB debugging. Something is very wrong
somewhere...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert@redhat.com>
To: Pierre-Yves Paulus <py@idlum.be>
Cc: linux-kernel@vger.kernel.org,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: Warnings and Oops on 2.6.23-rc6 while activily using rfcomm links (mm/slab.c)
Date: Tue, 25 Sep 2007 14:26:05 -0400 [thread overview]
Message-ID: <46F952BD.4010009@redhat.com> (raw)
In-Reply-To: <46F92364.3080603@idlum.be>
On 09/25/2007 11:04 AM, Pierre-Yves Paulus wrote:
> Hello,
>
> Putting the bluetooth system under load (opening and closing several
> rfcomm links off several USB adapters, and transmitting data over them),
> I got the Oops below. The computer hung completely, as you can see. Just
> before, I also got those warnings.
>
> I'm not sure if I'm providing the right and useful informations to allow
> fixing of those problems, as I'm definitely no expert. Please tell me if
> I do something the wrong way.
>
>
Please use CONFIG_SLUB and turn on SLUB debugging. Something is very wrong
somewhere...
next prev parent reply other threads:[~2007-09-25 18:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 15:04 [Bluez-devel] Warnings and Oops on 2.6.23-rc6 while activily using rfcomm links (mm/slab.c) Pierre-Yves Paulus
2007-09-25 15:04 ` Pierre-Yves Paulus
2007-09-25 15:32 ` [Bluez-devel] " Cornelia Huck
2007-09-25 15:32 ` Cornelia Huck
2007-09-25 18:26 ` Chuck Ebbert [this message]
2007-09-25 18:26 ` Chuck Ebbert
2007-09-26 13:27 ` [Bluez-devel] " Pierre-Yves Paulus
2007-09-26 13:27 ` Pierre-Yves Paulus
2007-09-27 6:56 ` [Bluez-devel] " Cornelia Huck
2007-09-27 6:56 ` Cornelia Huck
2007-09-27 14:43 ` [Bluez-devel] " Pierre-Yves Paulus
2007-09-27 14:43 ` Pierre-Yves Paulus
2007-09-27 18:07 ` [Bluez-devel] " Pierre-Yves Paulus
2007-09-27 18:07 ` Pierre-Yves Paulus
2007-09-28 6:54 ` [Bluez-devel] " Cornelia Huck
2007-09-28 6:54 ` Cornelia Huck
2007-09-28 14:38 ` [Bluez-devel] " Pierre-Yves Paulus
2007-09-28 14:38 ` Pierre-Yves Paulus
2007-09-28 14:57 ` [Bluez-devel] " Pierre-Yves Paulus
2007-09-28 14:57 ` Pierre-Yves Paulus
2007-09-28 16:32 ` Pierre-Yves Paulus
2007-10-01 12:32 ` Cornelia Huck
2007-11-06 2:46 ` Dave Young
2007-09-26 22:16 ` [Bluez-devel] " Marcel Holtmann
2007-09-26 22:16 ` Marcel Holtmann
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=46F952BD.4010009@redhat.com \
--to=cebbert@redhat.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=py@idlum.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.