also sprach martin f krafft <madduck@debian.org> [2003.04.28.1325 +0200]: > lately, one of my machines is experiencing very many segmentation > faults. I have grsecurity installed, which logs every single signal > 11 sent to a process, and from the logs I can see that there are > things like egrep, cron, rsync, zsh, and sshd being killed with > signal 11 -- that should not be. ocassionally (like now), i see kernel logs about unfulfilled paging requests: kernel: printing eip: kernel: c012347b kernel: Oops: 0000 kernel: CPU: 0 kernel: EIP: 0010:[do_generic_file_read+363/1024] Not tainted kernel: EFLAGS: 00010286 kernel: eax: a2000000 ebx: c14cb634 ecx: 00000011 edx: 0000fa65 kernel: esi: c15be994 edi: c5d379f4 ebp: 0000032e esp: c73f3f1c kernel: ds: 0018 es: 0018 ss: 0018 kernel: Process rsync (pid: 17550, stackpage=c73f3000) kernel: Stack: 00000000 daf55f40 ffffffea 00030000 00001000 00000001 00000000 00000000 kernel: c5d37940 c0123a05 daf55f40 daf55f60 c73f3f64 c01238f0 00000000 daf55f40 kernel: ffffffea 00030000 0001e000 00012000 4a20e008 00000000 c012f626 daf55f40 kernel: Call Trace: [generic_file_read+133/320] [file_read_actor+0/144] [sys_read+150/240] [system_call+51/80] kernel: kernel: Code: 39 78 08 75 f4 39 68 0c 75 ef 89 c3 85 db 0f 84 61 01 00 00 kernel: Unable to handle kernel paging request at virtual address a2000008 kernel: printing eip: kernel: c012347b kernel: *pde = 00000000 kernel: Oops: 0000 kernel: CPU: 0 kernel: EIP: 0010:[do_generic_file_read+363/1024] Not tainted kernel: EFLAGS: 00010286 kernel: eax: a2000000 ebx: c14cb634 ecx: 00000011 edx: 0000fa65 kernel: esi: c15be994 edi: c5d379f4 ebp: 0000032e esp: c73f3f1c kernel: ds: 0018 es: 0018 ss: 0018 kernel: Process rsync (pid: 17550, stackpage=c73f3000) kernel: Stack: 00000000 daf55f40 ffffffea 00030000 00001000 00000001 00000000 00000000 kernel: c5d37940 c0123a05 daf55f40 daf55f60 c73f3f64 c01238f0 00000000 daf55f40 kernel: ffffffea 00030000 0001e000 00012000 4a20e008 00000000 c012f626 daf55f40 kernel: Call Trace: [generic_file_read+133/320] so it tried to swap in from 0xa2000008 and failed to do so. how do i find out where that address is located? This is unbelievable. New mobo, new CPU, new RAM, new Hdd, and it's just broken. compared to another machine that's still running a 386-SX25, and has been for the past 7 years straight, this is a pity! i am very grateful for any tips... (btw: the reason this isn't on linux-kernel (yet) is because i hate that mailing list. it's impossible to get any constructive information in my experience. please excuse, debian-user is just the best...) -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Keyserver problems? http://keyserver.kjsl.com/~jharris/keyserver.html Get my key here: http://madduck.net/me/gpg/publickey
Attachment:
pgpnS1Yi7NXNR.pgp
Description: PGP signature