From kaos@sgi.com Wed Jan 4 02:18:50 2006 Received: with ECARTIS (v1.0.0; list kdb); Wed, 04 Jan 2006 02:18:53 -0800 (PST) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id k04AImm2008971 for ; Wed, 4 Jan 2006 02:18:49 -0800 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id UAA09139; Wed, 4 Jan 2006 20:10:50 +1100 Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 512F2EB1; Wed, 4 Jan 2006 20:10:50 +1100 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 36B1689733; Wed, 4 Jan 2006 20:10:50 +1100 (EST) X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.1 From: Keith Owens To: kdb@oss.sgi.com Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org Subject: Announce: kdb v4.4 is available for kernel 2.6.15 Date: Wed, 04 Jan 2006 20:10:49 +1100 Message-ID: <13550.1136365849@kao2.melbourne.sgi.com> X-archive-position: 1150 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: kaos@sgi.com Precedence: bulk X-list: kdb -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 KDB (Linux Kernel Debugger) has been updated for kernel 2.6.15. ftp://oss.sgi.com/projects/kdb/download/v4.4/ ftp://ftp.ocs.com.au/pub/mirrors/oss.sgi.com/projects/kdb/download/v4.4/ Note: Due to a spam attack, the kdb@oss.sgi.com mailing list is now subscriber only. If you reply to this mail, you may wish to trim kdb@oss.sgi.com from the cc: list. Current versions are :- kdb-v4.4-2.6.15-common-1.bz2 kdb-v4.4-2.6.15-i386-1.bz2 kdb-v4.4-2.6.15-ia64-1.bz2 Changelog extract since kdb-v4.4-2.6.14-common-1. 2006-01-04 Keith Owens * Print all buffers on a page in inode pages and update formatting to be legible, too. David Chinner, SGI. * Update page flags in kdbm_pg. * Remove inline from *.c files. * kdb v4.4-2.6.15-common-1. 2005-12-25 Keith Owens * kdb v4.4-2.6.15-rc7-common-1. 2005-12-20 Keith Owens * kdb v4.4-2.6.15-rc6-common-1. 2005-12-10 Keith Owens * Update mapping of flags to strings in kdbm_pg.c and kdbm_vm.c. * kdb v4.4-2.6.15-rc5-common-3. 2005-12-06 Keith Owens * Add RECOVERY flag to global KDB flags. * Add kdb_{save,restore}_flags. * kdb v4.4-2.6.15-rc5-common-2. 2005-12-05 Keith Owens * kdb v4.4-2.6.15-rc5-common-1. 2005-12-02 Keith Owens * kdbm_vm.c: offsets of page macros should be unsigned long. Reported by Dean Nelson, SGI. * kdb v4.4-2.6.15-rc4-common-1. 2005-11-30 Keith Owens * New follow_page() API. * kdb v4.4-2.6.15-rc3-common-1. 2005-11-21 Keith Owens * kdb v4.4-2.6.15-rc2-common-1. 2005-11-15 Keith Owens * kdb v4.4-2.6.15-rc1-common-1. 2005-11-15 Keith Owens * Allow kdb_printf() to be used outside kdb, in preemptible context. * Build with CONFIG_SWAP=n. Reported by Leo Yuriev. * kdb v4.4-2.6.14-common-2. Changelog extract since kdb-v4.4-2.6.14-i386-1. 2006-01-04 Keith Owens * Remove some inlines and the last vestige of CONFIG_NUMA_REPLICATE. * Read the keyboard acknowledgment after sending a character. SuSE Bugzilla 60240. * kdb v4.4-2.6.15-i386-1. 2005-12-25 Keith Owens * kdb v4.4-2.6.15-rc7-i386-1. 2005-12-20 Keith Owens * kdb v4.4-2.6.15-rc6-i386-1. 2005-12-05 Keith Owens * kdb v4.4-2.6.15-rc5-i386-1. 2005-12-02 Keith Owens * kdb v4.4-2.6.15-rc4-i386-1. 2005-11-30 Keith Owens * kdb v4.4-2.6.15-rc3-i386-1. 2005-11-21 Keith Owens * kdb v4.4-2.6.15-rc2-i386-1. 2005-11-15 Keith Owens * kdb v4.4-2.6.15-rc1-i386-1. Changelog extract since kdb v4.4-2.6.14-ia64-1. 2006-01-04 Keith Owens * Remove some inlines and the last vestige of CONFIG_NUMA_REPLICATE. * Read the keyboard acknowledgment after sending a character. SuSE Bugzilla 60240. * kdb v4.4-2.6.15-ia64-1. 2005-12-25 Keith Owens * kdb v4.4-2.6.15-rc7-ia64-1. 2005-12-20 Keith Owens * kdb v4.4-2.6.15-rc6-ia64-1. 2005-12-06 Keith Owens * Use RECOVERY flag in MCA handler. * kdb v4.4-2.6.15-rc5-ia64-2. 2005-12-05 Keith Owens * kdb v4.4-2.6.15-rc5-ia64-1. 2005-12-02 Keith Owens * Reinstate hook for debug trap, the patch chunk was accidentally dropped in 2.6.15-rc1. * kdb v4.4-2.6.15-rc4-ia64-1. 2005-11-30 Keith Owens * kdb v4.4-2.6.15-rc3-ia64-1. 2005-11-21 Keith Owens * kdb v4.4-2.6.15-rc2-ia64-1. 2005-11-15 Keith Owens * kdb v4.4-2.6.15-rc1-ia64-1. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Exmh version 2.1.1 10/15/1999 iD8DBQFDu5EZi4UHNye0ZOoRAladAJ9dOrLAnfedShRieBScdUM4LKoXdgCfa14w XkFg0U23y9XgZD64xu0iZ4Q= =nYyJ -----END PGP SIGNATURE----- --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From johnpw@TwinPeakSoft.com Wed Jan 25 21:53:09 2006 Received: with ECARTIS (v1.0.0; list kdb); Wed, 25 Jan 2006 21:53:14 -0800 (PST) Received: from TwinPeakSoft.com (adsl-69-227-249-30.dsl.pltn13.pacbell.net [69.227.249.30]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0Q5r5m2002333 for ; Wed, 25 Jan 2006 21:53:09 -0800 Received: from Twingates ([192.168.1.3]) by TwinPeakSoft.com (8.11.6/8.11.6) with SMTP id k0Q4KLJ02683 for ; Wed, 25 Jan 2006 20:20:22 -0800 Message-Id: <200601260420.k0Q4KLJ02683@TwinPeakSoft.com> Date: Wed, 25 Jan 2006 20:18:07 -0800 (PST) From: johnpw Reply-To: johnpw Subject: Problem with kdb-v4.4-2.6.9 To: kdb@oss.sgi.com MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-MD5: k1cQFPBUUG5GN87y7tacag== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.3_06 SunOS 5.9 sun4u sparc Content-Transfer-Encoding: 8bit X-archive-position: 1151 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: johnpw@TwinPeakSoft.com Precedence: bulk X-list: kdb Greetings, I have been running kdb v4.4-2.6.9 on 2.6.9 kernel for two weeks. I have found the following problems: 1. When the kernel panic, the bt command does not show the correct stack trace and the arguments on the calling chain. I did not have this problem with kdb-v4.3-2.4.21 on 2.4.21 kernel. I patched the kernel with kdb and there was no failure. for example, When the kernel panic, The console showed the following output, inode hda7:2555908 at cdbed370: mode 40755, nlink 0, next 0 Assertion failure in ext3_put_super() at fs/ext3/super.c:418: "list_empty(&sbi->s_orphan)" ------------[ cut here ]------------ kernel BUG at fs/ext3/super.c:418! invalid operand: 0000 [#1] Modules linked in: kdbm_task kdbm_pg kdbm_vm kdbm_x86 mfs nfs lockd md5 ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core sunrpc dm_mirror dm_mod button battery ac ohci_hcd ehci_hcd snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore sis900 floppy ext3 jbd CPU: 0 EIP: 0060:[] Tainted: P VLI EFLAGS: 00010292 (2.6.9-kdb) EIP is at ext3_put_super+0x166/0x190 [ext3] eax: 0000005e ebx: ddf74b68 ecx: c03d78c0 edx: 00000000 esi: ddf74ab4 edi: dbb6fad4 ebp: cebbaedc esp: cebbaebc ds: 007b es: 007b ss: 0068 Process umount (pid: 3739, threadinfo=cebba000 task=c1595790) Stack: de832a30 de83133b de831a21 000001a2 de831a06 dbb6fad4 dbb6fb38 de83b7c0 cebbaf0c c0183a0a 00052c00 ddf61900 00000000 cebbaf1c c015ad6f ddf61c80 00000000 dbb6fad4 dc38b9d8 08051bda cebbaf1c c018572a dbb6fad4 de83b980 Call Trace: [] show_stack+0x7a/0x90 [] show_registers+0x149/0x1c0 [] die+0x126/0x2a0 [] do_invalid_op+0xd7/0x100 [] error_code+0x2d/0x38 [] generic_shutdown_super+0x1ba/0x260 [] kill_block_super+0x1a/0x40 [] deactivate_super+0x93/0xf0 [] __mntput+0x28/0x40 [] path_release_on_umount+0x28/0x30 [] sys_umount+0x37/0x80 [] sys_oldumount+0x17/0x20 [] sysenter_past_esp+0x52/0x71 Code: 83 de b8 06 1a 83 de 89 44 24 10 b8 a2 01 00 00 89 44 24 0c b8 21 1a 83 de 89 44 24 08 b8 3b 13 83 de 89 44 24 04 e8 3a c1 8f e1 <0f> 0b a2 01 21 1a 83 de e9 31 ff ff ff 89 f8 89 f2 e8 e4 fd ff Entering kdb (current=0xc1595790, pid 3739) Oops: invalid operand due to oops @ 0xde82a786 eax = 0x0000005e ebx = 0xddf74b68 ecx = 0xc03d78c0 edx = 0x00000000 esi = 0xddf74ab4 edi = 0xdbb6fad4 esp = 0xcebbaebc eip = 0xde82a786 ebp = 0xcebbaedc xss = 0x00000068 xcs = 0x00000060 eflags = 0x00010292 xds = 0x0000007b xes = 0x0000007b origeax = 0xffffffff ®s = 0xcebbae88 kdb> Then, I entered 'bt' to show the calling chains, but only the last call was displayed and the argument were not corrrect. kdb> bt Stack traceback for pid 3739 0xc1595790 3739 3337 1 0 R 0xc1595a10 *umount EBP EIP Function (args) 0xcebbaedc 0xde82a786 [ext3]ext3_put_super+0x166 (0x5b, 0x4943, 0x499e, 0x499e) 0xcebbae18 0xc01265bb __call_console_drivers+0x4b (0x499e, 0x499e) 0xcebbae28 0xc0126659 _call_console_drivers+0x79 (0x30000002, 0x499e, 0x4940, 0x286, 0xcebbae74) 0xcebbae40 0xc01266bf call_console_drivers+0x5f (0xcebbae88, 0x0, 0xddf74b68, 0xc03d78c0, 0x0) 0xc0106931 error_code+0x2d Interrupt registers: eax = 0xdbb6fad4 ebx = 0xcebbae88 ecx = 0x00000000 edx = 0xddf74b68 esi = 0xc03d78c0 edi = 0x00000000 esp = 0x00000060 eip = 0x0000007b ebp = 0xddf74ab4 xss = 0x00010292 xcs = 0xffffffff eflags = 0xde82a786 xds = 0xcebbaedc xes = 0x0000005e origeax = 0x0000007b ®s = 0xcebbae80 Interrupt from user space, end of kernel trace kdb> The above is just one of many cases that the kdb can't display the right calling chains and the arguments, either in panic situation or when I hit KDB on my tty console port to force the kernel to kdp. What is the probelm ? 2. I config the SPIN_LOCK on kernel hacking, so the flag is CONFIG_DEBUG_SPINLOCK=y When there is some problem with spin_lock or spin_unlock, the kernel only display the following info and does not go into BUG(). lib/dec_and_lock.c:32: spin_lock(fs/dcache.c:c03dc280) already locked by lib/dec_and_lock.c/32 fs/dcache.c:101: spin_unlock(fs/dcache.c:c03dc280) not locked lib/dec_and_lock.c:32: spin_lock(fs/dcache.c:c03dc280) already locked by lib/dec_and_lock.c/32 fs/dcache.c:101: spin_unlock(fs/dcache.c:c03dc280) not locked lib/dec_and_lock.c:32: spin_lock(fs/dcache.c:c03dc280) already locked by lib/dec_and_lock.c/32 fs/dcache.c:101: spin_unlock(fs/dcache.c:c03dc280) not locked By checking the src. I found two spinlock.h include files that handle the spin lock problems differently. the include/linux/spinlock.h only display the above warning messages. The include/asm-i386/spinlock.h seems to go to the BUG() when there is a problem with spinlock or spinunlock. See the _raw_spin_lock function in both include file. What is the trick to force the kernel go to BUG() when there is spinlock/spinunlock problem ? 3. I was able to get the kernel to drop to kdb by doing one keystroke A (Control and A are next to each other on my keyboard) very quickly and easily. But now I have hit KDB (4 keystrokes) to get to kdb. Is there alternative ? I'll appreciate any comments and suggestions. Thanks, John W. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From roehrich@kickball-mn.Central.Sun.COM Thu Jan 26 11:30:52 2006 Received: with ECARTIS (v1.0.0; list kdb); Thu, 26 Jan 2006 11:30:58 -0800 (PST) Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0QJUpm2001090 for ; Thu, 26 Jan 2006 11:30:52 -0800 Received: from centralmail2brm.Central.Sun.COM ([129.147.62.14]) by brmea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id k0QIXfSD015970 for ; Thu, 26 Jan 2006 11:33:41 -0700 (MST) Received: from kickball-mn.Central.Sun.COM (kickball-mn.Central.Sun.COM [10.1.170.217]) by centralmail2brm.Central.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k0QIXfgr001539 for ; Thu, 26 Jan 2006 11:33:41 -0700 (MST) Received: from kickball-mn.Central.Sun.COM (localhost [127.0.0.1]) by kickball-mn.Central.Sun.COM (8.13.3+Sun/8.13.3) with ESMTP id k0QIXf0Z016082 for ; Thu, 26 Jan 2006 12:33:41 -0600 (CST) Received: (from roehrich@localhost) by kickball-mn.Central.Sun.COM (8.13.3+Sun/8.13.3/Submit) id k0QIXfwv016081 for kdb@oss.sgi.com; Thu, 26 Jan 2006 12:33:41 -0600 (CST) Date: Thu, 26 Jan 2006 12:33:41 -0600 From: Dean Roehrich To: kdb@oss.sgi.com Subject: Re: Problem with kdb-v4.4-2.6.9 Message-ID: <20060126183341.GA16033@kickball-mn.Central.Sun.COM> References: <200601260420.k0Q4KLJ02683@TwinPeakSoft.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601260420.k0Q4KLJ02683@TwinPeakSoft.com> User-Agent: Mutt/1.5.9i Content-Transfer-Encoding: 8bit X-archive-position: 1152 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: dean.roehrich@Sun.COM Precedence: bulk X-list: kdb On Wed, Jan 25, 2006 at 08:18:07PM -0800, johnpw wrote: > Greetings, > > I have been running kdb v4.4-2.6.9 on 2.6.9 kernel for two weeks. > I have found the following problems: > > 1. When the kernel panic, the bt command does not show the > correct stack trace and the arguments on the calling chain. > I did not have this problem with kdb-v4.3-2.4.21 on > 2.4.21 kernel. I patched the kernel with kdb and there was > no failure. > > for example, > When the kernel panic, The console showed the following output, > > > inode hda7:2555908 at cdbed370: mode 40755, nlink 0, next 0 > Assertion failure in ext3_put_super() at fs/ext3/super.c:418: > "list_empty(&sbi->s_orphan)" > ------------[ cut here ]------------ Hmmm, you don't say what arch you have. It's a 32bit something? I would check for arch/ kdb fixes that came later. For my own 2.6.9 (RHEL4) kernels I am using the 2.6.9 kdb patches and then various bits from all later kdb patches--especially anything that would fall under arch/. So this means my kdb patch stack for RHEL4 on x86_64 contains these patches: kdb-v4.4-2.6.9-common-2 kdb-v4.4-2.6.9-rc2-x86-64-1 kdb-task-fixes --compile error fix, from a later patch kdb-machine_restart --kdb_reboot() fix for x86_64, inspired by a later patch kdb-backtrace-fixes --kdba_bt_stack() fix for x86_64, from later patches # Misc things from kdb patches that were spun for later 2.6.x kernels. At # least one of these adds new useful kdb commands like 'inode', etc. kdb-fixes-from-2.6.10 kdb-fixes-from-2.6.11-a kdb-fixes-from-2.6.13 kdb-fixes-from-2.6.14 I haven't been using my 2.6.9 kernels lately, though, so I can't say if I'm seeing the problems you're describing or if one of the above fixes it. I also have all of my kdb stuff built-in to the kernel, rather than loading as modules as you have it. Dean --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From johnpw@TwinPeakSoft.com Thu Jan 26 13:47:11 2006 Received: with ECARTIS (v1.0.0; list kdb); Thu, 26 Jan 2006 13:47:20 -0800 (PST) Received: from TwinPeakSoft.com (adsl-69-227-249-30.dsl.pltn13.pacbell.net [69.227.249.30]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0QLl6m2014646 for ; Thu, 26 Jan 2006 13:47:11 -0800 Received: from Twingates ([192.168.1.3]) by TwinPeakSoft.com (8.11.6/8.11.6) with SMTP id k0QLrwJ09437; Thu, 26 Jan 2006 13:53:58 -0800 Message-Id: <200601262153.k0QLrwJ09437@TwinPeakSoft.com> Date: Thu, 26 Jan 2006 13:51:36 -0800 (PST) From: johnpw Reply-To: johnpw Subject: Re: Problem with kdb-v4.4-2.6.9 To: kdb@oss.sgi.com, dean.roehrich@sun.com MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-MD5: 2iHWQIjww5qQoim02ghtVw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.3_06 SunOS 5.9 sun4u sparc Content-Transfer-Encoding: 8bit X-archive-position: 1153 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: johnpw@TwinPeakSoft.com Precedence: bulk X-list: kdb Hi, Dean, Thanks for your quick response. The two patches I applied on my 2.6.9 i386 kernel are: 1. kdb-v4.4-2.6.9-common-2 2. kdb-v4.4-2.6.9-i386-1 Are these two patches the most updated one for 2.6.9 i386 kernel ? or there are other patches that I need to apply ? Thanks, John W. >Date: Thu, 26 Jan 2006 12:33:41 -0600 >From: Dean Roehrich >To: kdb@oss.sgi.com >Subject: Re: Problem with kdb-v4.4-2.6.9 >Content-Disposition: inline >User-Agent: Mutt/1.5.9i >X-archive-position: 1152 >X-ecartis-version: Ecartis v1.0.0 >X-original-sender: dean.roehrich@Sun.COM >X-list: kdb >X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on oss.sgi.com >X-Virus-Status: Clean > >On Wed, Jan 25, 2006 at 08:18:07PM -0800, johnpw wrote: >> Greetings, >> >> I have been running kdb v4.4-2.6.9 on 2.6.9 kernel for two weeks. >> I have found the following problems: >> >> 1. When the kernel panic, the bt command does not show the >> correct stack trace and the arguments on the calling chain. >> I did not have this problem with kdb-v4.3-2.4.21 on >> 2.4.21 kernel. I patched the kernel with kdb and there was >> no failure. >> >> for example, >> When the kernel panic, The console showed the following output, >> >> >> inode hda7:2555908 at cdbed370: mode 40755, nlink 0, next 0 >> Assertion failure in ext3_put_super() at fs/ext3/super.c:418: >> "list_empty(&sbi->s_orphan)" >> ------------[ cut here ]------------ > > >Hmmm, you don't say what arch you have. It's a 32bit something? > >I would check for arch/ kdb fixes that came later. For my own 2.6.9 >(RHEL4) kernels I am using the 2.6.9 kdb patches and then various bits from >all later kdb patches--especially anything that would fall under >arch/. > >So this means my kdb patch stack for RHEL4 on x86_64 contains these patches: > >kdb-v4.4-2.6.9-common-2 >kdb-v4.4-2.6.9-rc2-x86-64-1 >kdb-task-fixes --compile error fix, from a later patch >kdb-machine_restart --kdb_reboot() fix for x86_64, inspired by a later patch >kdb-backtrace-fixes --kdba_bt_stack() fix for x86_64, from later patches > ># Misc things from kdb patches that were spun for later 2.6.x kernels. At ># least one of these adds new useful kdb commands like 'inode', etc. > >kdb-fixes-from-2.6.10 >kdb-fixes-from-2.6.11-a >kdb-fixes-from-2.6.13 >kdb-fixes-from-2.6.14 > >I haven't been using my 2.6.9 kernels lately, though, so I can't say if I'm >seeing the problems you're describing or if one of the above fixes it. I also >have all of my kdb stuff built-in to the kernel, rather than loading as >modules as you have it. > >Dean >--------------------------- >Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From Scott.Lurndal@3leafnetworks.com Thu Jan 26 15:58:10 2006 Received: with ECARTIS (v1.0.0; list kdb); Thu, 26 Jan 2006 15:58:23 -0800 (PST) Received: from chronus.3leafnetworks.com (chronus.3leafnetworks.com [71.129.195.180]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0QNwAm2022489 for ; Thu, 26 Jan 2006 15:58:10 -0800 Received: from localhost (unknown [127.0.0.1]) by chronus.3leafnetworks.com (Postfix) with ESMTP id 2D10478634D for ; Thu, 26 Jan 2006 22:00:11 +0000 (UTC) Received: from chronus.3leafnetworks.com ([127.0.0.1]) by localhost (mailrelay.3leafnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18610-04 for ; Thu, 26 Jan 2006 13:59:49 -0800 (PST) Received: from chronus.3leafnetworks.corp (chronus.3leafnetworks.com [10.16.16.17]) by chronus.3leafnetworks.com (Postfix) with ESMTP id 58F03786349 for ; Thu, 26 Jan 2006 13:59:49 -0800 (PST) Received: from pendragon.3leafnetworks.com ([10.32.0.1]) by chronus.3leafnetworks.corp with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jan 2006 13:59:46 -0800 Received: from pendragon.3leafnetworks.com (localhost [127.0.0.1]) by pendragon.3leafnetworks.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0QM04vs022268; Thu, 26 Jan 2006 14:00:04 -0800 Received: (from slurndal@localhost) by pendragon.3leafnetworks.com (8.12.10/8.12.10/Submit) id k0QM041Q022267; Thu, 26 Jan 2006 14:00:04 -0800 Date: Thu, 26 Jan 2006 14:00:04 -0800 From: Scott Lurndal To: johnpw Cc: kdb@oss.sgi.com, dean.roehrich@sun.com Subject: Re: Problem with kdb-v4.4-2.6.9 Message-ID: <20060126220004.GB21747@pendragon.3leafnetworks.com> References: <200601262153.k0QLrwJ09437@TwinPeakSoft.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601262153.k0QLrwJ09437@TwinPeakSoft.com> User-Agent: Mutt/1.5.6i X-OriginalArrivalTime: 26 Jan 2006 21:59:46.0253 (UTC) FILETIME=[D1EC4FD0:01C622C3] Content-Transfer-Encoding: 8bit X-archive-position: 1154 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: scott.lurndal@3leafnetworks.com Precedence: bulk X-list: kdb On Thu, Jan 26, 2006 at 01:51:36PM -0800, johnpw wrote: > Hi, Dean, > > Thanks for your quick response. > The two patches I applied on my 2.6.9 i386 kernel are: > > 1. kdb-v4.4-2.6.9-common-2 > 2. kdb-v4.4-2.6.9-i386-1 > > Are these two patches the most updated one for 2.6.9 > i386 kernel ? or there are other patches that I need > to apply ? Thanks, I recently applied (ported) the 4.4 patches to the redhat 4.2 kernel (2.6.9-22.EL). I used the base patch set for the 2.6.9 release, then back-ported most of the fixes from the kdb4.4-2.6.15? (latest) release from Keith. Stack tracebacks work much better. So do breakpoints. FYI - if you don't like KDB (which I dislike, too), you can change it back to control-A (there's a const char * defined somewhere in the KDB patch that defines the enter KDB string). scott > > John W. > > > >Date: Thu, 26 Jan 2006 12:33:41 -0600 > >From: Dean Roehrich > >To: kdb@oss.sgi.com > >Subject: Re: Problem with kdb-v4.4-2.6.9 > >Content-Disposition: inline > >User-Agent: Mutt/1.5.9i > >X-archive-position: 1152 > >X-ecartis-version: Ecartis v1.0.0 > >X-original-sender: dean.roehrich@Sun.COM > >X-list: kdb > >X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on > oss.sgi.com > >X-Virus-Status: Clean > > > >On Wed, Jan 25, 2006 at 08:18:07PM -0800, johnpw wrote: > >> Greetings, > >> > >> I have been running kdb v4.4-2.6.9 on 2.6.9 kernel for two weeks. > >> I have found the following problems: > >> > >> 1. When the kernel panic, the bt command does not show the > >> correct stack trace and the arguments on the calling chain. > >> I did not have this problem with kdb-v4.3-2.4.21 on > >> 2.4.21 kernel. I patched the kernel with kdb and there was > >> no failure. > >> > >> for example, > >> When the kernel panic, The console showed the following output, > >> > >> > >> inode hda7:2555908 at cdbed370: mode 40755, nlink 0, next 0 > >> Assertion failure in ext3_put_super() at fs/ext3/super.c:418: > >> "list_empty(&sbi->s_orphan)" > >> ------------[ cut here ]------------ > > > > > >Hmmm, you don't say what arch you have. It's a 32bit something? > > > >I would check for arch/ kdb fixes that came later. For my own 2.6.9 > >(RHEL4) kernels I am using the 2.6.9 kdb patches and then various bits from > >all later kdb patches--especially anything that would fall under > >arch/. > > > >So this means my kdb patch stack for RHEL4 on x86_64 contains these patches: > > > >kdb-v4.4-2.6.9-common-2 > >kdb-v4.4-2.6.9-rc2-x86-64-1 > >kdb-task-fixes --compile error fix, from a later patch > >kdb-machine_restart --kdb_reboot() fix for x86_64, inspired by a later patch > >kdb-backtrace-fixes --kdba_bt_stack() fix for x86_64, from later patches > > > ># Misc things from kdb patches that were spun for later 2.6.x kernels. At > ># least one of these adds new useful kdb commands like 'inode', etc. > > > >kdb-fixes-from-2.6.10 > >kdb-fixes-from-2.6.11-a > >kdb-fixes-from-2.6.13 > >kdb-fixes-from-2.6.14 > > > >I haven't been using my 2.6.9 kernels lately, though, so I can't say if I'm > >seeing the problems you're describing or if one of the above fixes it. I also > >have all of my kdb stuff built-in to the kernel, rather than loading as > >modules as you have it. > > > >Dean > >--------------------------- > >Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. > > --------------------------- > Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From roehrich@kickball-mn.Central.Sun.COM Thu Jan 26 17:13:29 2006 Received: with ECARTIS (v1.0.0; list kdb); Thu, 26 Jan 2006 17:13:34 -0800 (PST) Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0R1DTm2030577 for ; Thu, 26 Jan 2006 17:13:29 -0800 Received: from centralmail1brm.Central.Sun.COM ([129.147.62.1]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id k0QMe44u017033 for ; Thu, 26 Jan 2006 14:40:05 -0800 (PST) Received: from kickball-mn.Central.Sun.COM (kickball-mn.Central.Sun.COM [10.1.170.217]) by centralmail1brm.Central.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id k0QMe44G002762 for ; Thu, 26 Jan 2006 15:40:04 -0700 (MST) Received: from kickball-mn.Central.Sun.COM (localhost [127.0.0.1]) by kickball-mn.Central.Sun.COM (8.13.3+Sun/8.13.3) with ESMTP id k0QMe47Y020762 for ; Thu, 26 Jan 2006 16:40:04 -0600 (CST) Received: (from roehrich@localhost) by kickball-mn.Central.Sun.COM (8.13.3+Sun/8.13.3/Submit) id k0QMe3GT020761 for kdb@oss.sgi.com; Thu, 26 Jan 2006 16:40:03 -0600 (CST) Date: Thu, 26 Jan 2006 16:40:03 -0600 From: Dean Roehrich To: kdb@oss.sgi.com Subject: Re: Problem with kdb-v4.4-2.6.9 Message-ID: <20060126224003.GA20744@kickball-mn.Central.Sun.COM> References: <200601262153.k0QLrwJ09437@TwinPeakSoft.com> <20060126220004.GB21747@pendragon.3leafnetworks.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060126220004.GB21747@pendragon.3leafnetworks.com> User-Agent: Mutt/1.5.9i Content-Transfer-Encoding: 8bit X-archive-position: 1155 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: dean.roehrich@sun.com Precedence: bulk X-list: kdb On Thu, Jan 26, 2006 at 01:51:36PM -0800, johnpw wrote: > Hi, Dean, > > Thanks for your quick response. > The two patches I applied on my 2.6.9 i386 kernel are: > > 1. kdb-v4.4-2.6.9-common-2 > 2. kdb-v4.4-2.6.9-i386-1 > > Are these two patches the most updated one for 2.6.9 > i386 kernel ? or there are other patches that I need > to apply ? Thanks, Those are the most recent for the 2.6.9 kernel. But that's not the most recent version of kdb. The patch model for kdb is that the latest version of kdb is available as a patch on the latest kernel...that's it. Dean --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From francois.wellenreiter@bull.net Fri Jan 27 06:57:01 2006 Received: with ECARTIS (v1.0.0; list kdb); Fri, 27 Jan 2006 06:57:07 -0800 (PST) Received: from ecfrec.frec.bull.fr (ecfrec.frec.bull.fr [129.183.4.8]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0REv0m2006815 for ; Fri, 27 Jan 2006 06:57:00 -0800 Received: from localhost (localhost [127.0.0.1]) by ecfrec.frec.bull.fr (Postfix) with ESMTP id A454119D929 for ; Fri, 27 Jan 2006 14:53:08 +0100 (CET) Received: from ecfrec.frec.bull.fr ([127.0.0.1]) by localhost (ecfrec.frec.bull.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32557-01 for ; Fri, 27 Jan 2006 14:53:07 +0100 (CET) Received: from ecn002.frec.bull.fr (ecn002.frec.bull.fr [129.183.4.6]) by ecfrec.frec.bull.fr (Postfix) with ESMTP id 4674C19D913 for ; Fri, 27 Jan 2006 14:53:07 +0100 (CET) Received: from [129.183.101.120] ([129.183.101.120]) by ecn002.frec.bull.fr (Lotus Domino Release 5.0.12) with ESMTP id 2006012714535693:1226 ; Fri, 27 Jan 2006 14:53:56 +0100 Message-ID: <43DA262A.5080503@bull.net> Date: Fri, 27 Jan 2006 14:54:50 +0100 From: Francois WELLENREITER Organization: BULL User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051007 Debian/1.7.12-1 X-Accept-Language: en MIME-Version: 1.0 To: kdb@oss.sgi.com Subject: Some module symbols are not correctly retrieved with KDB X-MIMETrack: Itemize by SMTP Server on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 27/01/2006 14:53:56, Serialize by Router on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 27/01/2006 14:54:00, Serialize complete at 27/01/2006 14:54:00 Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=ISO-8859-1 X-archive-position: 1156 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: francois.wellenreiter@bull.net Precedence: bulk X-list: kdb Hello Keith and all kdb users, I have to report the following bug : I use an official linux-2.6.15 with kdb-v4.4 on IA-64 machine. When trying to disassemble the "mpt_get_msg_frame" function (located in drivers/message/fusion/mptbase.c), I obtain a incoherent content on my screen : __________________________________________________________________ [1]kdb> id mpt_get_msg_frame 0xa00000020303f7a0 fusion_exit+0xc40[MMB] data8 0x010181e00 0xa00000020303f7a6 fusion_exit+0xc46 chk.a.nc f0,0xa0000002033378e0 0xa00000020303f7ac fusion_exit+0xc4c data8 0x14000000406 0xa00000020303f7b0 fusion_exit+0xc50[MMB] data8 0x010181e00 0xa00000020303f7b6 fusion_exit+0xc56 chk.a.nc f0,0xa0000002035978f0 0xa00000020303f7bc fusion_exit+0xc5c data8 0x14000000406 0xa00000020303f7c0 fusion_exit+0xc60[MMB] data8 0x010181e00 0xa00000020303f7c6 fusion_exit+0xc66 chk.a.clr f0,0xa0000002035c3900 0xa00000020303f7cc fusion_exit+0xc6c data8 0x14000000406 0xa00000020303f7d0 fusion_exit+0xc70[MMB] data8 0x010181e00 0xa00000020303f7d6 fusion_exit+0xc76 chk.a.nc f0,0xa000000203e2b910 0xa00000020303f7dc fusion_exit+0xc7c data8 0x14000000406 0xa00000020303f7e0 fusion_exit+0xc80[MMB] data8 0x010181e00 0xa00000020303f7e6 fusion_exit+0xc86 chk.a.clr f0,0xa00000020360b920 0xa00000020303f7ec fusion_exit+0xc8c data8 0x14000000406 0xa00000020303f7f0 fusion_exit+0xc90[MMB] data8 0x010181e00 0xa00000020303f7f6 fusion_exit+0xc96 break.m 0xa00 __________________________________________________________________ I think that this pointer contains the function descriptor and not the function address, because when publishing the content of this area, I have : __________________________________________________________________ [1]kdb> md8 mpt_get_msg_frame 1 0xa00000020303f728 a000000203031e00 a00000020303c018 ................ __________________________________________________________________ I first thought that it was an incoherency between module management and kdb module address retrieving, but for some other functions, I do not have this problem. For example, with "mptscsih_proc_info" function: __________________________________________________________________ [1]kdb> id mptscsih_proc_info 0xa0000002030618c0 mptscsih_proc_info[MMI] alloc r41=ar.pfs,15,11,0 0xa0000002030618c6 mptscsih_proc_info+0x6 adds r12=-32,r12 0xa0000002030618cc mptscsih_proc_info+0xc addl r44=16408,r1 0xa0000002030618d0 mptscsih_proc_info+0x10[MMI] adds r32=1160,r32 0xa0000002030618d6 mptscsih_proc_info+0x16 mov r42=r1 0xa0000002030618dc mptscsih_proc_info+0x1c cmp.eq p8,p9=0,r34;; 0xa0000002030618e0 mptscsih_proc_info+0x20[MMI] adds r38=28,r12 0xa0000002030618e6 mptscsih_proc_info+0x26 adds r14=16,r12 0xa0000002030618ec mptscsih_proc_info+0x2c adds r39=32,r12 0xa0000002030618f0 mptscsih_proc_info+0x30[MMI] add r44=r0,r44 0xa0000002030618f6 mptscsih_proc_info+0x36 ld8 r32=[r32] 0xa0000002030618fc mptscsih_proc_info+0x3c cmp4.eq p6,p7=0,r37;; 0xa000000203061900 mptscsih_proc_info+0x40[MMI] nop.m 0x0 0xa000000203061906 mptscsih_proc_info+0x46 mov r43=r14 0xa00000020306190c mptscsih_proc_info+0x4c mov r40=b0 0xa000000203061910 mptscsih_proc_info+0x50[MMB] nop.m 0x0 0xa000000203061916 mptscsih_proc_info+0x56 mov r8=r0 [1]more> q [1]kdb> md8 mptscsih_proc_info 1 0xa0000002030618c0 00c00580163d4808 9200098580467e33 .H=.....3~F..... [1]kdb> __________________________________________________________________ Could someone tell me what it is due to ? Thanks in advance for your help, best regards, François --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From francois.wellenreiter@bull.net Fri Jan 27 07:21:55 2006 Received: with ECARTIS (v1.0.0; list kdb); Fri, 27 Jan 2006 07:21:58 -0800 (PST) Received: from ecfrec.frec.bull.fr (ecfrec.frec.bull.fr [129.183.4.8]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k0RFLtm2009328 for ; Fri, 27 Jan 2006 07:21:55 -0800 Received: from localhost (localhost [127.0.0.1]) by ecfrec.frec.bull.fr (Postfix) with ESMTP id 8C21A19D91F for ; Fri, 27 Jan 2006 16:22:53 +0100 (CET) Received: from ecfrec.frec.bull.fr ([127.0.0.1]) by localhost (ecfrec.frec.bull.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14323-10 for ; Fri, 27 Jan 2006 16:22:52 +0100 (CET) Received: from ecn002.frec.bull.fr (ecn002.frec.bull.fr [129.183.4.6]) by ecfrec.frec.bull.fr (Postfix) with ESMTP id 4EC1B19D918 for ; Fri, 27 Jan 2006 16:22:52 +0100 (CET) Received: from [129.183.101.120] ([129.183.101.120]) by ecn002.frec.bull.fr (Lotus Domino Release 5.0.12) with ESMTP id 2006012716234357:1510 ; Fri, 27 Jan 2006 16:23:43 +0100 Message-ID: <43DA3B35.20202@bull.net> Date: Fri, 27 Jan 2006 16:24:37 +0100 From: Francois WELLENREITER Organization: BULL User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051007 Debian/1.7.12-1 X-Accept-Language: en MIME-Version: 1.0 To: kdb@oss.sgi.com Subject: Re: Some module symbols are not correctly retrieved with KDB References: <43DA262A.5080503@bull.net> In-Reply-To: <43DA262A.5080503@bull.net> X-MIMETrack: Itemize by SMTP Server on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 27/01/2006 16:23:43, Serialize by Router on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 27/01/2006 16:23:45, Serialize complete at 27/01/2006 16:23:45 Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=ISO-8859-1 X-archive-position: 1157 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: francois.wellenreiter@bull.net Precedence: bulk X-list: kdb Concerning this problem, what does STB_WEAK exactly erfer to ? Sorry for my ignorance, but my experience with ELF format is a bit limited. It appears that all the symbols with st_info fixed to STB_WEAK have the same behavior. Is it normal ? Kind regards, Francois --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.