netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Matheos Worku <Matheos.Worku@Sun.COM>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.24 BUG: soft lockup - CPU#X
Date: Wed, 26 Mar 2008 22:46:48 +0100	[thread overview]
Message-ID: <20080326214648.GA16497@ami.dom.local> (raw)
In-Reply-To: <47EAB158.3080806@sun.com>

On Wed, Mar 26, 2008 at 01:26:00PM -0700, Matheos Worku wrote:
...
> Reproduced the lockup with irqbalance disabled and with single src of  
> interrupt (TX interrupt, UDP transmit).  Lockup appears in different  
> location though.
>
> Regards
> matheos
>
> irq of interest: 454 (TX interrupt)
>
>
> 454:      19249      93234     907186       2691          0        188    
>       0        160   PCI-MSI-edge      eth6
...
> .......
>
> 454:      19249     126519     907186       2691          0        188    
>       0        160   PCI-MSI-edge      eth6


Hmm... Is this before disabling or I miss something?

Of course, my hint could be wrong here, but there are some issues
around napi vs. irq balancing, so it would be interesting to check
this with all network cards irqs affinity set (and respected).

This could be interesting:
http://marc.info/?l=linux-netdev&m=120349568512423&w=2
(but I suspect there are possible other reasons yet)

Jarek P.

  reply	other threads:[~2008-03-26 21:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 16:46 2.6.24 BUG: soft lockup - CPU#X Matheos Worku
2008-03-26 17:31 ` Rick Jones
2008-03-26 20:14 ` Jarek Poplawski
2008-03-26 20:26   ` Matheos Worku
2008-03-26 21:46     ` Jarek Poplawski [this message]
2008-03-26 21:53       ` Jarek Poplawski
2008-03-27 10:33     ` Jarek Poplawski
2008-03-27 23:18       ` Brandeburg, Jesse
2008-03-27 23:45         ` Matheos Worku
2008-03-28  0:02           ` David Miller
2008-03-28  0:19             ` Matheos Worku
2008-03-28  0:34               ` David Miller
2008-03-28  1:22                 ` Herbert Xu
2008-03-28  1:38                   ` David Miller
2008-03-28 10:29                     ` Herbert Xu
2008-03-28 10:56                       ` Ingo Molnar
2008-03-28 11:06                         ` Herbert Xu
2008-03-28 11:29                           ` Herbert Xu
2008-03-28 12:19                             ` jamal
2008-03-28 13:26                               ` Herbert Xu
2008-03-28 14:07                                 ` jamal
2008-03-28 14:12                                 ` Ingo Molnar
2008-03-28 23:25                             ` David Miller
2008-03-28 14:09                           ` Ingo Molnar
2008-03-28  1:58                   ` Matheos Worku
2008-03-28 10:33                     ` jamal
2008-03-28 17:00                       ` Matheos Worku
2008-03-28 10:38                     ` Herbert Xu
2008-03-28 13:38                       ` Jarek Poplawski
2008-03-28 13:53                         ` Herbert Xu
2008-03-28 14:39                           ` Jarek Poplawski
2008-03-28 14:56                             ` Herbert Xu
2008-03-28 15:29                               ` Jarek Poplawski
2008-03-28 15:47                                 ` Jarek Poplawski
2008-03-29  1:06                                 ` Herbert Xu
2008-03-29  9:11                                   ` Jarek Poplawski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080326214648.GA16497@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=Matheos.Worku@Sun.COM \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).