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. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
