linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Soft lockup
Date: Sun, 27 May 2007 15:43:23 +0100	[thread overview]
Message-ID: <1180277003.3030.18.camel@cookie.hadess.net> (raw)
In-Reply-To: <1180268229.21432.63.camel@aeonflux.holtmann.net>

Hey Marcel,

On Sun, 2007-05-27 at 14:17 +0200, Marcel Holtmann wrote:
> > Here's what I could capture from the i386 crash:
> > BUG warning at lib/kref.c:32/kref_get()
> 
> any chance you can test a 2.6.22-rc3 kernel. We fixed some potential
> problems in RFCOMM and Greg pushed some driver model changes that might
> make this go away. I really have no idea what triggers this at the
> moment. However I would like to see a simple reproducer.

Works with 2.6.22-rc3 (for a meaning of works, my code doesn't seem to
work, but that's a different matter).

To reproduce the problem:
- Install gnome-vfs2-obexftp (let me know if you want me to provide
binaries) from
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231005
- Make sure you have bluez-utils 3.11 (for the serial service)
- On the console:
eval `dbus-launch --sh-syntax` # Launches a session D-Bus daemon
/usr/libexec/gnome-vfs-daemon # Launches the gnome-vfs daemon
gnomevfs-ls obex://[00:00:11:22:22:00]/ # Where 00:00:11:22:22:00 is the
bdaddr of a phone, or other device with ObexFTP support

I can reproduce the crash at will on 2 different machines. It might be
easier to create a minimal reproducer if you have a debug version of the
serial service.

-- 
Bastien Nocera <hadess@hadess.net> 


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-27 14:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22  9:12 [Bluez-devel] Soft lockup Ville Tervo
2006-02-22 11:20 ` Marcel Holtmann
2006-02-22 12:54   ` Ville Tervo
2006-02-24 11:03     ` Ville Tervo
2006-03-01  4:48       ` Marcel Holtmann
2007-05-27 11:30         ` Bastien Nocera
2007-05-27 12:17           ` Marcel Holtmann
2007-05-27 14:43             ` Bastien Nocera [this message]
2007-05-27 16:28               ` Marcel Holtmann
2007-05-27 22:16                 ` Bastien Nocera
2007-05-28  8:39                   ` Marcel Holtmann
2007-06-01 14:53                     ` Pierre-Yves Paulus
2007-06-01 15:16                       ` Marcel Holtmann
2007-05-27 22:22               ` Bastien Nocera
2007-05-28  8:40                 ` 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=1180277003.3030.18.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 NNTP newsgroup(s).