From: Bastien Nocera <hadess@hadess.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Soft lockup
Date: Sun, 27 May 2007 12:30:56 +0100 [thread overview]
Message-ID: <1180265456.3030.9.camel@cookie.hadess.net> (raw)
In-Reply-To: <1141188501.29216.1.camel@localhost>
On Wed, 2006-03-01 at 05:48 +0100, Marcel Holtmann wrote:
> Hi Ville,
>
> > Now I have more information about this problem.
> >
> > I had debuggin enabled in net/bluetooth/rfcomm/core.c and I noticed that
> > for some reson rfcomm_dlc_clear_timer() is called for allready freed
> > dlc and lock_timer_base() gets stuck because it's trying to use invalid
> > timer pointer. I also tried to reproduce bug in i386 without success.
> > Also then debugging is on the bug much harder to reproduse. To me this
> > looks like dlc locking doens't work as it should work.
> >
> > And other notice. rfcomm_dlc_clear_timeri() uses timer_pending()
> > together with del_timer() which allready calls timer_pending(). So
> > timer_pending() is useless in rfcomm_dlc_clear_timer().
>
> this all looks like we are missing a memory barrier somewhere. This
> could also be the reason why it only gets triggered on OMAP systems. Any
> further ideas?
I'm getting the same kind of trace (on both x86-64 and i386) when
testing the gnome-vfs2-obexftp package with a patch to use the new
serial service[1].
It happens on 2.6.19-1.2895.fc6 (x86-64) and 2.6.21-1.3191.fc7 (i386).
Here's what I could capture from the i386 crash:
BUG warning at lib/kref.c:32/kref_get()
kref_get
kobject_get
get_device
device_move
rfcomm_tty_close
release_dev
rfcomm_dlc_send
rfcomm_tty_write
file_has_perm
tty_release
__fput
filp_close
sys_close
syscall_call
wext_handle_ioctl
BUG unable to handle kernel paging request at virtual address ffffffff
rfcomm_dlc_send
rfcomm_dlc_write
file_has_perm
tty_release
__fput
filp_close
sys_close
syscall_call
wext_handle_ioctl
BUG unable to handle kernel paging request at virtual address ffffffff
last sysfs file: /class/tty/rfcomm0/dev
[... Memory corruption dump]
The ffffffff address is the one in the actual oops.
[1]: Package at:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231005
--
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
next prev parent reply other threads:[~2007-05-27 11:30 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 [this message]
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
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=1180265456.3030.9.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.