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 <ESC>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 <[EMAIL PROTECTED]> > >To: [email protected] > >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: [EMAIL PROTECTED] > >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/<my-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/<my-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.
