On Sun, Jan 17, 2010 at 11:26:46AM -0500, Michael Breuer wrote:Not sure I agree. The symptoms are identical to those I hit without DMAR earlier on. Also, as this issue only happens when there is high receive load, I'm thinking there's some sort of race between TX and RX within the sky2 driver, or hardware. I think that DMAR is correctly catching the error.
On 01/13/2010 04:16 PM, Michael Breuer wrote:My proposal is to send some summary as a new thread, with dmar in the
On 1/13/2010 4:09 PM, Jarek Poplawski wrote:Update: after leaving the system up for a few days, I hit the DMAR
On Wed, Jan 13, 2010 at 03:39:37PM -0500, Michael Breuer wrote:
subject, and cc-ed dmar maintainers.
My bad: was running with the af_packet.c version 3 patch; and Stephen's v4 patch from last week. Both on 2.6.32 from git (so 126.96.36.199). Can't move back to head as I've hit two unrelated issues.This happened during a scheduled backup from my win7It would be nice to name those patches each time. Anyway, try this
box. A reboot was required to re-enable eth0. After the error, eth0
was receiving, but was unable to transmit. For example, the log
reported arp bogons; DHCPINFORM/ACK sequences (where the ACK that
was logged was not transmitted), etc. The log was filled with sky2
eth0: tx timeout messages; as well as disable/enable of eth0.
I attempted to get things up again without a reboot, but failed.
Even rmmod& insmod did not fix whatever was broken on the TX side.
Note that this is similar to the earlier sky2 errors I had under
load with the variety of patches, and with or without DMAR enabled.
Just took way longer this time. Note that eth1 remained functional.
Unfortunately, with the latest set of patches installed, this is no
longer reproducible at will. I'd guess therefore that the patches
narrowed some hole, but didn't close it.
again without DMAR.