kernel BUG at inode.c:486! (2.4.5)

2001-06-27 Thread Soeren Sonnenburg
This happens here from time to time :-( Is it fixed in some 2.4.6preX ? Soeren. ==snip kernel BUG at inode.c:486! invalid operand: CPU:0 EIP:0010:[load_aout_library+19/640] EFLAGS: 00010286 eax: 001b ebx: e43baa80 ecx: d7f54000 edx: e3801ac0 esi

kernel BUG at inode.c:486 - where fixed ?

2001-06-20 Thread Soeren Sonnenburg
Hi! Has this bug been fixed and if so in which version ? Jun 20 00:15:14 zapp kernel: kernel BUG at inode.c:486! Jun 20 00:15:14 zapp kernel: invalid operand: Jun 20 00:15:14 zapp kernel: CPU:0 Jun 20 00:15:14 zapp kernel: EIP:0010:[clear_inode+51/256] Jun 20 00:15:14 zapp kernel

Re: from dmesg: kernel BUG at inode.c:486

2001-06-12 Thread Olivier Sessink
0013 Before first symbol 13: 68 00 00 00 00push $0x0 kernel BUG at inode.c:486! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010286 eax: 001b ebx: cc703ba0 ecx: 0001 edx: c025ba84 esi: c025ec60 edi: c976eac0 ebp: c32fdfa4 esp: c32fdeec ds

kernel BUG at inode.c:486!

2001-05-31 Thread Steinar Hauan
hello, over the last few days, i've started to get several error messages of the following type: kernel: kernel BUG at inode.c:486! kernel: invalid operand: kernel: CPU:1 kernel: EIP:0010:[clear_inode+53/256] kernel: EIP:0010:[] kernel: EFLAGS: 00010286 (2 examples

Re: OOPS with 2.4.5 [kernel BUG at inode.c:486]

2001-05-30 Thread Trond Myklebust
> " " == Alexander Viro <[EMAIL PROTECTED]> writes: > On 30 May 2001, Trond Myklebust wrote: >> Al: Is there any reason why the cases >> >> if (!inode->i_nlink) >> >> and the 'magic nfs path' should be treated differently? >> Personally, I'd rather prefer to mer

Re: OOPS with 2.4.5 [kernel BUG at inode.c:486]

2001-05-30 Thread Alexander Viro
On 30 May 2001, Trond Myklebust wrote: > The reason we haven't seen this before is that we had 'force_delete' > that would always set i_nlink = 0. Unfortunately force_delete is toxic > to mmap(), as it will discard any dirty pages rather than flushing > them to storage, so it was removed in the

Re: OOPS with 2.4.5 [kernel BUG at inode.c:486]

2001-05-30 Thread Trond Myklebust
>>>>> " " == Alexander Viro <[EMAIL PROTECTED]> writes: > On Tue, 29 May 2001, Gergely Tamas wrote: >> Warning (compare_maps): mismatch on symbol partition_name , >> ksyms_base says c01c4020, System.map says c0154160. Ignoring

Re: OOPS with 2.4.5 [kernel BUG at inode.c:486]

2001-05-29 Thread Alexander Viro
On Tue, 29 May 2001, Gergely Tamas wrote: > Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says >c01c4020, System.map says c0154160. Ignoring ksyms_base entry > kernel BUG at inode.c:486! [snip] _Lovely_. NFS, apparently on revalidate path, doesn't c

OOPS with 2.4.5 [kernel BUG at inode.c:486]

2001-05-29 Thread Gergely Tamas
ksymoops -h explains the options. Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c01c4020, System.map says c0154160. Ignoring ksyms_base entry kernel BUG at inode.c:486! invalid operand: CPU:1 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a

PROBLEM: "kernel BUG at inode.c:486!"

2001-05-26 Thread josn
Indexing as suggested in 'REPORTING-BUGS'. [1.] One line summary I get "kernel BUG at inode.c:486" when using NFS. [2.] Full description I can reproducibly generate a problem when I try to build a kernel, located on a NFS drive. The kernel build failes when compiling t