Re: Oops w piatek
Jak doniosl wywiad/kontrwywiad dnia Fri, 21 Apr 2006 16:13:34 +0200
"Wojciech Firlej" <wfirlej@gmail.com> napisal(a):
> Czesc,
>
> wlasnie sie zabieralem powoli do domu, a tu nagle server przestaje
> reagowac - nawet bezposrednio nie da sie zalogowac. Po resecie nie
> zauwazylem niczego podejzanego (ale obserwuje go tylko 1/2 godziny).
>
> Ponizej zamieszczam, co mi syslog powiedzial:
>
> kernel: Unable to handle kernel paging request at virtual address 00004004
> kernel: printing eip:
> kernel: c0135ed3
> kernel: *pde = 00000000
> kernel: Oops: 0002 [#1]
> kernel: PREEMPT
> kernel: Modules linked in: ipv6 pcspkr tsdev mousedev evdev psmouse
> analog floppy parport_pc parport snd_intel8x0 snd_ac97_codec snd_pcm
> snd_timer snd_page_alloc gameport snd_mpu401_uart snd_rawmidi
> snd_seq_device snd pci_hotplug intel_agp uhci_hcd usbcore i810_audio
> ac97_codec soundcore piix 3c59x agpgart capability commoncap w83781d
> i2c_sensor i2c_i801 i2c_core ide_cd ide_core cdrom genrtc ext2 ext3
> jbd mbcache sd_mod gdth scsi_mod unix font vesafb cfbcopyarea
> cfbimgblt cfbfillrect
> kernel: CPU: 0
> kernel: EIP: 0060:[find_get_page+51/96] Not tainted
> kernel: EFLAGS: 00010006 (2.6.8-1-686)
> kernel: EIP is at find_get_page+0x33/0x60
> kernel: eax: 00004000 ebx: 00004000 ecx: f7b3b100 edx: 00000000
> kernel: esi: cd82e000 edi: 00000000 ebp: eb39c6fc esp: cd82fccc
> kernel: ds: 007b es: 007b ss: 0068
> kernel: Process clamscan (pid: 25357, threadinfo=cd82e000 task=f7830330)
> kernel: Stack: f7b3b180 0007595a f7b3b17c 0007595a c01561db f7b3b17c
> 0007595a 0000018b
> kernel: 00000000 f08ae128 00000001 00000000 f7b3b0e4 00001000
> 00000000 e81d4794
> kernel: eb39c6fc c01577a9 f7b3b080 0007595a 00000000 00000000
> 00001000 c0157db7
> kernel: Call Trace:
> kernel: [__find_get_block_slow+75/384] __find_get_block_slow+0x4b/0x180
> kernel: [unmap_underlying_metadata+41/112] unmap_underlying_metadata+0x29/0x70
> kernel: [__block_prepare_write+583/1056] __block_prepare_write+0x247/0x420
> kernel: [block_prepare_write+52/80] block_prepare_write+0x34/0x50
> kernel: [__crc_xfrm_state_alloc+4296573/4557196] ext3_get_block+0x0/0xc0 [ext3]
> kernel: [__crc_xfrm_state_alloc+4296573/4557196] ext3_get_block+0x0/0xc0 [ext3]
> kernel: [__crc_xfrm_state_alloc+4298205/4557196]
> ext3_prepare_write+0x70/0x140 [ext3]
> kernel: [__crc_xfrm_state_alloc+4296573/4557196] ext3_get_block+0x0/0xc0 [ext3]
> kernel: [add_to_page_cache+104/176] add_to_page_cache+0x68/0xb0
> kernel: [generic_file_aio_write_nolock+969/2912]
> generic_file_aio_write_nolock+0x3c9/0xb60
> kernel: [update_atime+154/224] update_atime+0x9a/0xe0
> kernel: [__generic_file_aio_read+514/576] __generic_file_aio_read+0x202/0x240
> kernel: [file_read_actor+0/240] file_read_actor+0x0/0xf0
> kernel: [generic_file_aio_write+120/176] generic_file_aio_write+0x78/0xb0
> kernel: [__crc_xfrm_state_alloc+4287217/4557196]
> ext3_file_write+0x44/0xd0 [ext3]
> kernel: [do_sync_write+128/176] do_sync_write+0x80/0xb0
> kernel: [do_mmap_pgoff+1440/1792] do_mmap_pgoff+0x5a0/0x700
> kernel: [vfs_write+237/352] vfs_write+0xed/0x160
> kernel: [sys_write+81/128] sys_write+0x51/0x80
> kernel: [syscall_call+7/11] syscall_call+0x7/0xb
> kernel: Code: ff 40 04 fb ff 4e 14 8b 46 08 a8 08 75 0e 89 d8 8b 74 24 0c
> kernel: <6>note: clamscan[25357] exited with preempt_count 1
> kernel: bad: scheduling while atomic!
> kernel: [schedule+1221/1232] schedule+0x4c5/0x4d0
> kernel: [unmap_page_range+83/128] unmap_page_range+0x53/0x80
> kernel: [unmap_vmas+438/464] unmap_vmas+0x1b6/0x1d0
> kernel: [exit_mmap+132/368] exit_mmap+0x84/0x170
> kernel: [mmput+101/144] mmput+0x65/0x90
> kernel: [do_exit+348/1056] do_exit+0x15c/0x420
> kernel: [do_page_fault+0/1389] do_page_fault+0x0/0x56d
> kernel: [die+249/256] die+0xf9/0x100
> kernel: [do_page_fault+478/1389] do_page_fault+0x1de/0x56d
> kernel: [__crc_xfrm_state_alloc+4309517/4557196]
> ext3_mark_inode_dirty+0x50/0x60 [ext3]
> kernel: [__crc_xfrm_state_alloc+4295506/4557196]
---
ciach
>
> Cos mam przeczucie, ze cos sie ze sprzetem dzieje. Spotkal sie moze
> juz z czyms takim?
>
> Zycze przyjemnego weekendu
>
> Wojtek
>
Witam,
coś podobnego mi się działo jak poleciała mi pamięć w serwerze (HP Compaq Proliant ML350).
A dokładniej jedna z kości - po wyjęciu wadliwej na drugiej ruszał bez błędu.
Pozdrawiam
--
Jerzy <sm0q> Patraszewski
patrasze{at}wszib{dot}edu{dot}pl
sm0q{at}rootshell{dot}be
Reply to: