From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarek Poplawski Subject: Re: 2.6.24 BUG: soft lockup - CPU#X Date: Thu, 27 Mar 2008 11:33:40 +0100 Message-ID: <20080327103340.GB2845@ami.dom.local> References: <47EA7DE8.9070203@sun.com> <47EAAE9A.9050305@gmail.com> <47EAB158.3080806@sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: Matheos Worku Return-path: Received: from ug-out-1314.google.com ([66.249.92.174]:32867 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756601AbYC0K2v (ORCPT ); Thu, 27 Mar 2008 06:28:51 -0400 Received: by ug-out-1314.google.com with SMTP id z38so302539ugc.16 for ; Thu, 27 Mar 2008 03:28:49 -0700 (PDT) Content-Disposition: inline In-Reply-To: <47EAB158.3080806@sun.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Mar 26, 2008 at 01:26:00PM -0700, Matheos Worku wrote: ... > nsn57-110 login: BUG: soft lockup - CPU#2 stuck for 11s! ... > Call Trace: > [] __skb_clone+0x24/0xdc > [] skb_realloc_headroom+0x30/0x63 > [] :niu:niu_start_xmit+0x114/0x5af > [] gart_map_single+0x0/0x70 > [] dev_hard_start_xmit+0x1d2/0x246 ... Maybe I'm wrong with this again, but I wonder about this gart_map_single on almost all traces, and probably not supposed to be seen here. Did you try with some memory re-config/debugging? Regards, Jarek P.