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 - 1:20 pm

On Sun, Sep 21, 2008 at 12:43:32PM -0700, Arjan van de Ven (arjan@infradead.org) wrote:

Well, I actually wanted to have a bug there because of it, but now I
think that annoying repeated warning is enough to bring attention to the
problem by putting bug information into some magic special place called
kerneloops collection.

Consider for inclusing for the upcoming kernel to get wider
notifications. Yes, it is not a bugfix, I know.

diff --git a/drivers/net/wireless/ipw2100.c b/drivers/net/wireless/ipw2100.c
index 19a401c..6599211 100644
--- a/drivers/net/wireless/ipw2100.c
+++ b/drivers/net/wireless/ipw2100.c
@@ -206,6 +206,9 @@ 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;
+module_param(ipw2100_max_fatal_ints, int, 0644);
+
 #ifdef CONFIG_IPW2100_DEBUG
 #define IPW_DEBUG(level, message...) \
 do { \
@@ -3174,6 +3177,9 @@ 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(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 ..., Evgeniy Polyakov, (Sun Sep 21, 1:20 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)