From owner-kdb@oss.sgi.com Tue Dec 5 10:22:56 2000 Received: by oss.sgi.com id ; Tue, 5 Dec 2000 10:22:37 -0800 Received: from thalia.fm.intel.com ([132.233.247.11]:54028 "EHLO thalia.fm.intel.com") by oss.sgi.com with ESMTP id ; Tue, 5 Dec 2000 10:22:30 -0800 Received: from SMTP (fmsmsxvs02-1.fm.intel.com [132.233.42.202]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.33 2000/11/21 19:27:27 smothers Exp $) with SMTP id SAA02714; Tue, 5 Dec 2000 18:23:30 GMT Received: from fmsmsx18.intel.com ([132.233.48.18]) by 132.233.48.202 (Norton AntiVirus for Internet Email Gateways 1.0) ; Tue, 05 Dec 2000 18:22:11 0000 (GMT) Received: by fmsmsx18.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Dec 2000 10:22:09 -0800 Message-ID: From: "Dunlap, Randy" To: "'Keith Owens'" Cc: kdb@oss.sgi.com Subject: RE: kdb-v1.6 for 2.4.0-test11 ? Date: Tue, 5 Dec 2000 10:20:03 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing > From: Keith Owens [mailto:kaos@melbourne.sgi.com] > > On Mon, 20 Nov 2000 15:28:25 -0800, > Randy Dunlap wrote: > >I'm having compile errors with kdb-v1.6-2.4.0-test11-pre7... > >but I'm trying to use it on 2.4.0-test11. > >I haven't seen any traffic about this. > >Is kdb available for 2.4.0-test11? > > Shortly, once I fix some problems. > > >First error is in arch/kernel/i386/io-apic.c, line 1608, > > x86_capability |= constant; > >needs to be > > x86_capability[0] |= constant; > > - boot_cpu_data.x86_capability |= X86_FEATURE_APIC; > + set_bit(X86_FEATURE_APIC, &boot_cpu_data.x86_capability); Did that. > >After this, arch/i386/kdb/i386-dis.c has a few errors (sample): > > > >gcc -D__KERNEL__ -I/work/linsrc/240-test11/include -Wall > >-Wstrict-prototypes -O2 -fno-strict-aliasing -pipe > -march=i686 -c -o > >i386-dis.o i386-dis.c > >i386-dis.c: In function `print_insn_i386': > >i386-dis.c:2143: `bfd_mach_i386_i386_intel_syntax' > >undeclared (first use in this function) > > Defined in /usr/include/bfd.h, mine is binutils-2.9.5.0.22-6. The > disassembly code in kdb was upgraded to a recent gdb, you > probably need to upgrade binutils. Did that. Is there a kdb that works with test11 or test12-preX? I made the changes above. The test11 and test12-preX kernels build but I get a hang during init (on some kind of parallel port driver init). (Pentium III, UP, 440BX/PIIX4 chipset, IDE drives) Thanks, ~Randy From owner-kdb@oss.sgi.com Wed Dec 6 00:06:21 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 00:06:11 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:7980 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 00:05:50 -0800 Received: from sydney.sydney.sgi.com (sydney.sydney.sgi.com [134.14.48.2]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id AAA06326 for ; Wed, 6 Dec 2000 00:13:57 -0800 (PST) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com by sydney.sydney.sgi.com via ESMTP (950413.SGI.8.6.12/930416.SGI) id TAA08123; Wed, 6 Dec 2000 19:04:24 +1100 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: "Dunlap, Randy" cc: kdb@oss.sgi.com Subject: Re: kdb-v1.6 for 2.4.0-test11 ? In-reply-to: Your message of "Tue, 05 Dec 2000 10:20:03 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 19:04:23 +1100 Message-ID: <8314.976089863@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing On Tue, 5 Dec 2000 10:20:03 -0800 , "Dunlap, Randy" wrote: >Is there a kdb that works with test11 or test12-preX? > >I made the changes above. The test11 and test12-preX kernels >build but I get a hang during init (on some kind of parallel >port driver init). (Pentium III, UP, 440BX/PIIX4 chipset, >IDE drives) With kdb and 2.4.0-test11, NMI for uniprocessor, I am seeing random hangs. It does not occur without NMI for UP. Investigating. From owner-kdb@oss.sgi.com Mon Dec 11 20:23:19 2000 Received: by oss.sgi.com id ; Mon, 11 Dec 2000 20:23:09 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:23605 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Mon, 11 Dec 2000 20:22:53 -0800 Received: from sydney.sydney.sgi.com (sydney.sydney.sgi.com [134.14.48.2]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id UAA08772; Mon, 11 Dec 2000 20:31:07 -0800 (PST) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com by sydney.sydney.sgi.com via ESMTP (950413.SGI.8.6.12/930416.SGI) id PAA10082; Tue, 12 Dec 2000 15:21:34 +1100 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: kdb@oss.sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: [Announce] kdb v1.7 is available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 15:21:34 +1100 Message-ID: <6020.976594894@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing http://oss.sgi.com/projects/kdb/download/ix86/ contains patches for kdb v1.7 against 2.4.0-test11 and 2.4.0-test12. There is a large amount of internal reorganisation from kdb v1.6 to v1.7 to make it easier to support multiple architectures. Most of this is feedback from the kdb for IA64 work in progress. The patch against 2.4.0-test11 fixes the boot hang with NMI for UP. kdb v1.7 contains a new "sections" command. Primarily intended for interfacing to external debuggers such as gdb, its output is not very human readable. From owner-kdb@oss.sgi.com Wed Dec 13 15:59:25 2000 Received: by oss.sgi.com id ; Wed, 13 Dec 2000 15:59:15 -0800 Received: from saltlake.cheek.com ([207.202.196.152]:9223 "EHLO saltlake.cheek.com") by oss.sgi.com with ESMTP id ; Wed, 13 Dec 2000 15:59:01 -0800 Received: from cheek.com (sanfrancisco.cheek.com [207.202.196.153]) by saltlake.cheek.com (8.9.3/8.9.3) with ESMTP id PAA10702 for ; Wed, 13 Dec 2000 15:59:00 -0800 Message-ID: <3A380D32.FA211053@cheek.com> Date: Wed, 13 Dec 2000 15:58:42 -0800 From: Joseph Cheek X-Mailer: Mozilla 4.73C-CCK-MCD Caldera Systems OpenLinux [en] (X11; U; Linux 2.4.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: kdb@oss.sgi.com Subject: kdb 1.5 doesn't compile on linux kernel 2.4.0-test10 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing hi, i know v1.5 and test10 are older versions, but here's a bug report fwiw: make CFLAGS="-D__KERNEL__ -I/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i586 -mcpu=i686 " -C arch/i386/kdb make[1]: Entering directory `/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/arch/i386/kdb' make all_targets make[2]: Entering directory `/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/arch/i386/kdb' gcc -D__KERNEL__ -I/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i586 -mcpu=i686 -c -o kdba_bt.o kdba_bt.c gcc -D__KERNEL__ -I/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i586 -mcpu=i686 -c -o kdba_bp.o kdba_bp.c kdba_bp.c: In function `kdba_db_trap': kdba_bp.c:232: warning: long unsigned int format, different type arg (arg 4) kdba_bp.c: In function `kdba_installbp': kdba_bp.c:710: warning: long unsigned int format, different type arg (arg 3) kdba_bp.c:722: warning: long unsigned int format, different type arg (arg 3) kdba_bp.c: In function `kdba_removebp': kdba_bp.c:758: warning: long unsigned int format, different type arg (arg 3) kdba_bp.c:764: warning: long unsigned int format, different type arg (arg 3) gcc -D__KERNEL__ -I/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i586 -mcpu=i686 -c -o kdba_id.o kdba_id.c kdba_id.c:76: conflicting types for `kdba_printaddress' /usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/include/linux/kdbprivate.h:283: previous declaration of `kdba_printaddress' make[2]: *** [kdba_id.o] Error 1 make[2]: Leaving directory `/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/arch/i386/kdb' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/RedmondLinux/BUILD/linux-2.4.0/linux/arch/i386/kdb' make: *** [_dir_arch/i386/kdb] Error 2 -- thanks! joe -- Joseph Cheek, Sr Linux Consultant, Linuxcare | http://www.linuxcare.com/ Linuxcare. Support for the Revolution. | joseph@linuxcare.com CTO / Acting PM, Redmond Linux Project | joseph@redmondlinux.org 425 990-1072 vox [1074 fax] 206 679-6838 pcs | joseph@cheek.com From owner-kdb@oss.sgi.com Mon Dec 18 00:00:24 2000 Received: by oss.sgi.com id ; Mon, 18 Dec 2000 00:00:14 -0800 Received: from 213-123-74-69.btconnect.com ([213.123.74.69]:23300 "EHLO penguin.homenet") by oss.sgi.com with ESMTP id ; Sun, 17 Dec 2000 23:59:57 -0800 Received: from localhost (tigran@localhost) by penguin.homenet (8.11.0/8.11.0) with ESMTP id eBI81wE01037; Mon, 18 Dec 2000 08:01:58 GMT X-Authentication-Warning: penguin.homenet: tigran owned process doing -bs Date: Mon, 18 Dec 2000 08:01:58 +0000 (GMT) From: Tigran Aivazian X-Sender: tigran@penguin.homenet To: Keith Owens cc: kdb@oss.sgi.com Subject: suggestion: kdb modules to be static. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing Hi Keith, How about changing things so that the kdbm_vm/kdbm_pg (and any future modules) be compiled statically into the kernel? Surely you would agree that the _only_ reason to have them as modules is to be able to enhance kdb "on the fly" on a running system with some exotic custom kernel features with the constraint of not being allowed to reboot. This is probably a real-world situation in 0.0000% of the cases, so I would suggest making them static not just by default but always. But if you disagree, at least making this optional is, without a doubt, a good idea. Regards, Tigran From owner-kdb@oss.sgi.com Wed Dec 20 23:17:34 2000 Received: by oss.sgi.com id ; Wed, 20 Dec 2000 23:17:24 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:50545 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Wed, 20 Dec 2000 23:17:11 -0800 Received: from sydney.sydney.sgi.com ([134.14.48.2]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id XAA03458 for ; Wed, 20 Dec 2000 23:17:05 -0800 (PST) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com by sydney.sydney.sgi.com via ESMTP (950413.SGI.8.6.12/930416.SGI) id SAA10675; Thu, 21 Dec 2000 18:15:43 +1100 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Tigran Aivazian cc: kdb@oss.sgi.com Subject: Re: suggestion: kdb modules to be static. In-reply-to: Your message of "Mon, 18 Dec 2000 08:01:58 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Dec 2000 18:15:43 +1100 Message-ID: <5871.977382943@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing On Mon, 18 Dec 2000 08:01:58 +0000 (GMT), Tigran Aivazian wrote: >How about changing things so that the kdbm_vm/kdbm_pg (and any future >modules) be compiled statically into the kernel? Sorry for the late reply, snowed under with Makefile changes. The aim of kdb/modules is to debug specific areas of the kernel, it is assumed that not everyone is interested in these areas. As such it would be wasteful to include every kdbm object in the kernel when the majority of people are not interested. Having a separate selection for each kdbm object would be messy. Turn on kdb and get multiple "do you want to debug this area of the kernel" options, no thanks. The choice is between (1) Compile everything in. kdb gets bigger and bigger, embedded people start complaining. (2) Config option for every kdbm object. Config option gets longer and longer. (3) Make them modules. Users who need these features can load the objects that they need. kdb currently does (3), the less evil option. From owner-kdb@oss.sgi.com Fri Dec 29 17:38:51 2000 Received: by oss.sgi.com id ; Fri, 29 Dec 2000 17:38:42 -0800 Received: from shasta.villamontage.com ([209.10.215.28]:53001 "EHLO villaex1.villamontage.com") by oss.sgi.com with ESMTP id ; Fri, 29 Dec 2000 17:38:19 -0800 Received: by VILLAEX1 with Internet Mail Service (5.5.2650.21) id ; Fri, 29 Dec 2000 17:31:48 -0800 Message-ID: <79FE2AD687E9D311916C00D0B72CE4763B17CF@VILLAEX1> From: Olive Tao To: "'kdb@oss.sgi.com'" Subject: Date: Fri, 29 Dec 2000 17:31:44 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing Hi , I was using kdb-v0.6-2.2.13 against Red Hat 6.1 2.2.13-13 kernel. After several try, it always fails during kernel boot and issues error message LILO boot: loading nlinux...... uncompressing Linux... ran out of input data -- System halted Please advised. Best Regards, Olive From owner-kdb@oss.sgi.com Fri Dec 29 18:15:22 2000 Received: by oss.sgi.com id ; Fri, 29 Dec 2000 18:15:12 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:24070 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Fri, 29 Dec 2000 18:14:48 -0800 Received: (qmail 5159 invoked from network); 30 Dec 2000 02:14:42 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 30 Dec 2000 02:14:42 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Olive Tao cc: "'kdb@oss.sgi.com'" In-reply-to: Your message of "Fri, 29 Dec 2000 17:31:44 -0800." <79FE2AD687E9D311916C00D0B72CE4763B17CF@VILLAEX1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 Dec 2000 13:14:41 +1100 Message-ID: <2464.978142481@ocs3.ocs-net> Sender: owner-kdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kdb-outgoing On Fri, 29 Dec 2000 17:31:44 -0800, Olive Tao wrote: >I was using kdb-v0.6-2.2.13 against Red Hat 6.1 2.2.13-13 kernel. After >several try, it always fails during kernel boot and issues error message > >LILO boot: >loading nlinux...... >uncompressing Linux... > >ran out of input data Best guess, the size of the kdb symbol table is either too small (you get warnings about invalid initialisers) or too large (uncompress runs out of room). kdb v0.6 is old and no longer supported. Newer versions of kdb use a different and better method for getting the symbol table.