Re: Severe problem with e1000 driver in 2.4.31/32 (at least)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 16 Feb 2006 13:49:12 -0800 (PST)
Jesse Brandeburg <[email protected]> wrote:


> > The box runs into a BUG in e1000_hw.c line 5052. The BUG shows up because
> > the code is obviously executed inside an interrupt, which seems not
> > intended. As this BUG is always reproducable and pretty annoying we made
> > this pretty bad workaround:
> 
> Please try this patch, compile tested.  It matches up this particular code 
> to what is currently in 2.6.16-rc
> 
> e1000: fix BUG reported due to calling msec_delay in irq context
> 
> There are some functions that are called in irq context that need to use
> msec_delay_irq instead to avoid a BUG.
> 
> Signed-off-by: Jesse Brandeburg <[email protected]>

Hello Jesse,

I can confirm the patch eliminates the problem here. I first thought about
doing it the same way but was unsure whether the function itself should execute
in interrupt at all.
Thank you for your immediate answer, please make sure to include the patch as
is in 2.4.

Stephan



> 
> ---
> 
>   drivers/net/e1000/e1000_hw.c |    8 ++++----
>   1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/e1000/e1000_hw.c b/drivers/net/e1000/e1000_hw.c
> --- a/drivers/net/e1000/e1000_hw.c
> +++ b/drivers/net/e1000/e1000_hw.c
> @@ -5049,7 +5049,7 @@ e1000_config_dsp_after_link_change(struc
>               if(ret_val)
>                   return ret_val;
> 
> -            msec_delay(20);
> +            msec_delay_irq(20);
> 
>               ret_val = e1000_write_phy_reg(hw, 0x0000,
>                                             IGP01E1000_IEEE_FORCE_GIGA);
> @@ -5073,7 +5073,7 @@ e1000_config_dsp_after_link_change(struc
>               if(ret_val)
>                   return ret_val;
> 
> -            msec_delay(20);
> +            msec_delay_irq(20);
> 
>               /* Now enable the transmitter */
>               ret_val = e1000_write_phy_reg(hw, 0x2F5B, phy_saved_data);
> @@ -5098,7 +5098,7 @@ e1000_config_dsp_after_link_change(struc
>               if(ret_val)
>                   return ret_val;
> 
> -            msec_delay(20);
> +            msec_delay_irq(20);
> 
>               ret_val = e1000_write_phy_reg(hw, 0x0000,
>                                             IGP01E1000_IEEE_FORCE_GIGA);
> @@ -5114,7 +5114,7 @@ e1000_config_dsp_after_link_change(struc
>               if(ret_val)
>                   return ret_val;
> 
> -            msec_delay(20);
> +            msec_delay_irq(20);
> 
>               /* Now enable the transmitter */
>               ret_val = e1000_write_phy_reg(hw, 0x2F5B, phy_saved_data);
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux