From owner-kdb@oss.sgi.com Mon Nov 5 17:59:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA61x7k00628 for kdb-outgoing; Mon, 5 Nov 2001 17:59:07 -0800 Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA61x3000625 for ; Mon, 5 Nov 2001 17:59:03 -0800 Received: (qmail 22839 invoked from network); 6 Nov 2001 01:59:01 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 6 Nov 2001 01:59:01 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id CA7E6300095; Tue, 6 Nov 2001 12:58:57 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 5A11096; Tue, 6 Nov 2001 12:58:57 +1100 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: kdb@oss.sgi.com Cc: linux-kernel@vger.kernel.org Subject: Announce: kdb v1.9 is available for kernel 2.4.14 Date: Tue, 06 Nov 2001 12:58:52 +1100 Message-ID: <16200.1005011932@ocs3.intra.ocs.com.au> Sender: owner-kdb@oss.sgi.com Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.9-2.4.14.bz2 Changelog extract. 2001-11-06 Keith Owens * Upgrade to kernel 2.4.14. 2001-11-02 Keith Owens * Sync kdbm_pg.c with XFS. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Exmh version 2.1.1 10/15/1999 iD8DBQE750Pbi4UHNye0ZOoRAgbpAJ9mt6PO1q5nSHl3/tZKaMelRUTFMACeKWAQ ZUBnFEGqK5YL02LLB6HhceI= =YF/P -----END PGP SIGNATURE----- From owner-kdb@oss.sgi.com Tue Nov 6 05:45:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA6DjZU18149 for kdb-outgoing; Tue, 6 Nov 2001 05:45:35 -0800 Received: from gum.csee.uq.edu.au (gum.csee.uq.edu.au [130.102.66.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA6DjS018143 for ; Tue, 6 Nov 2001 05:45:29 -0800 Received: from nut.csee.uq.edu.au (nut.csee.uq.edu.au [130.102.66.13]) by gum.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id fA6DjOk03417 for ; Tue, 6 Nov 2001 23:45:25 +1000 (EST) Received: from mango.csee.uq.edu.au (mango.csee.uq.edu.au [130.102.66.4]) by nut.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id fA6DjOS28757 for ; Tue, 6 Nov 2001 23:45:24 +1000 (EST) Date: Tue, 6 Nov 2001 23:45:24 +1000 (EST) From: Chris Pascoe X-X-Sender: chrisp@mango.csee.uq.edu.au To: kdb@oss.sgi.com Subject: what's going on in this trace? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 1.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-kdb@oss.sgi.com Precedence: bulk Hi, I was wondering if you could make any sense of the following trace, taken after the machine crashed (hangs at checking root filesystem, then eventually runs out of memory and panics 2.4.9-13XFS_PR1 enterprise kernel, with aacraid driver which has intermittent problems). In particular, what's happened after (before?) the interrupt handler - any way to find out, or does it look like something's walked over the stack? (extract from ps). 0xf69d6000 00000068 00000067 0 001 stop 0xf69d6360 fsck.ext2 [0]kdb> btp 68 EBP EIP Function(args) 0xf69d3e0c 0xc0118421 schedule+0x485 (0xc1ee0230) kernel .text 0xc0100000 0xc0117f9c 0xc011863c 0xc012da48 __lock_page+0x90 (0xc1ee0230) kernel .text 0xc0100000 0xc012d9b8 0xc012da74 0xc012da8b lock_page+0x17 (0xc1ee0230) kernel .text 0xc0100000 0xc012da74 0xc012da90 0xc012efdc filemap_nopage+0x358 (0xf776e4a0, 0x809c000, 0x0) kernel .text 0xc0100000 0xc012ec84 0xc012f174 0xc012ae2e do_no_page+0x8e (0xf74cfd20, 0xf776e4a0, 0x809c000, 0x0, 0xf69cd4e0) kernel .text 0xc0100000 0xc012ada0 0xc012af04 0xc012af9f handle_mm_fault+0x9b (0xf74cfd20, 0xf776e4a0, 0x809c4f0, 0x0) kernel .text 0xc0100000 0xc012af04 0xc012b068 0xc0117367 do_page_fault+0x1af (0xf69d3fc4, 0x4, 0x1, 0x0, 0x0) kernel .text 0xc0100000 0xc01171b8 0xc01177a0 0xc0107190 error_code+0x38 kernel .text 0xc0100000 0xc0107158 0xc0107198 Interrupt registers: eax = 0xbffffb20 ebx = 0x00000001 ecx = 0x00000000 edx = 0x00000000 esi = 0xbffffd74 edi = 0x00000003 esp = 0xbffffafc eip = 0x0809c4f0 ebp = 0xbffffd08 xss = 0x0000002b xcs = 0x00000023 eflags = 0x00010292 xds = 0x0000002b xes = 0x0000002b origeax = 0xffffffff ®s = 0xf69d3fc4 [0]more> 0x0809c4f0 +0x809c4f0 kernel 0x0 0x0 0x0 0x00000023 +0x23 kernel 0x0 0x0 0x0 0x00010292 +0x10292 kernel 0x0 0x0 0x0 0xbffffafc +0xbffffafc kernel 0x0 0x0 0x0 0x0000002b +0x2b kernel 0x0 0x0 0x0 0x000081a4 +0x81a4 kernel 0x0 0x0 0x0 0x00001aa4 +0x1aa4 kernel 0x0 0x0 0x0 0x3b135953 +0x3b135953 kernel 0x0 0x0 0x0 0x3b13521b +0x3b13521b kernel 0x0 0x0 0x0 0x3b13521b +0x3b13521b kernel 0x0 0x0 0x0 Thanks, Chris From owner-kdb@oss.sgi.com Tue Nov 6 06:48:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA6Em9j20411 for kdb-outgoing; Tue, 6 Nov 2001 06:48:09 -0800 Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA6Em2020405 for ; Tue, 6 Nov 2001 06:48:02 -0800 Received: (qmail 28525 invoked from network); 6 Nov 2001 14:48:00 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 6 Nov 2001 14:48:00 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 2061A300095; Wed, 7 Nov 2001 01:47:57 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id C2AD296; Wed, 7 Nov 2001 01:47:57 +1100 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Chris Pascoe Cc: kdb@oss.sgi.com Subject: Re: what's going on in this trace? In-reply-to: Your message of "Tue, 06 Nov 2001 23:45:24 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Nov 2001 01:47:52 +1100 Message-ID: <21159.1005058072@ocs3.intra.ocs.com.au> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 6 Nov 2001 23:45:24 +1000 (EST), Chris Pascoe wrote: >I was wondering if you could make any sense of the following trace, taken >after the machine crashed (hangs at checking root filesystem, then >eventually runs out of memory and panics 2.4.9-13XFS_PR1 enterprise >kernel, with aacraid driver which has intermittent problems). In >particular, what's happened after (before?) the interrupt handler - any >way to find out, or does it look like something's walked over the stack? > >(extract from ps). >0xf69d6000 00000068 00000067 0 001 stop 0xf69d6360 fsck.ext2 > >[0]kdb> btp 68 > EBP EIP Function(args) >0xf69d3e0c 0xc0118421 schedule+0x485 (0xc1ee0230) > kernel .text 0xc0100000 0xc0117f9c 0xc011863c > 0xc012da48 __lock_page+0x90 (0xc1ee0230) > kernel .text 0xc0100000 0xc012d9b8 0xc012da74 > 0xc012da8b lock_page+0x17 (0xc1ee0230) > kernel .text 0xc0100000 0xc012da74 0xc012da90 > 0xc012efdc filemap_nopage+0x358 (0xf776e4a0, 0x809c000, 0x0) > kernel .text 0xc0100000 0xc012ec84 0xc012f174 > 0xc012ae2e do_no_page+0x8e (0xf74cfd20, 0xf776e4a0, 0x809c000, 0x0, 0xf69cd4e0) > kernel .text 0xc0100000 0xc012ada0 0xc012af04 > 0xc012af9f handle_mm_fault+0x9b (0xf74cfd20, 0xf776e4a0, 0x809c4f0, 0x0) > kernel .text 0xc0100000 0xc012af04 0xc012b068 > 0xc0117367 do_page_fault+0x1af (0xf69d3fc4, 0x4, 0x1, 0x0, 0x0) > kernel .text 0xc0100000 0xc01171b8 0xc01177a0 > 0xc0107190 error_code+0x38 > kernel .text 0xc0100000 0xc0107158 0xc0107198 >Interrupt registers: >eax = 0xbffffb20 ebx = 0x00000001 ecx = 0x00000000 edx = 0x00000000 >esi = 0xbffffd74 edi = 0x00000003 esp = 0xbffffafc eip = 0x0809c4f0 >ebp = 0xbffffd08 xss = 0x0000002b xcs = 0x00000023 eflags = 0x00010292 >xds = 0x0000002b xes = 0x0000002b origeax = 0xffffffff ®s = 0xf69d3fc4 >[0]more> > 0x0809c4f0 +0x809c4f0 > kernel 0x0 0x0 0x0 > 0x00000023 +0x23 > kernel 0x0 0x0 0x0 kdb backtrace uses heuristics on ix86 to find the previous caller, this trace has broken the heuristics, so try a manual decode. The stack at interrupt was around 0xf69d3fc4 (®s). 'mds 0xf69d3fc4' and look for reasonable kernel addresses on stack, issue 'mds' (no parameters) until you find a possibility. Then 'bt address' where 'address' is the address of the stack location containing the possible return address. That usually gets the heuristics back in sync. In this case, the trace may not be useful. The code has hung in lock_page and the real question is which task already holds the lock. It might not be this task, it might be another one. From owner-kdb@oss.sgi.com Tue Nov 6 10:05:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA6I5BR00348 for kdb-outgoing; Tue, 6 Nov 2001 10:05:11 -0800 Received: from pigeon.verisign.com (pigeon.verisign.com [65.205.251.71]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA6I53000344 for ; Tue, 6 Nov 2001 10:05:03 -0800 Received: from vhqpostal-gw2.verisign.com (verisign.com [65.205.251.56]) by pigeon.verisign.com (8.9.3/BCH1.7.1) with ESMTP id JAA16599; Tue, 6 Nov 2001 09:56:34 -0800 (PST) From: slurn@verisign.com Received: from slurndal-lnx.verisign.com ([10.25.27.123]) by vhqpostal-gw2.verisign.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VW3FAHTT; Tue, 6 Nov 2001 10:05:11 -0800 Received: by slurndal-lnx.verisign.com; Tue, 6 Nov 2001 10:05:08 -0800 Message-Id: <200111061805.KAA17978@slurndal-lnx.verisign.com> Subject: Re: what's going on in this trace? To: c.pascoe@itee.uq.edu.au (Chris Pascoe) Date: Tue, 6 Nov 2001 10:05:08 -0800 (PST) Cc: kdb@oss.sgi.com In-Reply-To: from "Chris Pascoe" at Nov 06, 2001 11:45:24 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-kdb@oss.sgi.com Precedence: bulk > > Hi, > > I was wondering if you could make any sense of the following trace, taken > after the machine crashed (hangs at checking root filesystem, then > eventually runs out of memory and panics 2.4.9-13XFS_PR1 enterprise > kernel, with aacraid driver which has intermittent problems). In > particular, what's happened after (before?) the interrupt handler - any > way to find out, or does it look like something's walked over the stack? The portion of the stack prior to the invocation of 'error_code' is user-mode stack; the bt command won't do user stacks because it doesn't have the symbol information for the executable (and there are numerous issues around making paged-out user-mode stack pages available in kdb). Like Keith says, you need to find out who owns the page lock. But it is likely that even knowing that won't point to the root cause, which is why fsck needs so much memory; either you're checking a _very_ large filesystem, or the filesystem is broken. If you want to determine what is going on in the user-mode stack, you can do that carefully by starting with the eip (0x0809c4f0) and starting gdb on fsck.ext2 then disassembling at 0x0809c4f0. It appears that the instruction at 0x0809c4f0 is generating a page fault and the system hangs while attempting to service it; it is likely to be a mmap'ed area. You'll need to manually trace the user-mode stack based on the interrupt EIP and ESP (and possibly ebp; depending on whether or not fsck.ext2 was compiled with the no_frame_ptr option). scott > > (extract from ps). > 0xf69d6000 00000068 00000067 0 001 stop 0xf69d6360 fsck.ext2 > > [0]kdb> btp 68 > EBP EIP Function(args) > 0xf69d3e0c 0xc0118421 schedule+0x485 (0xc1ee0230) > kernel .text 0xc0100000 0xc0117f9c 0xc011863c > 0xc012da48 __lock_page+0x90 (0xc1ee0230) > kernel .text 0xc0100000 0xc012d9b8 0xc012da74 > 0xc012da8b lock_page+0x17 (0xc1ee0230) > kernel .text 0xc0100000 0xc012da74 0xc012da90 > 0xc012efdc filemap_nopage+0x358 (0xf776e4a0, 0x809c000, 0x0) > kernel .text 0xc0100000 0xc012ec84 0xc012f174 > 0xc012ae2e do_no_page+0x8e (0xf74cfd20, 0xf776e4a0, 0x809c000, 0x0, 0xf69cd4e0) > kernel .text 0xc0100000 0xc012ada0 0xc012af04 > 0xc012af9f handle_mm_fault+0x9b (0xf74cfd20, 0xf776e4a0, 0x809c4f0, 0x0) > kernel .text 0xc0100000 0xc012af04 0xc012b068 > 0xc0117367 do_page_fault+0x1af (0xf69d3fc4, 0x4, 0x1, 0x0, 0x0) > kernel .text 0xc0100000 0xc01171b8 0xc01177a0 > 0xc0107190 error_code+0x38 > kernel .text 0xc0100000 0xc0107158 0xc0107198 > Interrupt registers: > eax = 0xbffffb20 ebx = 0x00000001 ecx = 0x00000000 edx = 0x00000000 > esi = 0xbffffd74 edi = 0x00000003 esp = 0xbffffafc eip = 0x0809c4f0 > ebp = 0xbffffd08 xss = 0x0000002b xcs = 0x00000023 eflags = 0x00010292 > xds = 0x0000002b xes = 0x0000002b origeax = 0xffffffff ®s = 0xf69d3fc4 > [0]more> > 0x0809c4f0 +0x809c4f0 > kernel 0x0 0x0 0x0 > 0x00000023 +0x23 > kernel 0x0 0x0 0x0 > 0x00010292 +0x10292 > kernel 0x0 0x0 0x0 > 0xbffffafc +0xbffffafc > kernel 0x0 0x0 0x0 > 0x0000002b +0x2b > kernel 0x0 0x0 0x0 > 0x000081a4 +0x81a4 > kernel 0x0 0x0 0x0 > 0x00001aa4 +0x1aa4 > kernel 0x0 0x0 0x0 > 0x3b135953 +0x3b135953 > kernel 0x0 0x0 0x0 > 0x3b13521b +0x3b13521b > kernel 0x0 0x0 0x0 > 0x3b13521b +0x3b13521b > kernel 0x0 0x0 0x0 > > > Thanks, > Chris > From owner-kdb@oss.sgi.com Tue Nov 6 16:34:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA70YJI18243 for kdb-outgoing; Tue, 6 Nov 2001 16:34:19 -0800 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA70YI018240 for ; Tue, 6 Nov 2001 16:34:18 -0800 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id fA70YDT14883 for ; Tue, 6 Nov 2001 16:34:13 -0800 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id fA70XB410043810; Tue, 6 Nov 2001 16:33:11 -0800 (PST) Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 636CB3000AE; Wed, 7 Nov 2001 10:41:25 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id EB01B96; Wed, 7 Nov 2001 10:41:25 +1100 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: slurn@verisign.com Cc: c.pascoe@itee.uq.edu.au (Chris Pascoe), kdb@oss.sgi.com Subject: Re: what's going on in this trace? In-reply-to: Your message of "Tue, 06 Nov 2001 10:05:08 -0800." <200111061805.KAA17978@slurndal-lnx.verisign.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Nov 2001 10:41:20 +1100 Message-ID: <24536.1005090080@ocs3.intra.ocs.com.au> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 6 Nov 2001 10:05:08 -0800 (PST), slurn@verisign.com wrote: >The portion of the stack prior to the invocation of 'error_code' is >user-mode stack; Ugh! I missed the xcs=0x23 in the interrupt registers. Oh well, another special case for kdb to detect and stop the back trace. From owner-kdb@oss.sgi.com Thu Nov 8 05:12:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fA8DCc901797 for kdb-outgoing; Thu, 8 Nov 2001 05:12:38 -0800 Received: from gum.csee.uq.edu.au (gum.csee.uq.edu.au [130.102.66.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fA8DCY001794 for ; Thu, 8 Nov 2001 05:12:35 -0800 Received: from nut.csee.uq.edu.au (nut.csee.uq.edu.au [130.102.66.13]) by gum.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id fA8DCVJ29249 for ; Thu, 8 Nov 2001 23:12:31 +1000 (EST) Received: from mango.csee.uq.edu.au (mango.csee.uq.edu.au [130.102.66.4]) by nut.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id fA8DCVu27959 for ; Thu, 8 Nov 2001 23:12:31 +1000 (EST) Date: Thu, 8 Nov 2001 23:12:31 +1000 (EST) From: Chris Pascoe X-X-Sender: chrisp@mango.csee.uq.edu.au To: kdb@oss.sgi.com Subject: Re: what's going on in this trace? In-Reply-To: <200111061805.KAA17978@slurndal-lnx.verisign.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 1.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-kdb@oss.sgi.com Precedence: bulk Hi Keith, Scott, > Like Keith says, you need to find out who owns the page lock. But it > is likely that even knowing that won't point to the root cause, which > is why fsck needs so much memory; either you're checking a _very_ large > filesystem, or the filesystem is broken. Turning up the console loglevel reveals that the RAID controller is exhibiting broken behaviour - it stops responding to any requests, making it hard for anything that wants to read/write to disk to work. So the lock_page just sits there (I assume in the case where it has to do disk I/O)... All beyond me, so the board designers are looking into it. Thanks for the insight into what was going on in that stack trace, I learn a little bit every dday. Chris From owner-kdb@oss.sgi.com Thu Nov 15 12:13:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fAFKD9N25093 for kdb-outgoing; Thu, 15 Nov 2001 12:13:09 -0800 Received: from dell.ControlLaser.com (mail.controllaser.com [12.38.32.18]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fAFKD6025090 for ; Thu, 15 Nov 2001 12:13:07 -0800 Received: by DELL with Internet Mail Service (5.5.2653.19) id ; Thu, 15 Nov 2001 15:08:59 -0500 Message-ID: <4AB7D8719A7FD41191200090276DC943040CF9@DELL> From: Bob Cliborn To: "'kdb@oss.sgi.com'" Subject: SUSE 7.3 Date: Thu, 15 Nov 2001 15:07:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kdb@oss.sgi.com Precedence: bulk I just purchased SUSE 7.3 kernel 2.4-10-4GB. I've downloaded what I thought was the latest patch. I get patch mismatches in config.in of the 386 directory and Makefile. I assume the patches must work flawlessly to be able to recompile the kernel successfully. I checked the FAQ and previous news. Any suggestions? From owner-kdb@oss.sgi.com Thu Nov 15 13:13:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fAFLD5H27284 for kdb-outgoing; Thu, 15 Nov 2001 13:13:05 -0800 Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fAFLD1027281 for ; Thu, 15 Nov 2001 13:13:02 -0800 Received: (qmail 9657 invoked from network); 15 Nov 2001 21:12:59 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 15 Nov 2001 21:12:59 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 95712300095; Fri, 16 Nov 2001 08:12:57 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 876B596; Fri, 16 Nov 2001 08:12:57 +1100 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Bob Cliborn Cc: "'kdb@oss.sgi.com'" Subject: Re: SUSE 7.3 In-reply-to: Your message of "Thu, 15 Nov 2001 15:07:53 CDT." <4AB7D8719A7FD41191200090276DC943040CF9@DELL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Nov 2001 08:12:52 +1100 Message-ID: <14114.1005858772@ocs3.intra.ocs.com.au> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Thu, 15 Nov 2001 15:07:53 -0500, Bob Cliborn wrote: >I just purchased SUSE 7.3 kernel 2.4-10-4GB. > >I've downloaded what I thought was the latest patch. I get patch mismatches >in config.in of the 386 directory and Makefile. I assume the patches must >work flawlessly to be able to recompile the kernel successfully. > >I checked the FAQ and previous news. > >Any suggestions? Ask SuSe for help. They have applied their own patches to the standard kernel which is preventing the kdb patch from applying. kdb tracks Linus's and Alan COx's kernels, not kernels that have beem patched by distributors. From owner-kdb@oss.sgi.com Tue Nov 20 15:13:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fAKNDtw08103 for kdb-outgoing; Tue, 20 Nov 2001 15:13:55 -0800 Received: from isis.cs3-inc.com (isis.cs3-inc.com [207.224.119.73]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fAKNDro08096 for ; Tue, 20 Nov 2001 15:13:53 -0800 Received: (from don@localhost) by isis.cs3-inc.com (8.11.0/8.11.0) id fAKM7Fp20755 for kdb@oss.sgi.com; Tue, 20 Nov 2001 14:07:15 -0800 Date: Tue, 20 Nov 2001 14:07:15 -0800 Message-Id: <200111202207.fAKM7Fp20755@isis.cs3-inc.com> X-Authentication-Warning: isis.cs3-inc.com: don set sender to don-cs3 using -f X-Authentication-Warning: isis.cs3-inc.com: Processed from queue /var/spool/mqueue X-Authentication-Warning: isis.cs3-inc.com: Processed by don with -C /etc/sendmail.cf From: don-cs3@isis.cs3-inc.com (Don Cohen) To: kdb@oss.sgi.com Subject: advice on download Sender: owner-kdb@oss.sgi.com Precedence: bulk The files I find at ftp://oss.sgi.com/www/projects/kdb/download/ix86/ are all .bz2 and yet when I try tar xvfI kdb-v1.9-2.4.14.bz2 I get tar: This does not look like a tar archive tar: Skipping to next header tar: 418 garbage bytes ignored at end of archive tar: Error exit delayed from previous errors What should I do? From owner-kdb@oss.sgi.com Tue Nov 20 15:39:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fAKNd8L09493 for kdb-outgoing; Tue, 20 Nov 2001 15:39:08 -0800 Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fAKNd4o09490 for ; Tue, 20 Nov 2001 15:39:05 -0800 Received: (qmail 3307 invoked from network); 20 Nov 2001 22:39:00 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 20 Nov 2001 22:39:00 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id EB9E6300090; Wed, 21 Nov 2001 09:38:56 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 84DC996; Wed, 21 Nov 2001 09:38:56 +1100 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: don-cs3@isis.cs3-inc.com (Don Cohen) Cc: kdb@oss.sgi.com Subject: Re: advice on download In-reply-to: Your message of "Tue, 20 Nov 2001 14:07:15 -0800." <200111202207.fAKM7Fp20755@isis.cs3-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Nov 2001 09:38:51 +1100 Message-ID: <31585.1006295931@ocs3.intra.ocs.com.au> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 20 Nov 2001 14:07:15 -0800, don-cs3@isis.cs3-inc.com (Don Cohen) wrote: >The files I find at >ftp://oss.sgi.com/www/projects/kdb/download/ix86/ >are all .bz2 and yet when I try > tar xvfI kdb-v1.9-2.4.14.bz2 >I get > tar: This does not look like a tar archive Just use bunzip2, these are plain patch files that have been bzipped, they are not tar archives. From owner-kdb@oss.sgi.com Thu Nov 29 00:58:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fAT8wND05351 for kdb-outgoing; Thu, 29 Nov 2001 00:58:23 -0800 Received: from web20103.mail.yahoo.com (web20103.mail.yahoo.com [216.136.226.40]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fAT8wJo05348 for ; Thu, 29 Nov 2001 00:58:19 -0800 Message-ID: <20011129075818.86015.qmail@web20103.mail.yahoo.com> Received: from [132.233.247.23] by web20103.mail.yahoo.com via HTTP; Thu, 29 Nov 2001 07:58:18 GMT Date: Thu, 29 Nov 2001 07:58:18 +0000 (GMT) From: =?iso-8859-1?q?duan=20jiangang?= Subject: reboot when press go To: kdb@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-kdb@oss.sgi.com Precedence: bulk 1. These days I am studying the exception handler with kdb. I add some breakpoints into the kernel code, press "go" and result in the machine reboot. The detailed steps are listed as below: 1. enter KDB mode. 2. id divide_error The ASM codes on my screen are: 0xc010926c divide_errorpush $0x0 0xc010926e divide_error+0x2push $0xc0109890 ... 0xc01092a4 error_code+0x30and %esp,%ebx 0xc01092a6 error_code+0x32call *%edi ... 3. bp 0xc01092a6 /* the call instruction */ 4. go I run this test on my p4 and p3 machines with kernel 2.4.2 and 2.4.14 with corresponding KDB patch. The results are same: reboot. Is it a bug? 2. I test bph command as below: bph testkdbbph datar /*testkdbbph is a variant name in one of my own module*/ then press go; I call some function in my own module to modify the testkdbbph value and expect the breakpoint invoked. But no response, why? Thanks. jiangang