From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: sky2 panic in 2.6.32.1 under load (new oops) Date: Wed, 30 Dec 2009 00:07:24 -0800 Message-ID: <20091230000724.4083e7dd@nehalam> References: <4B300A2A.8040305@gmail.com> <4B300E30.9090707@majjas.com> <4B3114E3.1070602@majjas.com> <4B329FA3.9090904@majjas.com> <20091223230102.4bb0100e.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Andrew Morton , "Berck E. Nash" , "linux-kernel@vger.kernel.org" , netdev@vger.kernel.org To: Michael Breuer Return-path: In-Reply-To: <20091223230102.4bb0100e.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, 23 Dec 2009 23:01:02 -0800 Andrew Morton wrote: > > Dec 23 17:32:58 mail kernel: DRHD: handling fault status reg 2 > > Dec 23 17:32:58 mail kernel: DMAR:[DMA Read] Request device [06:00.0] > > fault addr fff8423fe000 > > Dec 23 17:32:58 mail kernel: DMAR:[fault reason 06] PTE Read access is > > not set > > Dec 23 17:32:58 mail kernel: sky2 0000:06:00.0: error interrupt > > status=0x80000000 > > Dec 23 17:32:58 mail kernel: sky2 0000:06:00.0: PCI hardware error (0x2010) > > Dec 23 17:33:06 mail kernel: ------------[ cut here ]------------ > > Dec 23 17:33:06 mail kernel: WARNING: at net/sched/sch_generic.c:255 > > dev_watchdog+0xf3/0x161() > > Dec 23 17:33:06 mail kernel: Hardware name: System Product Name > > Dec 23 17:33:06 mail kernel: NETDEV WATCHDOG: eth0 (sky2): transmit Just to reiterate, these are consistent with a DMA error on transmit. Since is 4 seconds after the DHCPACK, they probably are not related, except that when DHCP renew may have caused more traffic. Are you using something like network console or kgdb, or anything that could be using some unusual network I/O?