Skip to contentSkip to conversation

Segfaults in mkdir under high load. Software or hardware?

DISCUSSION Maurice Volaski 2 participants 2 messages Sep 19, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): mailman.3.1127041200.14075.linux-kernel-daily-digest@lists.us.dell.com

#1 lore raw
Quoted 11 lines · At 6:00 AM -0500 9/18/05, [email protected]…
Quoted 9 lines

I have been seeing a similar thing:

./current:Sep 17 18:00:01 [kernel] mkdir[7696]: segfault at 0000000000000000 rip 000000000040184d rsp 00007fffff826350 error 4

I'm using the plain 2.6.13 (from gentoo vanilla sources), though it was compiled with
gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)

x86_64 ? If so see http://bugzilla.kernel.org/show_bug.cgi?id=4851

Dual Opteron, and this looks like my issue. It recommends echo 0 > /proc/sys/kernel/randomize_va_space but that has not stopped it from happening, so I'll probably wait for the patch to get merged.

Signature · 3 lines
Maurice Volaski, [email protected]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
#2 lore raw
Quoted 12 lines · Maurice Volaski

At 6:00 AM -0500 9/18/05,

Quoted 9 lines · [email protected] wrote:
Quoted 8 lines

I have been seeing a similar thing:

./current:Sep 17 18:00:01 [kernel] mkdir[7696]: segfault at 0000000000000000 rip 000000000040184d rsp 00007fffff826350 error 4

I'm using the plain 2.6.13 (from gentoo vanilla sources), though it was compiled with
gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)

Quoted 5 lines
Quoted 1 line

x86_64 ? If so see http://bugzilla.kernel.org/show_bug.cgi?id=4851

Dual Opteron, and this looks like my issue. It recommends echo 0 > /proc/sys/kernel/randomize_va_space but that has not stopped it from happening, so I'll probably wait for the patch to get merged.

Linus has a patch for that, which you might try. Look at
http://bugzilla.kernel.org/show_bug.cgi?id=4851 for more details on this bug.

x86_64/kernel/setup.c 2005-09-18 07:37:25.000000000 +0200 renamed from x86_64/kernel/setup.c.orig 2005-09-18 07:34:36.000000000 +0200 +13 -0
@@ -793,10 +793,23 @@ static void __init amd_detect_cmp(struct
 #endif
 }
 
+#define HWCR 0xc0010015
+
 static int __init init_amd(struct cpuinfo_x86 *c)
 {
        int r;
        int level;
+#if CONFIG_SMP
+       unsigned long value;
+       // Disable TLB flush filter by setting HWCR.FFDIS:
+       // bit 6 of msr C001_0015
+       //
+       // Errata 63 for SH-B3 steppings
+       // Errata 122 for all(?) steppings
+       rdmsrl(HWCR, value);
+       value |= 1 << 6;
+       wrmsrl(HWCR, value);
+#endif
 
        /* Bit 31 in normal CPUID used for nonstandard 3DNow ID;
           3DNow is IDd by bit 31 in extended CPUID (1*32+31) anyway */