I got this while compiling kernel over NFS.
pavel@bug:/usr/src/linux-acpi$ time make bzImage
gcc -D__KERNEL__ -I/elf/big/linux-acpi/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-pipe -mpreferred-stack-boundary=2 -march=i386 -DUTS_MACHINE='"i386"'
-c -o init/version.o init/version.c
gcc: Internal compiler error: program cpp got fatal signal 11
make: *** [init/version.o] Error 1
0.46user 0.23system 6.09 (0m6.092s) elapsed 11.32%CPU
pavel@bug:/usr/src/linux-acpi$
And signal 11 was because:
Jun 5 23:00:48 bug kernel: kernel BUG at inode.c:486!
Jun 5 23:00:48 bug kernel: invalid operand: 0000
Jun 5 23:00:48 bug kernel: CPU: 0
Jun 5 23:00:49 bug kernel: EIP: 0010:[clear_inode+51/244]
Jun 5 23:00:49 bug kernel: EFLAGS: 00010286
Jun 5 23:00:49 bug kernel: eax: 0000001b ebx: c3c3f480 ecx:
c231e000 edx: c2f998a0
Jun 5 23:00:49 bug kernel: esi: c0304880 edi: c36a0f90 ebp:
c231ff84 esp: c231feb8
Jun 5 23:00:49 bug kernel: ds: 0018 es: 0018 ss: 0018
Jun 5 23:00:49 bug kernel: Process cpp (pid: 8457,
stackpage=c231f000)
Jun 5 23:00:49 bug kernel: Stack: c029b986 c029b9c5 000001e6 c3c3f480
c0140a37 c3c3f480 c13f6c80 c3c3f480
Jun 5 23:00:49 bug kernel: c016c969 c3c3f480 c013e646 c13f6c80
c3c3f480 c13f6c80 00000000 c0136ed9
Jun 5 23:00:49 bug kernel: c13f6c80 c231ff34 c0137619 c36a0f90
c231ff34 00000000 c3285000 00000000
Jun 5 23:00:49 bug kernel: Call Trace: [iput+327/348]
[nfs_dentry_iput+33/40] [dput+214/324] [cached_lookup+69/80]
[path_walk+1317/1916] [open_namei+115/1392] [nfs_file_release+28/36]
Jun 5 23:00:49 bug kernel: [dput+81/324] [filp_open+46/76]
[sys_open+53/184] [system_call+51/56]
Jun 5 23:00:49 bug kernel:
Jun 5 23:00:49 bug kernel: Code: 0f 0b 83 c4 0c f6 83 f4 00 00 00 10
75 19 68 e8 01 00 00 68
Retrying compilation, I get exactly same oops.
Pavel
-- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/