From: Larry Finger <larry.finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org, Bcm43xx-dev@lists.berlios.de
Subject: Re: A problem with shared interrupts
Date: Fri, 27 Jul 2007 09:36:47 -0500 [thread overview]
Message-ID: <46AA02FF.5020401@lwfinger.net> (raw)
In-Reply-To: <1185530070.4006.46.camel@johannes.berg>
Johannes Berg wrote:
> On Thu, 2007-07-26 at 15:13 -0500, Larry Finger wrote:
>> Michael,
>>
>> When I try the -mb tree on my old i386 notebook, I get an "irq 11: nobody cared"
>> message and interrupts for the bcm43xx-mac80211 device are not initialized.
>
> Hm. Just a thought about something related: do you have 'debug shared
> interrupts' on?
No I didn't. Thanks for the suggestion.
Larry
prev parent reply other threads:[~2007-07-27 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 20:13 A problem with shared interrupts Larry Finger
2007-07-26 22:42 ` Michael Buesch
2007-07-27 0:04 ` Larry Finger
2007-07-27 9:54 ` Johannes Berg
2007-07-27 14:36 ` Larry Finger [this message]
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=46AA02FF.5020401@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 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).