From: Marcel Holtmann <marcel@holtmann.org>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: RE: BUG: sleeping function called from invalid context at mm/slub.c:1595 --- "hcitool cc" or "l2ping"
Date: Wed, 29 Apr 2009 07:20:41 -0700 [thread overview]
Message-ID: <1241014841.997.69.camel@localhost.localdomain> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F704301E3F5C7FC@SC-VEXCH1.marvell.com>
Hi Bing,
> > > I'm getting this error whenever I use "hcitool cc" or "l2ping xx:xx:xx:xx:xx:xx"
> > command.
> > >
> > > Kernel: version 2.6.30-rc3 from bluetooth-testing tree
> > > HCI Tool: version 3.20
> > > Laptop: Lenovo X61s
> >
> > can you rebase the bluetooth-testing.git tree from a few hours ago and
> > test again.
>
> "git log" shows the last commit was ad4751fcada51292bb2967748667b582281647d0.
> Bluetooth: Fix errors and warnings in L2CAP reported by checkpatch.pl
>
> Is it the latest one?
yes, that one is the latest. What happens if you revert:
commit d97ebf3798fb5745953230e049011f5b20b7c6d9
Author: Roger Quadros <ext-roger.quadros@nokia.com>
Date: Thu Apr 23 14:50:54 2009 +0300
Bluetooth: Ensure that HCI sysfs add/del is preempt safe
Does this one introduces your problem?
What is your kernel config and hardware you are running this one? Seems
not everybody is seeing this one.
Regards
Marcel
next prev parent reply other threads:[~2009-04-29 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 1:02 BUG: sleeping function called from invalid context at mm/slub.c:1595 --- "hcitool cc" or "l2ping" Bing Zhao
2009-04-29 0:56 ` Marcel Holtmann
2009-04-29 1:14 ` Bing Zhao
2009-04-29 1:47 ` Gustavo F. Padovan
2009-04-29 2:13 ` Bing Zhao
2009-04-29 14:20 ` Marcel Holtmann [this message]
2009-04-29 22:18 ` Bing Zhao
2009-04-29 22:38 ` Marcel Holtmann
2009-04-30 2:55 ` Bing Zhao
2009-04-30 5:43 ` Marcel Holtmann
2009-05-01 0:54 ` Bing Zhao
2009-05-05 18:45 ` Bing Zhao
2009-05-05 19:14 ` 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=1241014841.997.69.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bzhao@marvell.com \
--cc=linux-bluetooth@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