From: Michael Buesch <mb@bu3sch.de>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
bcm43xx-dev@lists.berlios.de,
Christian Hoffmann <email@christianhoffmann.info>,
linux-wireless@vger.kernel.org
Subject: Re: b43 with upstream-davem stacktrace
Date: Mon, 15 Oct 2007 14:56:16 +0200 [thread overview]
Message-ID: <200710151456.16459.mb@bu3sch.de> (raw)
In-Reply-To: <1192439126.5684.13.camel@localhost.localdomain>
On Monday 15 October 2007 11:05:26 Richard Purdie wrote:
> On Sun, 2007-10-14 at 11:42 +0200, Johannes Berg wrote:
> > On Sat, 2007-10-13 at 17:26 +0200, Michael Buesch wrote:
> >
> > > I also saw this sometimes, but I have absolutely no idea how that happens.
> > > Someone any idea?
> >
> > Nope, but adding more CCs :) I briefly looked at the code and couldn't
> > track it. Got a powerpc oops with disassembly?
>
> It appears to be having a problem in the strcmp in
> led_trigger_set_default() which is odd. Code above that checks if one of
> the options is NULL so all I can think it either the default_trigger
> string being passed in is invalid or there is a trigger with an invalid
> name registered with the system.
>
> Is this an SMP system and would something else be registering an LED
> trigger on another processor or similar? There is locking there which
> should be sufficient though. So no, I'm not sure whats going on
> either...
>
I think this is some kind of a race, as it does only happen rarely and
is not really reproducible.
--
Greetings Michael.
next prev parent reply other threads:[~2007-10-15 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710131823.33420.email@christianhoffmann.info>
2007-10-13 15:26 ` b43 with upstream-davem stacktrace Michael Buesch
2007-10-14 9:42 ` Johannes Berg
2007-10-15 9:05 ` Richard Purdie
2007-10-15 12:56 ` Michael Buesch [this message]
2007-10-15 19:30 ` Christian Hoffmann
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=200710151456.16459.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=email@christianhoffmann.info \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rpurdie@openedhand.com \
/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).