Re: Stack traces in 2.6.9-rc2-mm4

From: J.A. Magallon
Date: Thu Sep 30 2004 - 18:18:56 EST



On 2004.10.01, Ingo Molnar wrote:

* J.A. Magallon <jamagallon@xxxxxxx> wrote:

> Sep 30 23:54:41 werewolf pumpd[9843]: intf: broadcast: 255.255.255.255
> Sep 30 23:54:41 werewolf pumpd[9843]: intf: network: 82.198.40.0
> Sep 30 23:54:41 werewolf kernel: using smp_processor_id() in preemptible > code: pump/9843
> Sep 30 23:54:41 werewolf kernel: [smp_processor_id+135/141] > smp_processor_id+0x87/0x8d
> Sep 30 23:54:41 werewolf kernel: [<b011bc8f>] smp_processor_id+0x87/0x8d
> Sep 30 23:54:41 werewolf kernel: [pg0+1079594592/1337930752] > death_by_timeout+0x11/0x65 [ip_conntrack]
> Sep 30 23:54:41 werewolf kernel: [<f099fe60>] death_by_timeout+0x11/0x65 > [ip_conntrack]

does the patch below fix these for you?

Ingo

--- include/linux/netfilter_ipv4/ip_conntrack.h.orig
+++ include/linux/netfilter_ipv4/ip_conntrack.h
@@ -311,7 +311,7 @@ struct ip_conntrack_stat
unsigned int expect_delete;
};
-#define CONNTRACK_STAT_INC(count) (__get_cpu_var(ip_conntrack_stat).count++)
+#define CONNTRACK_STAT_INC(count) (per_cpu(ip_conntrack_stat, _smp_processor_id()).count++)
/* eg. PROVIDES_CONNTRACK(ftp); */
#define PROVIDES_CONNTRACK(name) \

Yes, It has killed the stack trace.
But this messa from ACPI (I suspect it is unrelated) stays:

Oct 1 01:14:33 werewolf pumpd[5813]: intf: numDns: 2
Oct 1 01:14:33 werewolf pumpd[5813]: intf: broadcast: 255.255.255.255
Oct 1 01:14:33 werewolf pumpd[5813]: intf: network: 82.198.40.0
Oct 1 01:14:33 werewolf kernel: ACPI: PCI interrupt 0000:03:0a.0[A] -> GSI 22 (level, low) -> IRQ 22
Oct 1 01:14:33 werewolf pumpd[5813]: configured interface eth0
Oct 1 01:14:33 werewolf ifup: done.

Thanks.

--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-rc2-mm4 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #1


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/