Newsgroup: it.comp.os.linux.iniziare
Titolo: Blocchi del server - lunghetto

Ciao,
è da un pò che mi si congela uno dei 3 server identici .... che ho in
azienda ....
Fedora Core 1
P4 HT con 1 Gb Ram su scheda madre Tyan e controller 3ware s-ata 4 canali
in Raid 5.
Questo è quello che ho trovato in /var/log/messages,
ma non sempre lo indica. Spesso a monitor compare solo l'ultima parte del
messaggio, ma nei log non scrive, e quindi non capisco da dove possa esere
riprodotto l'errore.
Potrebbe essere un problema causato dalla ram difettosa?
Ciao
Feb 17 04:02:01 smbcservice kernel: Unable to handle kernel paging request at virtual address ff8dec60
Feb 17 04:02:01 smbcservice kernel:  printing eip:
Feb 17 04:02:01 smbcservice kernel: c015031e
Feb 17 04:02:01 smbcservice kernel: *pde = e37e87af
Feb 17 04:02:01 smbcservice kernel: Unable to handle kernel paging request at virtual address a37e8378
Feb 17 04:02:01 smbcservice kernel:  printing eip:
Feb 17 04:02:01 smbcservice kernel: c011cbea
Feb 17 04:02:01 smbcservice kernel: *pde = dfb513d9
Feb 17 04:02:01 smbcservice kernel: Unable to handle kernel paging request at virtual address 9fb51fa0
Feb 17 04:02:01 smbcservice kernel:  printing eip:
Feb 17 04:02:01 smbcservice kernel: c011cbea
Feb 17 04:02:01 smbcservice kernel: *pde = 33701cc9
Feb 17 04:02:01 smbcservice kernel: *pte = 00000000
Feb 17 04:02:01 smbcservice modprobe: modprobe: Invalid line 5 in /etc/modules.conf ^Ialia
Feb 17 04:02:01 smbcservice kernel: Oops: 0000
Feb 17 04:02:01 smbcservice modprobe: modprobe: Invalid line 6 in /etc/modules.conf ^Ialias2eth0
Feb 17 04:02:01 smbcservice kernel: parport_pc lp parport autofs e1000 bonding microcode reiserfs keybdev mousedev hid input ehci-hcd usb-uhci usbcore ext3 jbd 3w-9xxx sd_mod scsi_mod  
Feb 17 04:02:01 smbcservice modprobe: modprobe: Invalid line 8 in /etc/modules.conf ^Iali
Feb 17 04:02:01 smbcservice kernel: CPU:    0
Feb 17 04:02:01 smbcservice kernel: EIP:    0060:[<c011cbea>]    Not tainted
Feb 17 04:02:01 smbcservice kernel: EFLAGS: 00010206
Feb 17 04:02:01 smbcservice kernel: 
Feb 17 04:02:01 smbcservice kernel: EIP is at do_page_fault [kernel] 0x26a (2.4.22-1.2199.nptlsmp)
Feb 17 04:02:01 smbcservice kernel: eax: 00000013   ebx: dfb51000   ecx: c0374888   edx: 00004574
Feb 17 04:02:01 smbcservice kernel: esi: d426d3a4   edi: e46e4000   ebp: 000003e8   esp: e46e5d58
Feb 17 04:02:01 smbcservice kernel: ds: 0068   es: 0068   ss: 0068
Feb 17 04:02:01 smbcservice kernel: Process prelink (pid: 7544, stackpage=e46e5000)
Feb 17 04:02:01 smbcservice kernel: Stack: c02a68af dfb513d9 f8832669 00000001 00000802 00001000 f786de00 a37e8378 
Feb 17 04:02:01 smbcservice kernel:        00000802 00000000 00000000 00000207 00000010 c01c4478 00030001 00000000 
Feb 17 04:02:01 smbcservice kernel:        00000000 00000000 c01bf785 c1c15000 00000002 f72fe400 0000000a 0000000a 
Feb 17 04:02:01 smbcservice kernel: Call Trace:   [<f8832669>] twa_post_command_packet [3w-9xxx] 0x2d (0xe46e5d60)
Feb 17 04:02:01 smbcservice kernel: [<c01c4478>] clear_selection [kernel] 0x18 (0xe46e5d8c)
Feb 17 04:02:01 smbcservice kernel: [<c01bf785>] hide_cursor [kernel] 0x65 (0xe46e5da0)
Feb 17 04:02:01 smbcservice kernel: [<c01c2f56>] vt_console_print [kernel] 0x206 (0xe46e5db8)
Feb 17 04:02:01 smbcservice kernel: [<c01240cf>] __call_console_drivers [kernel] 0x5f (0xe46e5de8)
Feb 17 04:02:01 smbcservice kernel: [<c01241c5>] call_console_drivers [kernel] 0x65 (0xe46e5e04)
Feb 17 04:02:01 smbcservice kernel: [<c011c980>] do_page_fault [kernel] 0x0 (0xe46e5e10)
Feb 17 04:02:01 smbcservice kernel: [<c0109c18>] error_code [kernel] 0x34 (0xe46e5e18)
Feb 17 04:02:01 smbcservice kernel: [<c011cbea>] do_page_fault [kernel] 0x26a (0xe46e5e4c)
Feb 17 04:02:01 smbcservice kernel: [<c016b7d1>] iget4_locked [kernel] 0x61 (0xe46e5eb0)
Feb 17 04:02:01 smbcservice kernel: [<c0168400>] dput [kernel] 0x30 (0xe46e5ed8)
Feb 17 04:02:01 smbcservice kernel: [<c015e306>] link_path_walk [kernel] 0x816 (0xe46e5eec)
Feb 17 04:02:01 smbcservice kernel: [<c011c980>] do_page_fault [kernel] 0x0 (0xe46e5f10)
Feb 17 04:02:01 smbcservice kernel: [<c0109c18>] error_code [kernel] 0x34 (0xe46e5f18)
Feb 17 04:02:01 smbcservice kernel: [<c0150068>] chown_common [kernel] 0x78 (0xe46e5f40)
Feb 17 04:02:01 smbcservice kernel: [<c015031e>] dentry_open [kernel] 0x6e (0xe46e5f4c)
Feb 17 04:02:01 smbcservice kernel: [<c01502a8>] filp_open [kernel] 0x68 (0xe46e5f70)
Feb 17 04:02:01 smbcservice kernel: [<c0150683>] sys_open [kernel] 0x53 (0xe46e5fa8)
Feb 17 04:02:01 smbcservice kernel: [<c0109b27>] system_call [kernel] 0x33 (0xe46e5fc0)
Feb 17 04:02:01 smbcservice kernel: 
Feb 17 04:02:01 smbcservice kernel: 
Feb 17 04:02:01 smbcservice kernel: Code: 8b 9c ab 00 00 00 c0 c7 04 24 c0
68 2a c0 89 5c 24 04 e8 ef 
-- 
------------------------------------------
Togliere aldruz- per rispondermi via e-mail
------------------------------------------

 Feb 17 04:02:01 smbcservice kernel: Process prelink (pid: 7544, stackpage=e46e5000)
Ke processo hai sotto il pid 7544 ?
dai uno sguardo a /etc/modules.conf


 Potrebbe essere un problema causato dalla ram difettosa?
La ram sembra un'ottima indiziata.