[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120601201357.GA22597@electric-eye.fr.zoreil.com>
Date: Fri, 1 Jun 2012 22:13:57 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Vincent Pelletier <plr.vincent@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: r8169: IO_PAGE_FAULT & netdev watchdog
Vincent Pelletier <plr.vincent@...il.com> :
[...]
> If it's bogus, could it be a mis-interpretation of its state when the error
> occurs (I don't know how CPU knows a fault happened, I guess some IRQ + some
> register contain error status, address of error, some process/context
> identifier) ?
See "AMD I/O Virtualization Technology (IOMMU) Specification".
> Or hardware bug ? Or MMU misconfiguration for some reason ?
I don't have time to poke deeply enough into the iommu code.
[...]
> If it's not bogus, would it be the sign of firmware bug (accessing some
> unpredictable memory upon certain conditions) ?
That's what I thought first. Or I should have added something to the r8169
driver. However it's quite reproducible, the failing address is one of the
mapped Rx or Tx descriptor ring address - don't remember which one, see
the PR at korg - and it does not fit the timing pattern.
[...]
> I'll try either and both. Given the poor result I got from
> reset/remove/rescan, I guess I should reboot between attempts, right ?
Yes. The inlined patch could help avoiding the problem but it is not
supposed to help a failed network adapter recovering.
> Should I prevent original module auto-loading at boot ? Maybe more than just
> r8169 ?
It should not be required. YMMV.
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists