[EMAIL PROTECTED] wrote:
> On Mon, 24 Sep 2001 20:41:03 +0400
> "Vladimir V. Saveliev" <[EMAIL PROTECTED]> wrote:
>
> > If you ./configure again - does it oops?
> > If yes - can you please ksymoops(8) the dump?
>
> it does oops, and in the same place, everytime.
>
> where is the dump?
>
Do you see something like the below:
Aug 29 09:51:01 blizard kernel: Unable to handle kernel paging request at
virtual address f15e97cc
Aug 29 09:51:01 blizard kernel: current->tss.cr3 = 0062d000, %cr3 =
0062d000
Aug 29 09:51:01 blizard kernel: *pde = 00000000
Aug 29 09:51:01 blizard kernel: Oops: 0002
Aug 29 09:51:01 blizard kernel: CPU: 0
Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
Aug 29 09:51:01 blizard kernel: EFLAGS: 00010212
Aug 29 09:51:01 blizard kernel: eax: 315e97cc ebx: 003a6f80 ecx:
001be77b edx: 00237c0c
Aug 29 09:51:01 blizard kernel: esi: 00000000 edi: bffffdb3 ebp:
00589f90 esp: 00589f8c
Aug 29 09:51:01 blizard kernel: ds: 0018 es: 0018 fs: 002b gs:
002b ss: 0018
Aug 29 09:51:01 blizard kernel: Process oops_test (pid: 3374, process nr:
21, stackpage=00589000)
Aug 29 09:51:01 blizard kernel: Stack: 315e97cc 00589f98 0100b0b4
bffffed4 0012e38e 00240c64 003a6f80 00000001
Aug 29 09:51:01 blizard kernel: 00000000 00237810 bfffff00
0010a7fa 00000003 00000001 00000000 bfffff00
Aug 29 09:51:01 blizard kernel: bffffdb3 bffffed4 ffffffda
0000002b 0007002b 0000002b 0000002b 00000036
Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80]
[_sys_ioctl+254/272] [_system_call+82/128]
Aug 29 09:51:01 blizard kernel: Code: c7 00 05 00 00 00 eb 08 90 90 90 90
90 90 90 90 89 ec 5d c3
>
> could it be from bad blocks in the hard disk, it is an old one anyway.
>
There are a lot of reasons for Oops, without the trace I am not sure what
did cause it in your case. You may check your harddrive with
badblocks(8), though
Thanks,
vs
