From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 5 Oct 2002 03:43:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 5 Oct 2002 03:43:25 -0400 Received: from mta03ps.bigpond.com ([144.135.25.135]:1223 "EHLO mta03ps.bigpond.com") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Sat, 5 Oct 2002 03:43:23 -0400 Content-Type: text/plain; charset=US-ASCII From: Srihari Vijayaraghavan To: linux-kernel@vger.kernel.org Subject: Re: Linux-2.4.20-pre8-aa2 oops report. Date: Sat, 5 Oct 2002 17:55:01 +1000 User-Agent: KMail/1.4.3 References: <200210051247.14368.harisri@bigpond.com> <200210051309.45092.harisri@bigpond.com> In-Reply-To: <200210051309.45092.harisri@bigpond.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: <200210051755.01256.harisri@bigpond.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 05 October 2002 13:09, Srihari Vijayaraghavan wrote: > On Saturday 05 October 2002 12:47, Srihari Vijayaraghavan wrote: > > [1.] One line summary of the problem: > > 2.4.20-pre8aa2 Kernel oopsed couple of times. I was able to produce couple of more oops. ksymoops 2.4.5 on i686 2.4.20-pre8aa2. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20-pre8aa2/ (default) -m /boot/System.map-2.4.20-pre8aa2 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. ac97_codec: AC97 Audio codec, id: v9(SigmaTel STAC9721/23) Unable to handle kernel paging request at virtual address c5db0034 c0114517 *pde = 05c001e3 Oops: 0000 2.4.20-pre8aa2 #3 Thu Oct 3 21:07:54 EST 2002 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00013086 eax: 00000000 ebx: c665b324 ecx: c5db0000 edx: c665b324 esi: c665b31c edi: c01e6ae2 ebp: 00003246 esp: c73b1d90 ds: 0018 es: 0018 ss: 0018 Process modprobe (pid: 1012, stackpage=c73b1000) Stack: c73b0000 00000002 c66fc000 c73b0000 c0113e82 c01e6ae2 c73b1dfc c73b1f6c c3e27f8e c73b0000 00000000 c17e17c0 c016e94f c3e0cf80 d90e1390 0001ff9d c02102ef 00000000 dffcb5f4 da33f340 dffcb580 c3e0cf80 c016f2d4 d90e1390 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 8b 51 34 85 d2 74 3f f7 41 14 41 00 00 00 74 36 8b 71 38 89 >>EIP; c0114517 <===== >>ebx; c665b324 <[emu10k1].data.end+88bb25/8a4881> >>ecx; c5db0000 <[soundcore].bss.end+39889d/3a891d> >>edx; c665b324 <[emu10k1].data.end+88bb25/8a4881> >>esi; c665b31c <[emu10k1].data.end+88bb1d/8a4881> >>edi; c01e6ae2 >>ebp; 00003246 Before first symbol >>esp; c73b1d90 Trace; c0113e82 Trace; c01e6ae2 Trace; c016e94f Trace; c016f2d4 Trace; c016811f Trace; c0113c60 Trace; c0108ff0 Trace; c01e6ae2 Trace; c0127d19 Trace; c012860f Trace; c0113e0a Trace; c0128e88 Trace; c013b2cc Trace; c0129e9f Trace; c012a1d2 Trace; c012a254 Trace; c0113c60 Trace; c0108ff0 Code; c0114517 00000000 <_EIP>: Code; c0114517 <===== 0: 8b 51 34 mov 0x34(%ecx),%edx <===== Code; c011451a 3: 85 d2 test %edx,%edx Code; c011451c 5: 74 3f je 46 <_EIP+0x46> Code; c011451e 7: f7 41 14 41 00 00 00 testl $0x41,0x14(%ecx) Code; c0114525 e: 74 36 je 46 <_EIP+0x46> Code; c0114527 10: 8b 71 38 mov 0x38(%ecx),%esi Code; c011452a 13: 89 00 mov %eax,(%eax) 1 warning issued. Results may not be reliable. ksymoops 2.4.5 on i686 2.4.20-pre8aa2. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20-pre8aa2/ (default) -m /boot/System.map-2.4.20-pre8aa2 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. ac97_codec: AC97 Audio codec, id: v9(SigmaTel STAC9721/23) Unable to handle kernel paging request at virtual address c2d68358 c014e0f9 *pde = 0823c163 Oops: 0003 2.4.20-pre8aa2 #3 Thu Oct 3 21:07:54 EST 2002 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00210282 eax: c70b7f58 ebx: c70b7f40 ecx: c2d68358 edx: c78bae58 esi: c70b7fac edi: c687801f ebp: 4f55e46f esp: c2545ee0 ds: 0018 es: 0018 ss: 0018 Process pam_timestamp_c (pid: 2001, stackpage=c2545000) Stack: 00200217 c021097c 0001828e c0120b37 c70b7f40 dff200c0 c6878013 0000000c c6878013 c687801f 00000000 c2545f98 c014486b c70b7ec0 c2545f40 c6878013 c0144e94 c70b7ec0 c2545f40 00000000 00000008 00000000 c73f0d00 00000000 Call Trace: [] [] [] [] [] [] [] Code: 89 11 89 40 04 89 43 18 eb cc 89 f0 89 3c 24 83 c0 3c 89 44 >>EIP; c014e0f9 <===== >>eax; c70b7f58 >>ebx; c70b7f40 >>ecx; c2d68358 <[serial].bss.end+76be75/182bb9d> >>edx; c78bae58 >>esi; c70b7fac >>edi; c687801f >>ebp; 4f55e46f Before first symbol >>esp; c2545ee0 <[floppy].bss.end+2184a5/24e645> Trace; c0120b37 Trace; c014486b Trace; c0144e94 Trace; c0145377 Trace; c0145609 <__user_walk+49/60> Trace; c014204f Trace; c0108eff Code; c014e0f9 00000000 <_EIP>: Code; c014e0f9 <===== 0: 89 11 mov %edx,(%ecx) <===== Code; c014e0fb 2: 89 40 04 mov %eax,0x4(%eax) Code; c014e0fe 5: 89 43 18 mov %eax,0x18(%ebx) Code; c014e101 8: eb cc jmp ffffffd6 <_EIP+0xffffffd6> Code; c014e103 a: 89 f0 mov %esi,%eax Code; c014e105 c: 89 3c 24 mov %edi,(%esp,1) Code; c014e108 f: 83 c0 3c add $0x3c,%eax Code; c014e10b 12: 89 44 00 00 mov %eax,0x0(%eax,%eax,1) 1 warning issued. Results may not be reliable. Steps to reproduce: 1. Login to XFree86/KDE or GNOME 2. Start some open-source heavy-weight applications (I use Mozilla, Open Office Writer and Calc and Impress) 3. Exit all those applications 4. # mke2fs -j /dev/md0 (or) mke2fs -j /dev/hdc5 5. # mount /dev/md0 /md0 6. # cd /md0 7. # time dd if=/dev/zero of=zero bs=1024 count=1048576 (I have choosen 1 GB file because I have 512 MB RAM in the system) 8. # dmesg (to verify if there is an oops) 9. Repeat step 2 and verify if there is an oops 10. Else repeat steps 1 to 9 couple of times Intrestingly both mainline (2.4.20-pre8) and Red Hat 8 kernel (2.4.18-14) do not exhibit this regression (on few attempts). Please feel free to suggest any ideas to pinpoint the issue if you can. I will test the system with ReiserFS and Debian Woody (gcc 2.95.4) later today or tomorrow. -- Hari harisri@bigpond.com