This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Jun 11 13:17:37 2024 Received: from lml.valinux.com (postfix@lml.varesearch.com [209.81.8.228]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id JAA18230 for ; Fri, 17 Dec 1999 09:32:38 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id 14E2359AE4; Fri, 17 Dec 1999 06:35:52 -0800 (PST) Received: by vger.rutgers.edu via listexpand id ; Fri, 17 Dec 1999 09:30:23 -0500 Received: by vger.rutgers.edu id ; Fri, 17 Dec 1999 09:23:54 -0500 Received: from eamail1-out.unisys.com ([192.61.61.99]:44928 "EHLO eamail1-out.unisys.com") by vger.rutgers.edu with ESMTP id ; Fri, 17 Dec 1999 09:23:03 -0500 Received: from us-lacd-gtwy-1.ea.unisys.com (us-lacd-gtwy-1.ea.unisys.com [192.61.145.103]) by eamail1-out.unisys.com (8.9.3/8.9.3) with ESMTP id OAA22830; Fri, 17 Dec 1999 14:21:14 GMT Received: by us-lacd-gtwy-1.ea.unisys.com with Internet Mail Service (5.5.2650.21) id ; Fri, 17 Dec 1999 08:21:20 -0600 Message-Id: From: "Leeuw van der, Tim" To: "'Manfred Spraul'" , "'alan@lxorguk.ukuu.org.uk'" Cc: "'linux-kernel@vger.rutgers.edu'" Subject: RE: Oops in 2.2.14pre12 (and 2.2.14pre14, 2.3.33, network related ) Date: Fri, 17 Dec 1999 08:19:37 -0600 Mime-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig I again got an oops, this time in 2.2.14pre14, compiled without any crazy optimizations. I think we have a genuine bug, therefore. Again I was not able to capture my last oops, a lot of critical information had already scrolled off the screen. I don't have a serial cable or a printer available at the moment. I'm sorry. Using pcmcia 3.0.13, compiled with -O2 -m486 (same as the kernel). Lots of network traffic going on: WindowMaker running on laptop with PC as display; several dockapps, browsing internet w/Netscape, compiling kernel (causing lots of xterm updates). The system seems rock stable when I have the X server built in window manager, instead of the remote laptop windowmanager. And once again, the same happened with 2.3.33. Please let me know if there is anything extra that I could do. In the weekend I might have time to hook up a printer. I hope that my repeated messages are not starting to annoy anyone :-) Regards, --Tim Modules I typically have loaded: Module Size Used by af_packet 5980 1 (autoclean) autofs 9156 1 (autoclean) serial_cs 4228 0 (unused) pcnet_cs 8260 1 8390 6420 0 [pcnet_cs] dummy0 908 1 (autoclean) ds 6492 2 [serial_cs pcnet_cs] i82365 23128 2 pcmcia_core 36792 0 [serial_cs pcnet_cs ds i82365] sb 33780 0 (unused) opl3 11432 0 (unused) uart401 6192 0 [sb] sound 57420 0 [sb opl3 uart401] ide-cd 23352 0 (autoclean) soundcore 2596 5 [sb sound] cdrom 13592 0 (autoclean) [ide-cd] isofs 17588 0 (autoclean) nls_iso8859-1 2244 1 (autoclean) nls_cp437 3748 1 (autoclean) > -----Original Message----- > From: Manfred Spraul [mailto:manfreds@colorfullife.com] > Sent: 16 December 1999 22:05 > To: Alan Cox > Cc: Leeuw van der, Tim; 'linux-kernel@vger.rutgers.edu' > Subject: Re: Oops in 2.2.14pre12 > > > I traced the bug back to tcp_transmit_skb(): the function pointer > tp->af_specific->queue_xmit got corrupted, and thus the CPU > jumped to a > bogus address. This caused an oops. The oops code itself triggered > another oops when it tried to dump the code address. > > 1) What about adding safety checks before dereferencing the > EIP pointer? > Everything outside 0xC000 0000 and the end of the normal memory is > obviously wrong.[Add the apropiate macros] > > 2) Do you have any ide what mangled the function pointer? Any critical > changes? > > Tim, did you load/unload any modules immedialy prior to the oops? How > much memory do you have? > -- > Manfred > > "Leeuw van der, Tim" wrote: > > > > Ok, thank's to Manfred I re-decoded the first OOPS that I got! > > I mistook the <> for () - rather silly of me perhaps. But > the output is a > > lot more useful now. > > > > Here comes the oops again: > > > > bonsai:~ # ksymoops -m /boot22/System.map -o > /lib/modules/2.2.14pre12/ -K -L > > < oops.txt > > Options used: -V (default) > > -o /lib/modules/2.2.14pre12/ (specified) > > -K (specified) > > -L (specified) > > -m /boot22/System.map (specified) > > -c 1 (default) > > > > No modules in ksyms, skipping objects > > CPU: 0 > > EIP: 0010:[] > > EFLAGS: 00010046 > > eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c01bf0a8 > > esi: c0100175 edi: c01d0000 ebp: c2800000 esp: c01cfbe4 > > ds: 0018 es: 0018 ss: 0018 > > Process swapper > > Stack: 00000000 c01cfcfc c01ded43 00000246 c1c8da00 > c01cfcfc 00000000 > > c136da20 > > c0e68a2c 0000032f 00000000 00010046 02000000 > c3000000 c01093a4 > > c01cfc68 > > c01a05f8 c01a1d0e 00000000 00000000 c010e7f0 > c01a1d0e c01cfc68 > > 00000000 > > Call Trace: [] [] [] > [] [] > > [] [] > > [] [] [] [] > [] > > [] [] [] > > [] [] [] [] > [] > > [] [] [] > > [] [] [] [] > [] > > [] [] [] > > [] [] [] [] > [] > > [] [] > > Code: 8a 04 0b 89 44 24 38 50 68 f0 05 1a c0 e8 59 a7 00 00 83 c4 > > > > >>EIP: c0109259 > > Trace: c3000000 > > Trace: c01093a4 > > Trace: c01a05f8 > > Trace: c01a1d0e > > Trace: c010e7f0 > > Trace: c01a1d0e > > Trace: c0108ead > > Trace: c2861219 > > Trace: c0164995 > > Trace: c01687c6 > > Trace: c0107609 > > Code: c0109259 00000000 <_EIP>: <=== > > Code: c0109259 0: 8a 04 0b > > mov (%ebx,%ecx,1),%al <=== > > Code: c010925c 3: 89 44 24 38 > > mov %eax,0x38(%esp,1) > > Code: c0109260 7: 50 > > push %eax > > Code: c0109261 8: 68 > f0 05 1a c0 > > push $0xc01a05f0 > > Code: c0109266 d: e8 > 59 a7 00 00 > > call c01139c4 > > Code: c010926b 12: 83 c4 00 > > add $0x0,%esp > > > > Aiee, killing interrupt handler > > Kernel panic: Attempted to kill the idle task! > > In swapper task - not synching > > > - 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/