[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-security
Subject:    Re: [suse-security] Kernel Problem or Hacked?
From:       Markus Gaugusch <markus () gaugusch ! dhs ! org>
Date:       2000-10-31 5:13:24
[Download RAW message or body]

On Mon, 30 Oct 2000, Boris Kantwerk wrote:
> Oct 30 00:00:54 server kernel: kfree: Bad obj c053a300
> Oct 30 00:00:54 server kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Oct 30 00:00:54 server kernel: current->tss.cr3 = 00bd8000, %%cr3 = 00bd8000
> Oct 30 00:00:54 server kernel: *pde = 00000000
> Oct 30 00:00:54 server kernel: Oops: 0002
> Oct 30 00:00:54 server kernel: CPU:    0
> Oct 30 00:00:54 server kernel: EIP:    0010:[kfree+475/496]
> Oct 30 00:00:54 server kernel: EFLAGS: 00010282
> Oct 30 00:00:54 server kernel: eax: 0000001b   ebx: c1fff620   ecx: 0000003b
> edx: 00000028
> Oct 30 00:00:54 server kernel: esi: c053a300   edi: c053aaa0   ebp: 00000000
> esp: c0babe64
> Oct 30 00:00:54 server kernel: ds: 0018   es: 0018   ss: 0018
> Oct 30 00:00:54 server kernel: Process find (pid: 19826, process nr: 53,
> stackpage=c0bab000)
> Oct 30 00:00:54 server kernel: Stack: c1fa71e0 00000000 c053aaa0 00000000
> c053aac0 c0744450 c053aaa0 c0134562
> Oct 30 00:00:54 server kernel:        c053a300 c0babec0 00009803 00000405
> c1fb1000 00000405 c01356bc fffffdd3
> Oct 30 00:00:54 server kernel:        000001e8 c0208eb8 00009803 c0229188
> c1fb1000 c09db5d0 c07e4000 c0babec0
> Oct 30 00:00:54 server kernel: Call Trace: [prune_dcache+210/288]
> [try_to_free_inodes+188/256] [grow_inodes+32/416] [get_new_inode+229/336]
> [iget+106/128] [ext2_lookup+100/160] [real_lookup+79/192]
> Oct 30 00:00:54 server kernel:        [lookup_dentry+272/432]
> [__namei+41/96] [sys_newlstat+19/112] [system_call+52/56]
> Oct 30 00:00:54 server kernel: Code: c7 05 00 00 00 00 00 00 00 00 83 c4 08
> 5b 5e 5f 5d 83 c4 0c
You probably have a hardware problem. Maybe CPU is too hot or RAM
defective.
That's definitly NOT a break in... it's caused by the scripts running at
midnight and making CPU too hot or touching 'bad' RAM.

bye
Markus

-- 
_____________________________
Markus Gaugusch  ICQ 11374583
markus@gaugusch.dhs.org
92


[prev in list] [next in list] [prev in thread] [next in thread]