From: Jonas Oreland <jonas.oreland@mysql.com>
To: daniel.ritz@gmx.ch
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-pcmcia <linux-pcmcia@lists.infradead.org>
Subject: Re: yenta_socket "nobody cared - Disabling IRQ #4"
Date: Sat, 19 Mar 2005 00:00:10 +0100 [thread overview]
Message-ID: <423B5D7A.1060304@mysql.com> (raw)
In-Reply-To: <200503182243.24174.daniel.ritz@gmx.ch>
Daniel Ritz wrote:
> hi
Hi
Thanks for your effort!
>
> it's the second time now i see this problem with an atheros chipset in
> combination with a TI bridge. last time it was the 1225...
> attached a patch that could help...
>
Report:
1) It works somewhat better. irq doesn't get disabled.
2) however wlan card get disfunctional. I haven't been able to contact my wap
even if i'm standing on it...
3) unplug has resulted in kernel panic (twice)
(btw: how do I do to capture and report those)
4) when unlug don't produce kernel panic, then there is no way of power-oning that card again.
5) booting with the card inserted makes it not power on when yenta_socket is loaded (module)
comment: the card being disfunction could have something to with the driver.
but before it worked sometimes...
> --------------
>
> for TI bridges: turn off interrupts during card power-on. this seems
> to be neccessary for some combination of TI bridges with at least CB cards
> with atheros chipset...problem is that they produce an interrupt storm
> during power-on so the kernel happens to disable the IRQ which is a bad
> thing (tm).
> adds a generic hook function so that a socket driver can hook into
> almost anywhere (by adding more hook points of course). this is the
> cleanest way i can think of. and it allows adding more workarounds
> for more problems...
> for the TI specific interrupt on-off stuff just save the MFUNC register
> and set it to 0 to disable all interrupts, restore it afterwards.
>
> Signed-off-by: Daniel Ritz <daniel.ritz@gmx.ch>
Some thoughts: (not I'm neither pcmcia nor linux expert).
The "irq storm", shouldn't that be "acked" in someway.
I.e. the card produced a lot of irq's (that get ignored)
isn't the "real" solution to capture them, and "do something clever"?
Instead of just "shutting the card down".
hmmm...wonder if that made sence
Question: Why do you think that it worked sometimes before?
/Jonas
ps.
but the hook was/is nice :-)
ds.
next prev parent reply other threads:[~2005-03-18 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 21:43 yenta_socket "nobody cared - Disabling IRQ #4" Daniel Ritz
2005-03-18 23:00 ` Jonas Oreland [this message]
2005-03-18 23:34 ` Francois Romieu
2005-03-18 23:51 ` Daniel Ritz
2005-03-19 8:05 ` yenta_socket "nobody cared - Disabling IRQ #4" - WORKING!! Jonas Oreland
2005-03-19 21:14 ` Daniel Ritz
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 14:44 yenta_socket "nobody cared - Disabling IRQ #4" Jonas Oreland
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=423B5D7A.1060304@mysql.com \
--to=jonas.oreland@mysql.com \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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.