From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Larry Finger <larry.finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Fix handling of failure to create debugfs directory
Date: Wed, 8 Aug 2007 13:16:37 +0200 [thread overview]
Message-ID: <200708081316.38183.mb@bu3sch.de> (raw)
In-Reply-To: <46B95C75.8060404@lwfinger.net>
On Wednesday 08 August 2007 08:02:29 Larry Finger wrote:
> Larry Finger wrote:
> > Pavel Roskin wrote:
> >> This can happen if CONFIG_BCM43XX_MAC80211_DEBUG is enabled, but
> >> CONFIG_DEBUG_FS is not.
> >>
> >> Signed-off-by: Pavel Roskin <proski@gnu.org>
> >> ---
> >>
> > With this patch installed, and the DEBUG configuration set as above, I get a kernel panic on an
> > x86_64 SMP system. The reason for the panic scrolled off the screen, but the complete stack dump
> > (hand copied) is as follows:
> >
> > lock_acquire+0x85/0x31
> > bcm43xx_mac80211: bcm43xx_debugfs_log_txstat+0x5a/099
> > _spin_lock+0x25/0x31
>
> Ignore the noise above. I had failed to get the right patch. The crash confirms the problem
> _without_ the patch. Getting it in properly fixes the problem
>
> Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
Yeah, I just noticed that, too :)
So, I applied it to my queue and it will soon go upstream.
http://bu3sch.de/patches/wireless-dev/LATEST/patches/
--
Greetings Michael.
next prev parent reply other threads:[~2007-08-08 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 5:17 [PATCH] Fix handling of failure to create debugfs directory Pavel Roskin
2007-08-08 5:52 ` Larry Finger
2007-08-08 6:02 ` Larry Finger
2007-08-08 11:16 ` Michael Buesch [this message]
2007-08-08 10:38 ` Michael Buesch
2007-08-08 9:04 ` Michael Buesch
2007-08-08 12:04 ` Larry Finger
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=200708081316.38183.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@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 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.