netdev
[Top] [All Lists]

Re: linux 2.6.9: r8169: eth0: PCI error (status: 0x8404). Device disable

To: Francois Romieu <romieu@xxxxxxxxxxxxx>
Subject: Re: linux 2.6.9: r8169: eth0: PCI error (status: 0x8404). Device disabled.
From: Eamonn Hamilton <EAMONN.HAMILTON@xxxxxxxx>
Date: Wed, 10 Nov 2004 10:04:09 +0000
Cc: netdev <netdev@xxxxxxxxxxx>
In-reply-to: <20041109234353.GA6020@xxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1098269117.6631.5.camel@xxxxxxxxxxxxxxxxxxxxx> <20041020121520.GA4004@xxxxxxxxxxxxxxxxxxxxxxxxxx> <1098282567.6631.10.camel@xxxxxxxxxxxxxxxxxxxxx> <20041020201010.GA13023@xxxxxxxxxxxxxxxxxxxxxxxxxx> <1098350743.15528.40.camel@xxxxxxxxxxxxxxxxxxxxx> <20041021120208.GA752@xxxxxxxxxxxxxxxxxxxxxxxxxx> <1098437493.5513.8.camel@xxxxxxxxxxxxxxxxxxxxx> <20041022105224.GA26714@xxxxxxxxxxxxxxxxxxxxxxxxxx> <1099922587.16833.2.camel@xxxxxxxxxxxxxxxxxxxxx> <20041109234353.GA6020@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 2004-11-10 at 00:43 +0100, Francois Romieu wrote:
> Eamonn Hamilton <EAMONN.HAMILTON@xxxxxxxx> :
> [...]
> > Anyway, The device was brought back to functioning order by removing the
> > module and re-inserting it. I have to confess, I forgot to try simply
> > downing/upping it, I'll ask my friend to try that should it happen
> > again. Bizarrely, the frequency of it happening seems to be down for
> > whatever reason - it took ~12GB traffic to cause it to happen this
> > afternoon.
> > 
> > Anyway, hope this helps.
> 
> Yes. It suggests that it should not be too hard to add a hack for recovery.
> 
> I am a bit surprized with this isolated report though.

Arghh.

The guy whose computer it is has just told me that he was getting weird
errors until he rebooted it after reinserting the module, which makes me
very suspicious of DMA/PCI issues on this board. 

Ho-hum, more testing required.

Cheers,
Eamonn


> 
> --
> Ueimor
-- 
Eamonn Hamilton

Senior Systems Engineer
SAIC Ltd
Tel : 01224 333833


<Prev in Thread] Current Thread [Next in Thread>