Pad jadra?

[Pavel Kankovsky]

On Tue, 2 May 2000, Petr Stanek wrote:

> Apr 25 04:13:30 penguin kernel: Call Trace: [setup_arg_pages+69/264]
> [load_elf_binary+1314/2576]
> Apr 25 04:13:30 penguin kernel:        [do_execve+417/488]
> [sys_execve+44/100] [system_call+52/56] 
> Apr 25 04:13:30 penguin kernel: Code: 8b 01 89 03 85 c0 74 2c 8b 53 04
> 85 d2 75 13 89 19 89 c8 2b 
> Apr 25 05:13:58 penguin kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Apr 25 05:13:58 penguin kernel: current->tss.cr3 = 0370e000, %cr3 =
> 0370e000
...
> Apr 25 05:13:58 penguin kernel: EIP:    0010:[kmem_cache_alloc+46/288]
....
> Apr 25 05:13:58 penguin kernel: Call Trace: [setup_arg_pages+69/264]
> [load_elf_binary+1314/2576]
> [do_generic_file_read+1353/1364] [cprt+1300/25349]
> [file_read_actor+0/84] [search_binary_handler+60/260]
> [do_execve+384/488] 

Hm. To vypada, jako kdyby to na drzku padalo systematicky kazdou hodinu
(pri kazdem spusteni named-xfer?). Vypada to, jako kdyby byly naborene
slaby (resp. jeden konkretni), protoze to v obou pripadech asi krachnulo
v kmem_cache_alloc. Nelze nez doporucit, abyste vypis namapoval na
zdrojovy kod a otravoval v linux-kernel. :)

--Pavel Kankovsky aka Peak  [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."