All of lore.kernel.org
 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 23:16:10 +0100	[thread overview]
Message-ID: <1180304170.3030.23.camel@cookie.hadess.net> (raw)
In-Reply-To: <1180283308.21432.67.camel@aeonflux.holtmann.net>

On Sun, 2007-05-27 at 18:28 +0200, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > > > 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).
> 
> so this is actually fixed now within the upstream kernel. This also
> means that I didn't really bother about older kernels.

Any plans for a backport? It would be most useful, at least for testing.

> > 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.
> 
> Actually using SIGUSR2 should switch debugging mode on/off, but I think
> we forgot to introduce that within the service implementation. Need to
> fix that at some point.

It would also be useful if the different functions could have debugging
output of their different entry points, after argument parsing.

-- 
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 22:16 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
2007-05-27 16:28               ` Marcel Holtmann
2007-05-27 22:16                 ` Bastien Nocera [this message]
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=1180304170.3030.23.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 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.