Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Evgeniy Polyakov
Date: Sunday, September 21, 2008 - 12:38 pm

Hi.

On Sun, Sep 21, 2008 at 09:14:04PM +0200, Johannes Berg (johannes@sipsolutions.net) wrote:

Both maintainers were added to the copy list.


As I pointed, I can rewrite the whole driver's initialization process,
so that it looked like init/wait/exit loop, which can be processed at
the module load and when fatal interrupt fires. Do this a fix? This is
not even a remotely workaround. We can just add
rmmod/modprobe/ifdown/ifup to the crontab job. Another users reported in
bugzilla that they needed to reboot a machine to make card working
again. I'm not sure that user tried to do a rmmod/modprobe though.


If we will keep silence, no one will notice that problem exists.

I do hope this will result in a progress. Arjan, do you aggree to add
this patch to the current tree?

diff --git a/drivers/net/wireless/ipw2100.c b/drivers/net/wireless/ipw2100.c
index 19a401c..9a7b64c 100644
--- a/drivers/net/wireless/ipw2100.c
+++ b/drivers/net/wireless/ipw2100.c
@@ -206,6 +206,8 @@ MODULE_PARM_DESC(disable, "manually disable the radio (default 0 [radio on])");
 
 static u32 ipw2100_debug_level = IPW_DL_NONE;
 
+static int ipw2100_max_fatal_ints = 10;
+
 #ifdef CONFIG_IPW2100_DEBUG
 #define IPW_DEBUG(level, message...) \
 do { \
@@ -3174,6 +3176,10 @@ static void ipw2100_irq_tasklet(struct ipw2100_priv *priv)
 	if (inta & IPW2100_INTA_FATAL_ERROR) {
 		printk(KERN_WARNING DRV_NAME
 		       ": Fatal interrupt. Scheduling firmware restart.\n");
+		WARN_ON(1);
+
+		BUG_ON(ipw2100_max_fatal_ints-- <= 0);
+
 		priv->inta_other++;
 		write_register(dev, IPW_REG_INTA, IPW2100_INTA_FATAL_ERROR);
 


-- 
	Evgeniy Polyakov
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmwa ..., Evgeniy Polyakov, (Sun Sep 21, 10:23 am)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Evgeniy Polyakov, (Sun Sep 21, 10:38 am)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Arjan van de Ven, (Sun Sep 21, 11:04 am)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Evgeniy Polyakov, (Sun Sep 21, 11:28 am)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Arjan van de Ven, (Sun Sep 21, 11:35 am)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Evgeniy Polyakov, (Sun Sep 21, 12:00 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Arjan van de Ven, (Sun Sep 21, 12:20 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Evgeniy Polyakov, (Sun Sep 21, 12:38 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Arjan van de Ven, (Sun Sep 21, 12:43 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Denys Fedoryshchenko, (Sun Sep 21, 2:43 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Denys Fedoryshchenko, (Sun Sep 21, 3:15 pm)
Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling fi ..., Evgeniy Polyakov, (Thu Sep 25, 10:56 pm)