From: Jarek Poplawski <jarkao2@o2.pl>
To: Christian Kujau <christian@g-house.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
malte@g-house.de, Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: 2.6.20.4: NETDEV WATCHDOG and lockups
Date: Thu, 5 Apr 2007 08:20:00 +0200 [thread overview]
Message-ID: <20070405062000.GA1717@ff.dom.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0704041412310.3963@sheep.housecafe.de>
On Wed, Apr 04, 2007 at 02:20:23PM +0100, Christian Kujau wrote:
> On Wed, 4 Apr 2007, Jarek Poplawski wrote:
> >So, it's a lot sooner than before. (BTW, isn't there anything
> >in debug log?)
>
> No, nothing. I've set up remote-syslgging to the other node (node1
> logging to node2 and vice versa) - nothing :(
>
> >I see both CPUs did interrupt handling again.
>
> Yes, when booting with 'lapic' both CPUs/cores are handling interrupts
> again. However, since 'lapic' seems to lead to crashes here, we would be
> more than happy to just boot with 'noapic' but have 'irqbalance'
> working. Unfortunately, irqbalance is unable to write to
> /proc/irq/*/smp_affinity (did not help to disable CONFIG_IRQBALANCE).
I hope you are right, but maybe it's not lapic's fault?
Probably the fastest way to know would be to try with
some other card, yet.
> >Maybe it's a real locking problem. Here are some more
> >suggestions for testing (if you don't find anything better):
> >- try without SMP, so: 'acpi=off lapic nosmp'
BTW, I'm not sure acpi should be turned off with any
modern hardware. Did you tried to compile with
CONFIG_ACPI = y, all other acpi options off, and maybe
to tweak only with 'pci=...' boot parameter?
Regards,
Jarek P.
next prev parent reply other threads:[~2007-04-05 6:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 19:41 2.6.20.4: NETDEV WATCHDOG and lockups Christian Kujau
2007-04-02 20:20 ` Chuck Ebbert
2007-04-02 21:15 ` Christian Kujau
2007-04-03 5:34 ` Christian Kujau
2007-04-03 15:17 ` Christian Kujau
2007-04-03 5:20 ` Len Brown
2007-04-03 5:46 ` Christian Kujau
2007-04-03 6:58 ` Jarek Poplawski
2007-04-03 9:47 ` Christian Kujau
2007-04-03 15:19 ` Christian Kujau
2007-04-03 20:34 ` Francois Romieu
2007-04-04 11:21 ` Jarek Poplawski
2007-04-04 13:20 ` Christian Kujau
2007-04-05 6:20 ` Jarek Poplawski [this message]
2007-04-06 18:19 ` Christian Kujau
2007-04-06 18:27 ` Christian Kujau
2007-04-17 12:36 ` Jarek Poplawski
2007-04-04 13:53 ` Denys
2007-04-04 17:34 ` Christian Kujau
2007-04-03 20:57 ` Francois Romieu
2007-04-04 13:12 ` Christian Kujau
2007-04-04 18:10 ` Francois Romieu
2007-04-04 18:57 ` Christian Kujau
[not found] <fa.P3upyx4QAcXHtp/c/s+b4/cKk5w@ifi.uio.no>
[not found] ` <fa.u/RjoL2ybMMaAY+GDfTzm7jO5d0@ifi.uio.no>
[not found] ` <fa.G7qJfhdvOynxlffny+Xc1kIaqBY@ifi.uio.no>
2007-04-03 14:28 ` Robert Hancock
2007-04-03 15:26 ` Christian Kujau
2007-04-03 15:41 ` Lee Revell
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=20070405062000.GA1717@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=christian@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=malte@g-house.de \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.