Re: Frequent oops in shrink_mmap

Mike Coleman (mkc@kc.net)
29 Nov 1999 23:49:33 -0600

David desJardins <desj@google.com> writes:
> Or is it the
> case that only memory errors in the top two bits will trigger this oops,
> and other memory errors might remain undetected, and that the great
> majority of entries will be zero so that all of the errors are likely to
> occur on those pages?

Regarding whether only the top two bits are affected, I seem to be repeatedly
getting this same oops, but with the error always at 00000040 instead:

Nov 28 22:32:43 microdog kernel: Oops: 0000
Nov 28 22:32:43 microdog kernel: CPU: 0
Nov 28 22:32:43 microdog kernel: EIP: 0010:[try_to_free_buffers+18/136]
Nov 28 22:32:43 microdog kernel: EFLAGS: 00010206
Nov 28 22:32:43 microdog kernel: eax: 00000040 ebx: c02420c0 ecx: 00037900
edx: 00018000
Nov 28 22:32:43 microdog kernel: esi: 00000040 edi: 00000040 ebp: c02420c0
esp: c0095fa8
Nov 28 22:32:43 microdog kernel: ds: 0018 es: 0018 ss: 0018
Nov 28 22:32:43 microdog kernel: Process kswapd (pid: 4, process nr: 4, stackpag
e=c0095000)
Nov 28 22:32:43 microdog kernel: Stack: 00000030 c0094000 c0119daa c02420c0 0000
0016 00000006 c011eaeb 00000006
Nov 28 22:32:43 microdog kernel: 00000030 00000000 c01c0cda c00941c1 c011
eb97 00000030 00000f00 c009dfb4
Nov 28 22:32:43 microdog kernel: c0106000 00001000 c0106513 00000000 0000
0f00 c01f3fd4
Nov 28 22:32:43 microdog kernel: Call Trace: [shrink_mmap+218/300] [do_try_to_fr
ee_pages+35/120] [tvecs+4894/25410] [kswapd+87/200] [get_options+0/116] [kernel_
thread+35/48]
Nov 28 22:32:43 microdog kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74
13 6a 00 e8 4c 01 

-- 
Any sufficiently adverse technology is indistinguishable from Microsoft.


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