From murali.selvaraj2003@yahoo.com Thu Sep 4 09:37:58 2008 Received: with ECARTIS (v1.0.0; list kdb); Thu, 04 Sep 2008 09:38:01 -0700 (PDT) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m84GbvTp029261 for ; Thu, 4 Sep 2008 09:37:57 -0700 X-ASG-Debug-ID: 1220546364-1a6d02450000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from n2d.bullet.mail.ac4.yahoo.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with SMTP id 813D71242D4C for ; Thu, 4 Sep 2008 09:39:24 -0700 (PDT) Received: from n2d.bullet.mail.ac4.yahoo.com (n2d.bullet.mail.ac4.yahoo.com [76.13.13.86]) by cuda.sgi.com with SMTP id QyI75165OcXP2ieP for ; Thu, 04 Sep 2008 09:39:24 -0700 (PDT) Received: from [76.13.13.26] by n2.bullet.mail.ac4.yahoo.com with NNFMP; 04 Sep 2008 16:39:24 -0000 Received: from [76.13.10.166] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 04 Sep 2008 16:39:23 -0000 Received: from [127.0.0.1] by omp107.mail.ac4.yahoo.com with NNFMP; 04 Sep 2008 16:39:23 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 880787.73183.bm@omp107.mail.ac4.yahoo.com Received: (qmail 22762 invoked by uid 60001); 4 Sep 2008 16:39:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=RBaHr/9CbLdrgd8bDGNL5dHUz8K29p01eUK/2g4J5XP26exSXehN2AxWqOATYgvWd6NgOe7hS5uEzUYsRfDtnsiSxKM6LtITmjEW2Uua6vdYbK5Vw1TlR4wy9lsfNszKkmi5ELro5LcGwM20idIqO7N6q39pOf5342GKSoFrzGU=; X-YMail-OSG: NjWaBNQVM1kaSYY0oagUL1znVwsUflxcUDtOrpsBTbFn2_u2OXQwF.gYpPRZ1VrvFnfxnDTd1rAeWI7frgfnSYpKjHwU8mCu2ybYDfsH3x0ONzvw1SUrMr9_o5X9Hik- Received: from [116.75.183.110] by web59601.mail.ac4.yahoo.com via HTTP; Thu, 04 Sep 2008 09:39:23 PDT X-Mailer: YahooMailRC/1096.28 YahooMailWebService/0.7.218.2 Date: Thu, 4 Sep 2008 09:39:23 -0700 (PDT) From: Murali Selvaraj X-ASG-Orig-Subj: Doubts in Kernel Debugger Subject: Doubts in Kernel Debugger To: kdb@oss.sgi.com MIME-Version: 1.0 Content-type: text/plain Message-ID: <768563.21599.qm@web59601.mail.ac4.yahoo.com> X-Barracuda-Connect: n2d.bullet.mail.ac4.yahoo.com[76.13.13.86] X-Barracuda-Start-Time: 1220546364 X-Barracuda-Bayes: INNOCENT GLOBAL 0.4897 1.0000 0.0000 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.4643 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Transfer-Encoding: 8bit X-archive-position: 1452 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: murali.selvaraj2003@yahoo.com Precedence: bulk X-list: kdb  Hello All,               This is my first mail for this mailing list.Actually i have tried to clear my doubt in all forums,but i could not able to find the solution for my problem.Here i will explain about my issue.              i have some problem in my Linux Machine(2.4.17),it seems one of the application process is become looping. So i could not able to access my system.So i have tried through kdb mode.After enter into KDB that time only i have found current running process(my application process using ps command under KDB). Then i have dumped the memory to dedicated Crashdump partition.My system having Crashdump Mechanism. The problem is when i have dump the System memory,all system registers (eax,ebx,........,esp,eip) values like invalid values. The values all are less than 0xc0000000(PAGE_OFFSET).All values are like user-space values.So my crashdump mechanism could not able to dump the memory.Because the computation of current process descriptor (esp & 0xffffe000) address becomes invalid.So i didnt get Kernel Stack for this Process,because of invalid ESP value.           Could you please explain me,in this case how can i dump the corresponding kernel-space values (all pt_regs values) in kdb mode.Then only i can able to dump the memory properly.After that only i can able to start my Crash analysis. How to find the pt_regs address for this case,in kernel-space land.           Actually i have modified my part of KDB code like this for this case,                      if ( regs->esp < PAGE_OFFSET)                    {                              regs->esp=current->thread.esp;                              regs->eip=current->thread.eip;                              regs->ebp=*(unsigned long *)esp;                         }                       Then pass the address of pt_regs for Crashdump Mechanism,i tried this modification in my system,but i couldnt succeeded.               If you have any information  about this one Could you reply to me,it will be very useful. If my Question is wrong,Could you please ignore it. Thankx & Regards, Murali.S --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From kworth@gmail.com Thu Sep 25 19:30:13 2008 Received: with ECARTIS (v1.0.0; list kdb); Thu, 25 Sep 2008 19:30:16 -0700 (PDT) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m8Q2UBcp022233 for ; Thu, 25 Sep 2008 19:30:13 -0700 X-ASG-Debug-ID: 1222396304-79a102770000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from wa-out-1112.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id D2A5D1AF28E1 for ; Thu, 25 Sep 2008 19:31:44 -0700 (PDT) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by cuda.sgi.com with ESMTP id 2nYkCeGd1OjuoQFC for ; Thu, 25 Sep 2008 19:31:44 -0700 (PDT) Received: by wa-out-1112.google.com with SMTP id j5so355112wah.4 for ; Thu, 25 Sep 2008 19:31:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=xnAEX5ygFkWAgfp2bb276tppVEVGJf4M0xLpbHCrzg4=; b=l0wkbPVBilKEcCzcxoZBBcXk9goG30eDmw9vAnBBWZlhn7FcnfCLoceFB3TUz49KVL T2Rc9WGkC0ovWelvV5mVfJMBT7kAS4NBlph801N9IvayH7BiLqfvucxCWfwS+bL107gf WxnycPrjOlaM9vUO6TGF8QreF6ICxVm+jKyEA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=dXcVr+LnIi5gZesmoovxBfK54p6HkDPISzw58HJOlPTcKez3as+8YTHoYosv3YEms5 obGYup8RP58G8GaKfjDctywvGbQJNE7kuDS9TO3mm06iF7KdZO/pyfOgjfK4pHoCTfnV VfQeHs33+UnUV8L00Bpn1k9ebYpnj2nnDO63E= Received: by 10.115.18.3 with SMTP id v3mr628343wai.180.1222396304291; Thu, 25 Sep 2008 19:31:44 -0700 (PDT) Received: by 10.114.79.6 with HTTP; Thu, 25 Sep 2008 19:31:44 -0700 (PDT) Message-ID: Date: Thu, 25 Sep 2008 19:31:44 -0700 From: "Kevin Worth" To: kdb@oss.sgi.com X-ASG-Orig-Subj: Serial console hangs intermittently on kdb-v4.4-2.6.20-common-6/kdb-v4.4-2.6.20-i386-3 Subject: Serial console hangs intermittently on kdb-v4.4-2.6.20-common-6/kdb-v4.4-2.6.20-i386-3 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Barracuda-Connect: wa-out-1112.google.com[209.85.146.181] X-Barracuda-Start-Time: 1222396306 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0209 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.6517 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1453 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: kworth@gmail.com Precedence: bulk X-list: kdb Hi All, I set up a system with KDB and everything runs great, except that when I am in KDB on the serial console, it seems to hang intermittently (for several minutes) and then continue working again for a few seconds or so. I am grateful to have some immediate post-mortem debugging capability now on this system (since sometimes kdump fails due to memory corruption), but the process goes very slowly when the system hangs every couple times you go to type a command. I know this kernel is a bit old- is this an issue that has been fixed on newer versions but was not backported to the 2.6.20 version? Any ideas of where I can start? I've now tried two different serial ports and both are running at 9600 8-n-1, with flow control off. The problem seems to occur most often if I leave the console sitting for a few seconds, though I've also had it when I'm quickly interacting and typing commands. Additionally, is the sgi ftp at ftp://oss.sgi.com/projects/kdb/download/v4.4/ the only place to find files for kdb? It would be nice to have some of the patches that were added to the KDB patches for later kernels (i.e. ehci/uhci USB, kdump), but it doesn't seem particularly easy to tell which modifications are for which feature... I guess perhaps I could search the mailing list archives for the original patch submissions... any easier way? Does KDB exist in any online source control systems? The SGI CVS server no longer appears to contain it... are new versions just posted straight to the FTP site? -Kevin --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Thu Sep 25 20:35:46 2008 Received: with ECARTIS (v1.0.0; list kdb); Thu, 25 Sep 2008 20:35:50 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m8Q3Zk0r002172 for ; Thu, 25 Sep 2008 20:35:46 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by cthulhu.engr.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m8Q3bKPc016304; Thu, 25 Sep 2008 20:37:21 -0700 Message-ID: <48DC58C8.3030604@sgi.com> Date: Thu, 25 Sep 2008 20:36:40 -0700 From: Jay Lan User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: Kevin Worth CC: KDB Subject: Re: Serial console hangs intermittently on kdb-v4.4-2.6.20-common-6/kdb-v4.4-2.6.20-i386-3 References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1454 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Kevin Worth wrote: > Hi All, Hi Kevin, > > I set up a system with KDB and everything runs great, except that when > I am in KDB on the serial console, it seems to hang intermittently > (for several minutes) and then continue working again for a few > seconds or so. I am grateful to have some immediate post-mortem > debugging capability now on this system (since sometimes kdump fails > due to memory corruption), but the process goes very slowly when the > system hangs every couple times you go to type a command. > > I know this kernel is a bit old- is this an issue that has been fixed > on newer versions but was not backported to the 2.6.20 version? Which arch were you running on and how did you set up your serial console? I have not seen the intermittent stall problem you described before. > Any > ideas of where I can start? I've now tried two different serial ports > and both are running at 9600 8-n-1, with flow control off. The problem > seems to occur most often if I leave the console sitting for a few > seconds, though I've also had it when I'm quickly interacting and > typing commands. I let people more better on serial port setting to respond here. > > Additionally, is the sgi ftp at > ftp://oss.sgi.com/projects/kdb/download/v4.4/ the only place to find > files for kdb? Yes. > It would be nice to have some of the patches that were > added to the KDB patches for later kernels (i.e. ehci/uhci USB, > kdump), but it doesn't seem particularly easy to tell which > modifications are for which feature... That is true. You can look at the ChangLog at kdb/ and at arch/{ia64,x86}/kdb/ directories. Major bug fixes/features are described in the ChangeLog's. Unzipped patches will have complete version of ChangeLog's. BTW, uhci USB feature has been backed out since it caused regression in ohci. > I guess perhaps I could search > the mailing list archives for the original patch submissions... any > easier way? Does KDB exist in any online source control systems? The > SGI CVS server no longer appears to contain it... Unfortunately, no. > are new versions > just posted straight to the FTP site? Yes, it has been that way. We use internal RCS tree to maintain the patches and newer versions are then placed at the FTP site. Regards, jay > > -Kevin > --------------------------- > 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 kworth@gmail.com Fri Sep 26 01:15:38 2008 Received: with ECARTIS (v1.0.0; list kdb); Fri, 26 Sep 2008 01:15:47 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m8Q8Fcdd024253 for ; Fri, 26 Sep 2008 01:15:38 -0700 X-ASG-Debug-ID: 1222417033-2f1200c20000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from wa-out-1112.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id B74B11210425 for ; Fri, 26 Sep 2008 01:17:13 -0700 (PDT) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by cuda.sgi.com with ESMTP id DHh2MbZaQ6Ij84mm for ; Fri, 26 Sep 2008 01:17:13 -0700 (PDT) Received: by wa-out-1112.google.com with SMTP id j5so410708wah.4 for ; Fri, 26 Sep 2008 01:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cfQEQ0J45ak4/B3XmCHh7ZscFdEng8dZg2HrIPTASrc=; b=MVgndkAtJM8pOYoGvcsvYKdF5vrl4CMBfLHdPqVMS7j9P2Nh3BXrg5l4A6ORLsE6aS NF+Bkk7AxWCIynmel7JuhTGLEwPBWvOzML52Oti5N/gAVxJVGpNP04k98JvsUamdEwF8 W/1tzZGvdC6G2x2fKgCFeir9Wisj9KWHEZsz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=QzyTS0MbJhskOjVjtxloUUEDbQ+bUWYIozvL6h6uvj4ZWfdNDqrgQmid3UeT5NSFH0 jozM8w11JMhuG773ZTEvmZ1bF1X01BehBaM+74KXnus1GneWSkjnOrSiou+S6+AZsPMj bMbhpT3xyJ4oPLnUrgb7SP5/YAqNI2rub2N2E= Received: by 10.115.74.1 with SMTP id b1mr954052wal.169.1222417032419; Fri, 26 Sep 2008 01:17:12 -0700 (PDT) Received: by 10.114.79.6 with HTTP; Fri, 26 Sep 2008 01:17:12 -0700 (PDT) Message-ID: Date: Fri, 26 Sep 2008 01:17:12 -0700 From: "Kevin Worth" To: "Jay Lan" X-ASG-Orig-Subj: Re: Serial console hangs intermittently on kdb-v4.4-2.6.20-common-6/kdb-v4.4-2.6.20-i386-3 Subject: Re: Serial console hangs intermittently on kdb-v4.4-2.6.20-common-6/kdb-v4.4-2.6.20-i386-3 Cc: KDB In-Reply-To: <48DC58C8.3030604@sgi.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <48DC58C8.3030604@sgi.com> X-Barracuda-Connect: wa-out-1112.google.com[209.85.146.180] X-Barracuda-Start-Time: 1222417033 X-Barracuda-Bayes: INNOCENT GLOBAL 0.3422 1.0000 -0.1808 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -0.18 X-Barracuda-Spam-Status: No, SCORE=-0.18 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.6540 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1455 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: kworth@gmail.com Precedence: bulk X-list: kdb Hi Jay, Thanks for the quick reply. I read through the last year or so of mailing list archives (stopped when I got to the notification of the 2.6.19 kernel release). Was helpful to catch up on the happenings and see what else had gone on. Didn't see any mentions of anyone having trouble like this (or much trouble at all) with serial ports. Let me see if I can describe the setup and perhaps someone might have a pointer- even if it's just something to try to eliminate a variable. I am running Ubuntu 7.04 (kernel 2.6.20 + ubuntu patches + latest 2.6.20 KDB patches) on i386 (dual core CPU). I added the line console=ttyS0,9600 to my kernel boot parameters and have the file /etc/event.d/ttyS0 set to spawn a getty process on ttyS0. I get the weird freeze behavior even when I invoke KDB using the ESC+KDB sequence, so it doesn't seem to be just a load-from-panic behavior (I have also loaded KDB from a panic and it exhibits this behavior). Unfortunately my system doesn't have a PS/2 keyboard port, so I'm left with serial and USB (it's an uhci/ehci controller- so sounds like this will not work). I'm really at a loss as to what could be happening here- when KDB is running, that's the only code executing in the CPU, right? So it's not like it's getting swapped out while another process runs, right? The only think I could think is that perhaps there is some weird buffering or polling going on in the serial driver/protocol/terminal setup. My connection on the other end is a PuTTY terminal running on a Windows XP machine with a known-to-be-working USB serial port. PuTTY is in its default settings, though I have also tried kicking the speed on both sides of the connection up to 115200 to see if things improved- it was faster, but I still encountered the intermittent freezes. Tomorrow I'll try a different terminal emulator like TeraTerm, and a different serial port (the native COM port instead of USB) to see if anything changes. If anyone has suggestions, please let me know. Thanks! If I can get this to work properly, it might be nice to see if I can backport the kdump patch into the 2.6.20 version of kdb, since I use kdump on this system, and right now I have to disable kdump before crashes will drop me into kdb. Am I correct in my understand that post-patch, a crash will cause the system to drop into kdb, then runing the "kdump" command will cause the kdump/kexec kernel to be execed? If so that sounds like what I'd want. -Kevin On Thu, Sep 25, 2008 at 8:36 PM, Jay Lan wrote: > Kevin Worth wrote: >> Hi All, > > Hi Kevin, > >> >> I set up a system with KDB and everything runs great, except that when >> I am in KDB on the serial console, it seems to hang intermittently >> (for several minutes) and then continue working again for a few >> seconds or so. I am grateful to have some immediate post-mortem >> debugging capability now on this system (since sometimes kdump fails >> due to memory corruption), but the process goes very slowly when the >> system hangs every couple times you go to type a command. >> >> I know this kernel is a bit old- is this an issue that has been fixed >> on newer versions but was not backported to the 2.6.20 version? > > Which arch were you running on and how did you set up your serial > console? I have not seen the intermittent stall problem you > described before. > >> Any >> ideas of where I can start? I've now tried two different serial ports >> and both are running at 9600 8-n-1, with flow control off. The problem >> seems to occur most often if I leave the console sitting for a few >> seconds, though I've also had it when I'm quickly interacting and >> typing commands. > > I let people more better on serial port setting to respond here. > >> >> Additionally, is the sgi ftp at >> ftp://oss.sgi.com/projects/kdb/download/v4.4/ the only place to find >> files for kdb? > > Yes. > >> It would be nice to have some of the patches that were >> added to the KDB patches for later kernels (i.e. ehci/uhci USB, >> kdump), but it doesn't seem particularly easy to tell which >> modifications are for which feature... > > That is true. You can look at the ChangLog at kdb/ and at > arch/{ia64,x86}/kdb/ directories. Major bug fixes/features are > described in the ChangeLog's. Unzipped patches will have complete > version of ChangeLog's. BTW, uhci USB feature has been backed out > since it caused regression in ohci. > >> I guess perhaps I could search >> the mailing list archives for the original patch submissions... any >> easier way? Does KDB exist in any online source control systems? The >> SGI CVS server no longer appears to contain it... > > Unfortunately, no. > >> are new versions >> just posted straight to the FTP site? > > Yes, it has been that way. We use internal RCS tree to maintain > the patches and newer versions are then placed at the FTP site. > > Regards, > jay > >> >> -Kevin >> --------------------------- >> 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 kworth@gmail.com Fri Sep 26 17:34:00 2008 Received: with ECARTIS (v1.0.0; list kdb); Fri, 26 Sep 2008 17:34:06 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m8R0XxHh012880 for ; Fri, 26 Sep 2008 17:34:00 -0700 X-ASG-Debug-ID: 1222475708-31c9031c0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from wa-out-1112.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id DBDC89972B4 for ; Fri, 26 Sep 2008 17:35:08 -0700 (PDT) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by cuda.sgi.com with ESMTP id CTFPp0N4PoQVGrdS for ; Fri, 26 Sep 2008 17:35:08 -0700 (PDT) Received: by wa-out-1112.google.com with SMTP id j5so608618wah.4 for ; Fri, 26 Sep 2008 17:35:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=P/VejxRl/0B/zOydGItdNwuANkmmsl8uywzGlqCUV3k=; b=IzDJzlceuHF3xzq+lFpcQFRWBWAjCMN/RYPRUur2wLVEXhRB0DttpFyvaF0RWBiYLf oG4eY0tviRK1RMySZf29CpYkkvbRZRo3l31rG96NVHsSDgdBZV3Shag5ySBiremYhaOI xwwO7cVvB7Bp/G2LOli6UYdpX81gSt/uaW59A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=YX2fZoC+CeWh/qgo/cDdpYRbqc6oPUb3C0C4QnaGGHvdVfRU4AdFfAthREUr2RBYsr bdrLV8uv1IU6zuobg6qetQjiJGad14du/gGAqEFe7PZs8YtrFy8Yt6oZbuwzvLxJS3bF RRP+Anxo83rbdsrNKWvPTypHbEN3AHD5bQDqc= Received: by 10.114.127.1 with SMTP id z1mr2272215wac.203.1222475708240; Fri, 26 Sep 2008 17:35:08 -0700 (PDT) Received: by 10.114.79.6 with HTTP; Fri, 26 Sep 2008 17:35:07 -0700 (PDT) Message-ID: Date: Fri, 26 Sep 2008 17:35:07 -0700 From: "Kevin Worth" To: KDB , "Jay Lan" X-ASG-Orig-Subj: [PATCH] Backport kdump capability to 2.6.20 kernel Subject: [PATCH] Backport kdump capability to 2.6.20 kernel MIME-Version: 1.0 Content-type: text/plain X-Barracuda-Connect: wa-out-1112.google.com[209.85.146.181] X-Barracuda-Start-Time: 1222475710 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -1001.00 X-Barracuda-Spam-Status: No, SCORE=-1001.00 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 Content-Transfer-Encoding: 8bit X-archive-position: 1456 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: kworth@gmail.com Precedence: bulk X-list: kdb Hi Jay and others, I've attached two patches that nearly backport KDB's kdump capability to the 2.6.20 kernel. I marked them as "ubuntu" because I'm patching against the Ubuntu 7.04 kernel, though the only difference as far as KDB is concerned is a couple lines in ohci-pci.c. I think I got the arch-independent part right, as I can apply the patch cleanly against my source tree. However, I haven't been able to test it yet because I can't apply the arch-dependent (i386) patch successfully. It appears that at some point an arch-independent (between i386 and x86_64) directory called "x86" was added. As such, I can't patch the files linux/arch/x86/kdb/kdba_support.c and linux/arch/x86/kernel/crash.c because they simply aren't there. Trying to figure out what I can do from here and would appreciate if anyone is able to lend a hand or some insight. -Kevin -- Binary/unsupported file stripped by Ecartis -- -- Type: application/octet-stream -- File: kdb-v4.4-2.6.20-common-6-ubuntu-2 -- Binary/unsupported file stripped by Ecartis -- -- Type: application/octet-stream -- File: kdb-v4.4-2.6.20-i386-3-ubuntu-2 --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.