From: Larry Finger <larry.finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
wireless <linux-wireless@vger.kernel.org>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: Lock problem with latest b43 patches
Date: Mon, 20 Aug 2007 12:48:38 -0500 [thread overview]
Message-ID: <46C9D3F6.7020306@lwfinger.net> (raw)
In-Reply-To: <1187609202.6090.93.camel@johannes.berg>
Johannes Berg wrote:
> On Sat, 2007-08-18 at 23:45 -0500, Larry Finger wrote:
>
>> -> #1 (&inode->i_mutex){--..}:
>> [<ffffffff80252d52>] __lock_acquire+0xad4/0xcf0
>> [<ffffffff803fe515>] mutex_lock+0x2a/0x2e
>> [<ffffffff80252ff3>] lock_acquire+0x85/0xa9
>> [<ffffffff803fe515>] mutex_lock+0x2a/0x2e
>> [<ffffffff803fe34a>] __mutex_lock_slowpath+0xef/0x290
>> [<ffffffff803fe515>] mutex_lock+0x2a/0x2e
>> [<ffffffff88600d7d>] nfs_revalidate_mapping+0x6d/0xac [nfs]
>> [<ffffffff885fe7e1>] nfs_file_mmap+0x4d/0x65 [nfs]
>
> Are you running on NFS? This is a bit weird but not related to wireless
> at all, seems to be dnotify/NFS interaction.
My / and /home partitions are local, but I do have mounted NFS partitions. Whatever happened here
has been a one-time only event, at least so far. Until it happens again, I'll assume that an
electron got crosswise somewhere. :)
Larry
next prev parent reply other threads:[~2007-08-20 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 4:45 Lock problem with latest b43 patches Larry Finger
2007-08-19 12:16 ` Michael Buesch
2007-08-19 16:07 ` Larry Finger
2007-08-20 11:26 ` Johannes Berg
2007-08-20 17:48 ` Larry Finger [this message]
2007-08-21 18:58 ` Johannes Berg
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=46C9D3F6.7020306@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.