Re: unable to handle paging request (kernel 2.2.10)

Peter Hanecak (hany@megaloman.sk)
Tue, 3 Aug 1999 15:23:30 +0200 (CEST)


On Wed, 14 Jul 1999, Stephen C. Tweedie wrote:

> > i occasionaly get "unable to handle kernel paging request" kernel error.
>
> Can you reproduce this on 2.2.10ac10? We've had a couple of problems in
> 2.2.9/10 which are fixed in that patch.

i goess throug 2.2.10ac10 to current 2.2.10ac12 and my batch picture
convertor (as mentioned in my other posts) still leads to system crash.

latest message (when running job from my local CD-ROM copying files to NFS
filesystem and converting them there):

Aug 3 13:38:05 m1 kernel: Unable to handle kernel paging request at
virtual address 10000000
Aug 3 13:38:05 m1 kernel: current->tss.cr3 = 06a6b000, %cr3 = 06a6b000
Aug 3 13:38:05 m1 kernel: *pde = 00000000
Aug 3 13:38:05 m1 kernel: Oops: 0000
Aug 3 13:38:05 m1 kernel: CPU: 0
Aug 3 13:38:05 m1 kernel: EIP: 0010:[find_buffer+40/76]
Aug 3 13:38:05 m1 kernel: EFLAGS: 00010206
Aug 3 13:38:05 m1 kernel: eax: 10000000 ebx: 0000a8d2 ecx: 00000340
edx: 10000000
Aug 3 13:38:05 m1 kernel: esi: 00000800 edi: 000000cc ebp: c108d200
esp: c6af1e48
Aug 3 13:38:05 m1 kernel: ds: 0018 es: 0018 ss: 0018
Aug 3 13:38:05 m1 kernel: Process cp (pid: 1441, process nr: 37,
stackpage=c6af1000)
Aug 3 13:38:05 m1 kernel: Stack: c012500b 00000340 0000a8d2 00000800
c0125de8 00000340 0000a8d2 00000800
Aug 3 13:38:05 m1 kernel: 00000000 c6af1eec 000000cc c5689870
00000000 c68e1000 c3c53000 00000340
Aug 3 13:38:05 m1 kernel: 00000000 c108d200 00000000 c108d140
c108d920 00000000 00000000 c0164b2c
Aug 3 13:38:05 m1 kernel: Call Trace: [get_hash_table+23/36]
[brw_page+332/880] [sync_cluster+168/252] [generic_readpage+
129/144] [try_to_read_ahead+266/288] [do_generic_file_read+758/1508]
[generic_file_read+99/124]
Aug 3 13:38:05 m1 kernel: [file_read_actor+0/80]
[sys_read+174/196] [system_call+52/56]

X windows crashed, system works but i rebooted it while earlier it
completely locks up machine after aditional time.

whe shuting down, file-systems were not unmounted properly because they
were busy.

sincerely

peter hanecak

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/