From owner-kdb@oss.sgi.com Tue Aug 7 10:17:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f77HHbP04474 for kdb-outgoing; Tue, 7 Aug 2001 10:17:37 -0700 Received: from web12302.mail.yahoo.com (web12302.mail.yahoo.com [216.136.173.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f77HHaV04471 for ; Tue, 7 Aug 2001 10:17:36 -0700 Message-ID: <20010807171736.74196.qmail@web12302.mail.yahoo.com> Received: from [192.148.11.77] by web12302.mail.yahoo.com; Tue, 07 Aug 2001 10:17:36 PDT Date: Tue, 7 Aug 2001 10:17:36 -0700 (PDT) From: Daniel Stekloff Subject: IBM Netvista problems with hanging after "go" To: kdb@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-kdb@oss.sgi.com Precedence: bulk Sorry if this is a repeat question for the list. I am seeing the problem reported in the FAQ about system appearing hung after typing "go" on my single processor IBM NetVista. I can remotely log in and restart the gpm subsystem as suggested. I am running kernel 2.4.6 and kdb patch kdb-v1.8-2.4.6. I have also tried kernel and patches for 2.4.4 and 2.4.7 and I have tried other NetVistas. Has this bug been fixed? What is causing this problem? Thanks in advance, Dan stekloff@yahoo.com __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ From owner-kdb@oss.sgi.com Tue Aug 7 16:34:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f77NYE412887 for kdb-outgoing; Tue, 7 Aug 2001 16:34:14 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f77NYDV12872 for ; Tue, 7 Aug 2001 16:34:13 -0700 Received: from www23.ureach.com (IDENT:root@www23.ureach.com [172.16.2.51]) by ureach.com (8.9.1/8.8.5) with ESMTP id TAA21195 for ; Tue, 7 Aug 2001 19:33:38 -0400 Received: (from nobody@localhost) by www23.ureach.com (8.9.3/8.9.1) id TAA03891; Tue, 7 Aug 2001 19:34:07 -0400 Date: Tue, 7 Aug 2001 19:34:07 -0400 Message-Id: <200108072334.TAA03891@www23.ureach.com> To: kdb@oss.sgi.com From: Kapish K Reply-to: Subject: kdb query Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-vsuite-type: e Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello, I would like to understand the meaning of the following in the kdb output: firstly, when would kdb normally show unknown in the bt trace? I see a lot of output, but with no symbol information. The addresses are not in the 0xc**** range. Is it because of the fact that the addresses are not in the kernel address space range that it gives this unknown for everything? or is it because something is not compiled with -g? But for some other processes, when I do a btp pid, I do see output with symbol information even when those addresses do not fall in the 0xc**** range. What does the unknown in kdb output imply? second is, what does the thread column mean? We are seeing consistent oops on an smp system, and while trying to debug the problem with kdb, I get to a sensible kdb output of the current process on one processor, but for the other processor, the faulting code does not show any symbol information, and gives unknown all throughout. So, though I can see which process it is ( actually a daemon process among a group of daemons ), I am not able to see which portion of code is faulting for that processor. system drops into kdb and shows oops for that processor - but oops shows only register information. Or is there some other way, I can get more information for that process from this limited information in kdb? finally, what do the runs for the various processes mean? that they are in the run queue? any clarifications would be very helpful. TIA ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag From owner-kdb@oss.sgi.com Tue Aug 7 17:13:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f780Dqp18689 for kdb-outgoing; Tue, 7 Aug 2001 17:13:52 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f780DnV18674 for ; Tue, 7 Aug 2001 17:13:49 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id CAA763019 for ; Wed, 8 Aug 2001 02:13:18 +0200 (CEST) mail_from (kaos@melbourne.sgi.com) 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 KAA09655; Wed, 8 Aug 2001 10:12:26 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: kapish@ureach.com cc: kdb@oss.sgi.com Subject: Re: kdb query In-reply-to: Your message of "Tue, 07 Aug 2001 19:34:07 -0400." <200108072334.TAA03891@www23.ureach.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Aug 2001 10:12:26 +1000 Message-ID: <25530.997229546@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 7 Aug 2001 19:34:07 -0400, Kapish K wrote: > I would like to understand the meaning of the following in the >kdb output: >firstly, when would kdb normally show unknown in the bt trace? I assume you are talking about ix86 here. kdb tries to unwind the ix86 stack, making its best guess at where functions were called from. The problem with ix86 is that it is not always possible to do an extract stack decode. appears when kdb has got what it belives is the return address from the stack but that address does not fall inside the kernel or any module. It is likely that the stack unwind has found a false return address. The next time it oops, "set KDBDEBUG=0x19" then bt. That will produce a *big* trace of what kdb is doing with stack unwind, send the trace to me, not to the list. You will need a serial console to capture the trace output. Also I need to know which version of gcc you are using. >second is, what does the thread column mean? It is the address of the thread structure currently associated with the process. Unless the process used clone with CLONE_THREAD, you can ignore that field. It is only useful when debugging multi threaded applications, you can ignore that field. It is only useful when debugging multi threaded applications, you can ignore that field. It is only useful when debugging multi threaded applications >finally, what do the runs for the various processes mean? that >they are in the run queue? The status field for the process has it marked as runnable. If it is actually running on a cpu then it has '1' in the cpu column. Most processes are stopped waiting for an event. From owner-kdb@oss.sgi.com Tue Aug 7 17:16:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f780GKk19055 for kdb-outgoing; Tue, 7 Aug 2001 17:16:20 -0700 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 f780GJV19048 for ; Tue, 7 Aug 2001 17:16:19 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f780KeS29224 for ; Tue, 7 Aug 2001 17:20:41 -0700 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 KAA09661; Wed, 8 Aug 2001 10:14:53 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Daniel Stekloff cc: kdb@oss.sgi.com Subject: Re: IBM Netvista problems with hanging after "go" In-reply-to: Your message of "Tue, 07 Aug 2001 10:17:36 MST." <20010807171736.74196.qmail@web12302.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Aug 2001 10:14:53 +1000 Message-ID: <25565.997229693@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 7 Aug 2001 10:17:36 -0700 (PDT), Daniel Stekloff wrote: >I am seeing the problem reported in the FAQ about >system appearing hung after typing "go" on my single >processor IBM NetVista. I can remotely log in and >restart the gpm subsystem as suggested. I am running >kernel 2.4.6 and kdb patch kdb-v1.8-2.4.6. I have also >tried kernel and patches for 2.4.4 and 2.4.7 and I >have tried other NetVistas. > >Has this bug been fixed? What is causing this problem? I thought it had been fixed in kdb 0.6, you are the first person to report the bug in ages. Does the same problem occur if you use a serial console and only enter kdb via the serial console. That is, if you never type anything on the keyboard while kdb is active, does the keyboard work after typing go on the serial console? From owner-kdb@oss.sgi.com Tue Aug 7 17:24:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f780ObO20189 for kdb-outgoing; Tue, 7 Aug 2001 17:24:37 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f780OZV20186 for ; Tue, 7 Aug 2001 17:24:35 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f780TxW31371 for ; Tue, 7 Aug 2001 17:29:59 -0700 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 KAA09707; Wed, 8 Aug 2001 10:23:10 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: kapish@ureach.com, kdb@oss.sgi.com Subject: Re: kdb query In-reply-to: Your message of "Wed, 08 Aug 2001 10:12:26 +1000." <25530.997229546@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Aug 2001 10:23:10 +1000 Message-ID: <25826.997230190@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk Resend, I accidentally hit send too soon. On Tue, 7 Aug 2001 19:34:07 -0400, Kapish K wrote: > I would like to understand the meaning of the following in the >kdb output: >firstly, when would kdb normally show unknown in the bt trace? I assume you are talking about ix86 here. kdb tries to unwind the ix86 stack, making its best guess at where functions were called from. The problem with ix86 is that it is not always possible to do an exact stack decode, due to lack of frame pointers and non-standard kernel frames. appears when kdb has got what it believes is the return address from the stack but that address does not fall inside the kernel or any module. It is likely that the stack unwind has found a false return address. Alternatively your run time system might be using an old version of insmod that does not add module symbols to the kallsyms table. The next time it oops, "set KDBDEBUG=0x19" then bt. That will produce a *big* trace of what kdb is doing with stack unwind, send the trace to me, not to the list. You will need a serial console to capture the trace output. Also I need to know which version of gcc and insmod you are using. >second is, what does the thread column mean? It is the address of the thread structure currently associated with the process. Unless the process used clone with CLONE_THREAD, you can ignore that field, it is only useful when debugging multi threaded applications. >finally, what do the runs for the various processes mean? that >they are in the run queue? The status field for the process has it marked as runnable. If it is actually running on a cpu then it has '1' in the cpu column. Most processes are stopped waiting for an event. From owner-kdb@oss.sgi.com Wed Aug 8 10:34:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f78HYU524984 for kdb-outgoing; Wed, 8 Aug 2001 10:34:30 -0700 Received: from web12304.mail.yahoo.com (web12304.mail.yahoo.com [216.136.173.102]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f78HYSV24981 for ; Wed, 8 Aug 2001 10:34:28 -0700 Message-ID: <20010808173422.76172.qmail@web12304.mail.yahoo.com> Received: from [192.148.11.77] by web12304.mail.yahoo.com; Wed, 08 Aug 2001 10:34:22 PDT Date: Wed, 8 Aug 2001 10:34:22 -0700 (PDT) From: Daniel Stekloff Subject: Re: IBM Netvista problems with hanging after "go" To: Keith Owens Cc: kdb@oss.sgi.com In-Reply-To: <25565.997229693@kao2.melbourne.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-kdb@oss.sgi.com Precedence: bulk --- Keith Owens wrote: > On Tue, 7 Aug 2001 10:17:36 -0700 (PDT), > Daniel Stekloff wrote: > >I am seeing the problem reported in the FAQ about > >system appearing hung after typing "go" on my > single > >processor IBM NetVista. I can remotely log in and > >restart the gpm subsystem as suggested. I am > running > >kernel 2.4.6 and kdb patch kdb-v1.8-2.4.6. I have > also > >tried kernel and patches for 2.4.4 and 2.4.7 and I > >have tried other NetVistas. > > > >Has this bug been fixed? What is causing this > problem? > > I thought it had been fixed in kdb 0.6, you are the > first person to > report the bug in ages. Does the same problem occur > if you use a > serial console and only enter kdb via the serial > console. That is, if > you never type anything on the keyboard while kdb is > active, does the > keyboard work after typing go on the serial console? I hooked up a serial console and ran kdb over the serial console. That worked fine. I could get into kdb and return after typing "go". But, once I entered the kdb on the serial line, the keyboard on my NetVista locked up and the NetVista wouldn't return until I restarted gpm from the serial console. The keyboard lights that flash when in the kdb stay lit once "go" is typed on the serial console. I also tried changing keyboards. Normally I use a Microsoft ergonomic keyboard, but I did try out a standard keyboard. Where is the problem occurring? Maybe I can play with it a bit to get it to work correctly. Thank you for your assistance. __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ From owner-kdb@oss.sgi.com Wed Aug 8 22:36:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f795aq305159 for kdb-outgoing; Wed, 8 Aug 2001 22:36:52 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f795apV05156 for ; Wed, 8 Aug 2001 22:36:51 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id WAA02778 for ; Wed, 8 Aug 2001 22:34:46 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 PAA17595; Thu, 9 Aug 2001 15:35:31 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: kapish@ureach.com Cc: kdb@oss.sgi.com Subject: Re: kdb query In-reply-to: Your message of "Wed, 08 Aug 2001 14:17:01 -0400." <200108081817.OAA18420@www20.ureach.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Aug 2001 15:35:31 +1000 Message-ID: <10746.997335331@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Wed, 8 Aug 2001 14:17:01 -0400, Kapish K wrote: > Thanks for the info. I was able to get the KDBDEBUG set on and >capture the output. The output on processor 0 is able to resolve >the symbols. The one on processor 1 is not. The gcc and modutils >are from Red Hat 7.1 distribution. The kdb output is attached. bt EBP EIP Function(args) kdb_get_next_ar: arend=0xf2cfbc57 func=0x0 pc=0x9c3f1cf8 fp=0xb735e8f2 kdb_get_next_ar: callee not in kernel kdba_prologue: code=0x0 pc=0x0 sp=0xf2cfbc57 fp=0xb735e8f2 pc==0: ret=0xcfbc68f8 kdb_get_next_ar: callee activation record start=0xf2cfbc5b end=0xf2cfbc57 ret=0xcfbc68f8 oldfp=0x0 fp=0x0 locals=0 regs=0 setup=4 This data is complete garbage. The program count is 0x9c3f1cf8 which is outside the kernel and modules. Normally that would indicate your code has taken a branch via an undefined function pointer. However the stack pointer has values like 0xf2cfbc57 which is flatly impossible. All kernel stack addresses are 4 byte aligned, that sp value cannot occur in a valid kernel. It looks like something has corrupted the registers. The registers are saved in the process structure, the process stack is at the top of the process structure and fills downwards. Is there any chance that your code has gone recursive or allocated a large structure on stack and overwritten the start of the process structure? Remember that ix86 kernel stacks are limited to about 6Kb. The only useful field in that trace is ret=0xcfbc68f8, everything else looks corrupt. Check where 0xcfbc68f8 is, it might help track down what is corrupting the registers. From owner-kdb@oss.sgi.com Thu Aug 9 18:19:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7A1Jq500400 for kdb-outgoing; Thu, 9 Aug 2001 18:19:52 -0700 Received: from ctv.es ([213.96.153.12]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7A1JnV00393 for ; Thu, 9 Aug 2001 18:19:50 -0700 Message-ID: <169852001851012159740@ctv.es> X-EM-Version: 5, 0, 0, 21 X-EM-Registration: #01B0530810E603002D00 X-Priority: 3 Reply-To: clean@ctv.es X-MSMail-Priority: Normal From: "Clean World Hispania" To: kdb@oss.sgi.com Subject: ACTIVADORES BIOLÓGICOS PARA ELIMINAR OLORES. ¡PUBLICIDAD! Date: Fri, 10 Aug 2001 03:21:59 +0200 MIME-Version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f7A1JpV00394 Sender: owner-kdb@oss.sgi.com Precedence: bulk Activadores biológicos naturales para eliminar olores en pozos sépticos, depuradoras, etc. Tratamientos de Purines, Alpechin, Alpeorujo etc. http://www.ctv.es/clean_world_hispania/ http://www.ctv.es/clean_world_hispania/odour.htm http://www.ctv.es/clean_world_hispania/fosassepticaspozossepticos.htm http://www.ctv.es/clean_world_hispania/enviosPOZOSNEGROS.html http://www.ctv.es/clean_world_hispania/PEDIDO.htm ¡PUBLICIDAD! Baja en clean@ctv.es Poligono Asuarán nave 16 48950 Asua Vizcaya 944710500 - Fax 944711324 From owner-kdb@oss.sgi.com Tue Aug 14 14:35:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7ELZdI21758 for kdb-outgoing; Tue, 14 Aug 2001 14:35:39 -0700 Received: from mercury.lss.emc.com (mercury.eng.emc.com [168.159.40.77]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7ELZbj21755 for ; Tue, 14 Aug 2001 14:35:37 -0700 Received: by mercury.eng.emc.com with Internet Mail Service (5.5.2653.19) id ; Tue, 14 Aug 2001 17:35:29 -0400 Message-ID: <69C8DD8179FCD41187CC0003470E0196DD421A@srstart.lss.emc.com> From: "moumni, ismail" To: "'kdb@oss.sgi.com'" Subject: kernel 2.4.4ga Date: Tue, 14 Aug 2001 17:35:23 -0400 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 hi, I would like to know if you have a version of kdb that runs on a 2.4.4ga kernel. Your answer is greatly appreciated. thanks, Ismail Moumni From owner-kdb@oss.sgi.com Wed Aug 15 23:14:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7G6EEw13954 for kdb-outgoing; Wed, 15 Aug 2001 23:14:14 -0700 Received: from cs.brown.edu (fullabull.cs.brown.edu [128.148.32.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7G6EDj13951 for ; Wed, 15 Aug 2001 23:14:13 -0700 Received: from cslab5e.cs.brown.edu (cslab5e.cs.brown.edu [128.148.33.222]) by cs.brown.edu (8.9.3/8.9.3) with ESMTP id CAA29429 for ; Thu, 16 Aug 2001 02:14:03 -0400 (EDT) Received: (from rmanches@localhost) by cslab5e.cs.brown.edu (8.9.0/8.9.0) id CAA00876 for kdb@oss.sgi.com; Thu, 16 Aug 2001 02:14:07 -0400 (EDT) Date: Thu, 16 Aug 2001 02:14:07 -0400 From: r To: kdb@oss.sgi.com Subject: dropping into kdb from X windows Message-ID: <20010816021407.B534@cslab5e.cs.brown.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-kdb@oss.sgi.com Precedence: bulk when entering kdb from X I am unable to see any output. I can type commands, but with out any visual feedback it is sort of useless. Is this possible? -r From owner-kdb@oss.sgi.com Wed Aug 15 23:56:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7G6uxo15132 for kdb-outgoing; Wed, 15 Aug 2001 23:56:59 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7G6uxj15129 for ; Wed, 15 Aug 2001 23:56:59 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id XAA22319 for ; Wed, 15 Aug 2001 23:56:42 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 QAA28158; Thu, 16 Aug 2001 16:55:39 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: r cc: kdb@oss.sgi.com Subject: Re: dropping into kdb from X windows In-reply-to: Your message of "Thu, 16 Aug 2001 02:14:07 -0400." <20010816021407.B534@cslab5e.cs.brown.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Aug 2001 16:55:39 +1000 Message-ID: <12867.997944939@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Thu, 16 Aug 2001 02:14:07 -0400, r wrote: >when entering kdb from X I am unable to see any output. I can type >commands, but with out any visual feedback it is sort of useless. Is >this possible? kdb requires a text mode console. The code to switch in and out of X mode is huge, there is no way that kdb can support every video driver. Either type kdb commands blind or use a serial console. From owner-kdb@oss.sgi.com Thu Aug 16 03:39:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7GAdVJ22870 for kdb-outgoing; Thu, 16 Aug 2001 03:39:31 -0700 Received: from magnifire.net (IDENT:root@genie.magnifire.com [212.150.5.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7GAdTj22867 for ; Thu, 16 Aug 2001 03:39:30 -0700 Received: from there ([212.150.5.72]) by magnifire.net (8.11.2/8.11.2) with SMTP id f7GAcRR22441 for ; Thu, 16 Aug 2001 13:38:27 +0300 Message-Id: <200108161038.f7GAcRR22441@magnifire.net> Content-Type: text/plain; charset="iso-8859-1" From: Felix Rubinstein Reply-To: felixr@magnifire.net To: kdb@oss.sgi.com Subject: Linux kenel 2.4.x Date: Thu, 16 Aug 2001 13:39:54 -0200 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello ! Does kdb suppost linux kernels 2.4.x ? What should I do to run kdb under 2.4.x ? Thank you, Felix R. From owner-kdb@oss.sgi.com Thu Aug 16 05:32:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7GCWcQ26825 for kdb-outgoing; Thu, 16 Aug 2001 05:32:38 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7GCWZj26819 for ; Thu, 16 Aug 2001 05:32:36 -0700 Received: (qmail 31246 invoked from network); 16 Aug 2001 12:32:33 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 16 Aug 2001 12:32:33 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: felixr@magnifire.net cc: kdb@oss.sgi.com Subject: Re: Linux kenel 2.4.x In-reply-to: Your message of "Thu, 16 Aug 2001 13:39:54 -0200." <200108161038.f7GAcRR22441@magnifire.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Aug 2001 22:32:32 +1000 Message-ID: <16750.997965152@ocs3.ocs-net> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Thu, 16 Aug 2001 13:39:54 -0200, Felix Rubinstein wrote: >Does kdb suppost linux kernels 2.4.x ? >What should I do to run kdb under 2.4.x ? It only supports 2.4.x. Get whichever patch fits your kernel from http://oss.sgi.com/projects/kdb/download/ix86/. Patches for older kernels are in the old/ directory. From owner-kdb@oss.sgi.com Mon Aug 20 09:46:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7KGkIb25105 for kdb-outgoing; Mon, 20 Aug 2001 09:46:18 -0700 Received: from mail.b2i-toulouse.com (host.97.67.23.62.rev.coltfrance.com [62.23.67.97]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7KGkFj25102 for ; Mon, 20 Aug 2001 09:46:16 -0700 Received: from b2i-toulouse.com (wilson.b2i-toulouse.com [192.168.0.25] (may be forged)) by mail.b2i-toulouse.com (8.11.0/8.11.0) with ESMTP id f7KGk8v09953 for ; Mon, 20 Aug 2001 18:46:08 +0200 Message-ID: <3B814033.D34B8A55@b2i-toulouse.com> Date: Mon, 20 Aug 2001 18:52:03 +0200 From: =?iso-8859-1?Q?S=E9bastien?= GAUME Organization: b2i-toulouse X-Mailer: Mozilla 4.75 [fr] (WinNT; U) X-Accept-Language: fr MIME-Version: 1.0 To: kdb@oss.sgi.com Subject: kdb doesn't start ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello, I've just installed kdb version 1.5 with linux 2.2.18, redhat 6.1. What I've done is : - install modutils 2.3.11 - download and unzip the patch - apply the patch in my linux source tree - $ cd linux $ patch -p1 < kdb-2.2.18.... $ make xconfig - in the " xconfig kernel hacking" window, I've chosen the options that enable * the use of a kernel debugger, * the use of frame pointers * the kdb running automatically after booting. But, after rebooting, I didn't see the flag "kdb" in /proc/sys/kernel. Thus, the kdb command seems not to work... What did I miss ? Where am I wrong ? Thank you for your help Sebastien From owner-kdb@oss.sgi.com Mon Aug 20 09:50:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7KGo9p25179 for kdb-outgoing; Mon, 20 Aug 2001 09:50:09 -0700 Received: from mail.b2i-toulouse.com (host.97.67.23.62.rev.coltfrance.com [62.23.67.97]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7KGo7j25176 for ; Mon, 20 Aug 2001 09:50:07 -0700 Received: from b2i-toulouse.com (wilson.b2i-toulouse.com [192.168.0.25] (may be forged)) by mail.b2i-toulouse.com (8.11.0/8.11.0) with ESMTP id f7KGo0v09993 for ; Mon, 20 Aug 2001 18:50:00 +0200 Message-ID: <3B81411B.BA14B050@b2i-toulouse.com> Date: Mon, 20 Aug 2001 18:55:55 +0200 From: =?iso-8859-1?Q?S=E9bastien?= GAUME Organization: b2i-toulouse X-Mailer: Mozilla 4.75 [fr] (WinNT; U) X-Accept-Language: fr MIME-Version: 1.0 To: kdb@oss.sgi.com Subject: KDB doesn't start ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello, I've just installed kdb version 1.5 with linux 2.2.18, redhat 6.1. What I've done is : - install modutils 2.3.11 - download and unzip the patch - apply the patch in my linux source tree - $ cd linux $ patch -p1 < kdb-2.2.18.... $ make xconfig - in the " xconfig kernel hacking" window, I've chosen the options that enable * the use of a kernel debugger, * the use of frame pointers * the kdb running automatically after booting. But, after rebooting, I didn't see the flag "kdb" in /proc/sys/kernel. Thus, the kdb command seems not to work... What did I miss ? Where am I wrong ? Thank you for your help Sebastien From owner-kdb@oss.sgi.com Mon Aug 20 10:29:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7KHTk226242 for kdb-outgoing; Mon, 20 Aug 2001 10:29:46 -0700 Received: from eagle.verisign.com (eagle.verisign.com [208.206.241.105]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7KHTij26239 for ; Mon, 20 Aug 2001 10:29:44 -0700 Received: from vhqpostal-gw2.verisign.com (gateway.verisign.com [63.104.27.100]) by eagle.verisign.com (8.9.3/BCH1.7.1) with ESMTP id KAA20019; Mon, 20 Aug 2001 10:32:52 -0700 (PDT) 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 RBT7B6D7; Mon, 20 Aug 2001 10:27:27 -0700 Received: by slurndal-lnx.verisign.com; Mon, 20 Aug 2001 10:29:11 -0700 Message-Id: <200108201729.KAA25075@slurndal-lnx.verisign.com> Subject: Re: kdb doesn't start ? To: sgaume@b2i-toulouse.com (=?iso-8859-1?Q?S=E9bastien?= GAUME) Date: Mon, 20 Aug 2001 10:29:11 -0700 (PDT) Cc: kdb@oss.sgi.com In-Reply-To: <3B814033.D34B8A55@b2i-toulouse.com> from "=?iso-8859-1?Q?S=E9bastien?= GAUME" at Aug 20, 2001 06:52:03 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 > > Hello, > > I've just installed kdb version 1.5 with linux 2.2.18, redhat 6.1. What > I've done is : > - install modutils 2.3.11 > - download and unzip the patch > - apply the patch in my linux source tree > - $ cd linux > $ patch -p1 < kdb-2.2.18.... > $ make xconfig > - in the " xconfig kernel hacking" window, I've chosen the options that > enable > * the use of a kernel debugger, > * the use of frame pointers > * the kdb running automatically after booting. > > But, after rebooting, I didn't see the flag "kdb" in /proc/sys/kernel. > Thus, the kdb command seems not to work... > > What did I miss ? Where am I wrong ? > > Thank you for your help > > Sebastien > I'm not sure what you mean by the 'kdb command'. There is no such command that can be executed from a shell. To invoke KDB, one either uses the keyboard sequences (pause key on PC keyboard, control-a on serial port) or uses the 'kdb' flag to lilo causing kdb to gain control of the kernel early in the boot process. From there, one can set breakpoints, examine kernel memory, check thread stacks, etc. scott From owner-kdb@oss.sgi.com Tue Aug 21 08:35:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7LFZtc24061 for kdb-outgoing; Tue, 21 Aug 2001 08:35:55 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7LFZs924058 for ; Tue, 21 Aug 2001 08:35:54 -0700 Received: from www20.ureach.com (IDENT:root@www20.ureach.com [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id LAA08247 for ; Tue, 21 Aug 2001 11:35:48 -0400 Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id LAA12633; Tue, 21 Aug 2001 11:35:48 -0400 Date: Tue, 21 Aug 2001 11:35:48 -0400 Message-Id: <200108211535.LAA12633@www20.ureach.com> To: kdb@oss.sgi.com From: Kapish K Reply-to: Subject: total hang Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-vsuite-type: e Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello, We see a wierd situation here - when we run some tests on an smp system, we see a total system freeze... whats' interesting is that we turn on magic-sysrq and kdb, but still we are totally locked on the keyboard - can't get to kdb or make the magic-sysrq work.. is there any other hacks to get into the system one way or the other and get some info.? network doesn't work either - no ping packets.. TIA ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag From owner-kdb@oss.sgi.com Tue Aug 21 09:46:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7LGkLK25239 for kdb-outgoing; Tue, 21 Aug 2001 09:46:21 -0700 Received: from eagle.verisign.com (eagle.verisign.com [208.206.241.105]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7LGkJ925233 for ; Tue, 21 Aug 2001 09:46:19 -0700 Received: from vhqpostal-gw2.verisign.com (gateway.verisign.com [63.104.27.100]) by eagle.verisign.com (8.9.3/BCH1.7.1) with ESMTP id JAA24677; Tue, 21 Aug 2001 09:49:28 -0700 (PDT) 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 RBT7CWZ9; Tue, 21 Aug 2001 09:43:58 -0700 Received: by slurndal-lnx.verisign.com; Tue, 21 Aug 2001 09:45:42 -0700 Message-Id: <200108211645.JAA26342@slurndal-lnx.verisign.com> Subject: Re: total hang To: kapish@ureach.com Date: Tue, 21 Aug 2001 09:45:42 -0700 (PDT) Cc: kdb@oss.sgi.com In-Reply-To: <200108211535.LAA12633@www20.ureach.com> from "Kapish K" at Aug 21, 2001 11:35:48 AM 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 > > Hello, > We see a wierd situation here - when we run some tests on > an smp system, we see a total system freeze... whats' > interesting is that we turn on magic-sysrq and kdb, but still we > are totally locked on the keyboard - can't get to kdb or make > the magic-sysrq work.. is there any other hacks to get into the > system one way or the other and get some info.? network doesn't > work either - no ping packets.. > TIA What kernel, 2.2 or 2.4? If you can manage to generate a non-maskable interrupt, you should be able to force control to kdb. Some hardware platforms include an NMI button, but most don't. One can build fairly simple hardware using the simple ISA or PCI cards to generate an NMI, I'm not sure if anyone sells such a product however. Sounds like you're in a tight loop with all interrupts masked or disabled. scott From owner-kdb@oss.sgi.com Tue Aug 21 15:55:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7LMtjg32641 for kdb-outgoing; Tue, 21 Aug 2001 15:55:45 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7LMtg932638 for ; Tue, 21 Aug 2001 15:55:42 -0700 Received: (qmail 30603 invoked from network); 21 Aug 2001 22:55:38 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 21 Aug 2001 22:55:38 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: kapish@ureach.com cc: kdb@oss.sgi.com Subject: Re: total hang In-reply-to: Your message of "Tue, 21 Aug 2001 11:35:48 -0400." <200108211535.LAA12633@www20.ureach.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Aug 2001 08:55:37 +1000 Message-ID: <6720.998434537@ocs3.ocs-net> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Tue, 21 Aug 2001 11:35:48 -0400, Kapish K wrote: > We see a wierd situation here - when we run some tests on >an smp system, we see a total system freeze... whats' >interesting is that we turn on magic-sysrq and kdb, but still we >are totally locked on the keyboard - can't get to kdb or make >the magic-sysrq work.. is there any other hacks to get into the >system one way or the other and get some info.? network doesn't >work either - no ping packets.. Sounds like a disabled spin loop, interrupts are being ignored. Use the non maskable interrupt, see Documentation/nmi_watchdog.txt. From owner-kdb@oss.sgi.com Thu Aug 23 11:00:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7NI07B01141 for kdb-outgoing; Thu, 23 Aug 2001 11:00:07 -0700 Received: from web13808.mail.yahoo.com (web13808.mail.yahoo.com [216.136.175.18]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7NI04d01138 for ; Thu, 23 Aug 2001 11:00:04 -0700 Message-ID: <20010823180004.63406.qmail@web13808.mail.yahoo.com> Received: from [63.87.1.106] by web13808.mail.yahoo.com; Thu, 23 Aug 2001 11:00:04 PDT Date: Thu, 23 Aug 2001 11:00:04 -0700 (PDT) From: blank blank Subject: KDB/mips To: kdb@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-kdb@oss.sgi.com Precedence: bulk I found this on the kdb website: Release v1.0 supports the following new features and bugfixes. [snip] Support for mips architecture ...but I can't seem to find any files in the downloads section for anything other than x86 or ia64. [Checked the FAQ and list archives, too.] Does mips support exist? Did it exist and then get dropped? I'm running 2.4.0-test5, about to upgrade to 2.4.5. Any info or advice would be appreciated. Thanks, Eric Uhrhane jen_060272@yahoo.com __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ From owner-kdb@oss.sgi.com Thu Aug 23 16:15:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7NNFkd03791 for kdb-outgoing; Thu, 23 Aug 2001 16:15:46 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7NNFgd03788 for ; Thu, 23 Aug 2001 16:15:43 -0700 Received: (qmail 24943 invoked from network); 23 Aug 2001 23:15:40 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 23 Aug 2001 23:15:40 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: blank blank cc: kdb@oss.sgi.com Subject: Re: KDB/mips In-reply-to: Your message of "Thu, 23 Aug 2001 11:00:04 MST." <20010823180004.63406.qmail@web13808.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Aug 2001 09:15:39 +1000 Message-ID: <17215.998608539@ocs3.ocs-net> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Thu, 23 Aug 2001 11:00:04 -0700 (PDT), blank blank wrote: >I found this on the kdb website: > > Release v1.0 supports the following new features > and bugfixes. > [snip] > Support for mips architecture Sorry, that is a mistake. kdb does not support mips and there are no plans to do so, Linux on mips is not an important target for SGI. If somebody writes the arch dependent code for kdb then we will take the patches but we do not plan to do them ourselves. From owner-kdb@oss.sgi.com Fri Aug 24 14:26:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7OLQkR26314 for kdb-outgoing; Fri, 24 Aug 2001 14:26:46 -0700 Received: from thalia.fm.intel.com (fmfdns02.fm.intel.com [132.233.247.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7OLQdd26311 for ; Fri, 24 Aug 2001 14:26:44 -0700 Received: from fmsmsxvs040.fm.intel.com (fmsmsxv040-1.fm.intel.com [132.233.48.108]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.41 2001/07/09 21:06:22 root Exp $) with SMTP id VAA18223 for ; Fri, 24 Aug 2001 21:26:39 GMT Received: from fmsmsx17.intel.com ([132.233.48.17]) by fmsmsxvs040.fm.intel.com (NAVGW 2.5.1.6) with SMTP id M2001082414261913091 for ; Fri, 24 Aug 2001 14:26:19 -0700 Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 24 Aug 2001 14:27:38 -0700 Message-ID: <10C8636AE359D4119118009027AE99870CE2F921@FMSMSX34> From: "Howell, David P" To: kdb@oss.sgi.com Subject: Watchdog timer support in kdb Date: Fri, 24 Aug 2001 14:26:35 -0700 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 Hope that this isn't a repeat from the past. Looking through the kdb code there is definitely watchdog timer support. Does the code support only generic IA32 IO_APIC/PerfCounters flavor of watchdog timers or are hardware watchdog timer cards that generate NMI on expire supported as well? Thanks! David Howell From owner-kdb@oss.sgi.com Fri Aug 24 14:34:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7OLYGm26528 for kdb-outgoing; Fri, 24 Aug 2001 14:34:16 -0700 Received: from eagle.verisign.com (eagle.verisign.com [208.206.241.105]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7OLYEd26525 for ; Fri, 24 Aug 2001 14:34:14 -0700 Received: from vhqpostal-gw2.verisign.com (gateway.verisign.com [63.104.27.100]) by eagle.verisign.com (8.9.3/BCH1.7.1) with ESMTP id OAA07604; Fri, 24 Aug 2001 14:37:25 -0700 (PDT) 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 RBT7FL7H; Fri, 24 Aug 2001 14:31:59 -0700 Received: by slurndal-lnx.verisign.com; Fri, 24 Aug 2001 14:33:37 -0700 Message-Id: <200108242133.OAA22253@slurndal-lnx.verisign.com> Subject: Re: Watchdog timer support in kdb To: david.p.howell@intel.com (Howell, David P) Date: Fri, 24 Aug 2001 14:33:37 -0700 (PDT) Cc: kdb@oss.sgi.com In-Reply-To: <10C8636AE359D4119118009027AE99870CE2F921@FMSMSX34> from "Howell, David P" at Aug 24, 2001 02:26:35 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 > > Hope that this isn't a repeat from the past. > > Looking through the kdb code there is definitely watchdog timer support. > Does the code support only > generic IA32 IO_APIC/PerfCounters flavor of watchdog timers or are hardware > watchdog timer cards > that generate NMI on expire supported as well? KDB does not support _programming_ hardware watchdog timer cards, however KDB does support NMI, no matter how it is delivered. One can use the appropriate kdb commands to write to the hardware registers to program the board, however. scott > > Thanks! > > David Howell > From owner-kdb@oss.sgi.com Sun Aug 26 23:21:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7R6L5e14911 for kdb-outgoing; Sun, 26 Aug 2001 23:21:05 -0700 Received: from mail-relay-vsat2.ernet.in ([202.41.99.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7R6Kxd14904 for ; Sun, 26 Aug 2001 23:21:01 -0700 Received: from matrix.reccal.ernet.in (IDENT:mc98m03@matrix.reccal.ernet.in [202.41.105.50]) by mail-relay-vsat2.ernet.in (8.9.3/8.9.3) with ESMTP id KAA30709 for ; Mon, 27 Aug 2001 10:07:19 +0530 Received: (from mc98m03@localhost) by matrix.reccal.ernet.in (8.8.7/8.8.7) id LAA09250; Mon, 27 Aug 2001 11:40:51 +0530 Date: Mon, 27 Aug 2001 11:40:51 +0530 (IST) From: "Bijoy Kumar K.M." To: kdb@oss.sgi.com Subject: Problem with the pause Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello I have installed the kdb on my system withe kernel 2.4.5 and can get into the kdb mode if the kdb=early flag is given at boot time. But if I boot my system normally and hit the pause key at any later stage I get a kernel panic. The messages are somewhat like this In interrupt handler, not syncing. Not executing a kdb command No longjump available for recovery. Allowing the event to happen And the system hangs. Can you please tell me why it is so? Thanks ! Bijoy From owner-kdb@oss.sgi.com Mon Aug 27 00:03:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7R733Q16052 for kdb-outgoing; Mon, 27 Aug 2001 00:03:03 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7R731d16047 for ; Mon, 27 Aug 2001 00:03:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id AAA25839 for ; Mon, 27 Aug 2001 00:02:40 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 SAA24836; Mon, 27 Aug 2001 18:01:30 +1100 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: "Bijoy Kumar K.M." cc: kdb@oss.sgi.com Subject: Re: Problem with the pause In-reply-to: Your message of "Mon, 27 Aug 2001 11:40:51 +0530." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Aug 2001 17:01:30 +1000 Message-ID: <6677.998895690@kao2.melbourne.sgi.com> Sender: owner-kdb@oss.sgi.com Precedence: bulk On Mon, 27 Aug 2001 11:40:51 +0530 (IST), "Bijoy Kumar K.M." wrote: > I have installed the kdb on my system withe kernel 2.4.5 and can >get into the kdb mode if the kdb=early flag is given at boot time. But if >I boot my system normally and hit the pause key at any later stage I get a >kernel panic. The messages are somewhat like this > > In interrupt handler, not syncing. > Not executing a kdb command > No longjump available for recovery. > Allowing the event to happen >And the system hangs. It works for me. Did you use the correct patch? You should be using ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.8-2.4.5.gz for that kernel. Is it a standard 2.4.5 kernel or has it been patched by a distributor? If it has been patched then there is no guarantee that kdb will work. Assuming you have the correct patch and you are applying it to a clean kernel, you need to debug kdb. You will need to compile and boot with a serial console, see Documentation/serial-console.txt. Boot with kdb=early, enter the command "set KDBDEBUG=0xff" and go. Capture all the kdb debug output on the serial console and send it to me. NOTE: I need the exact output, not "somewhat like this". From owner-kdb@oss.sgi.com Tue Aug 28 21:47:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7T4lIf13031 for kdb-outgoing; Tue, 28 Aug 2001 21:47:18 -0700 Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7T4l5d13027 for ; Tue, 28 Aug 2001 21:47:05 -0700 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id AAA34138 for ; Wed, 29 Aug 2001 00:44:47 -0400 Received: from maze.in.ibm.com (maze.in.ibm.com [9.186.135.29]) by northrelay03.pok.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f7T4euP21220 for ; Wed, 29 Aug 2001 00:40:57 -0400 Received: (from vamsi@localhost) by maze.in.ibm.com (8.11.2/8.11.2) id f7T4qa704966 for kdb@oss.sgi.com; Wed, 29 Aug 2001 10:22:36 +0530 Date: Wed, 29 Aug 2001 10:22:35 +0530 From: "Vamsi Krishna S ." To: kdb@oss.sgi.com Subject: [PATCH] embed width and count in md/mm commands Message-ID: <20010829102235.A4919@in.ibm.com> Reply-To: r1vamsi@in.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-kdb@oss.sgi.com Precedence: bulk Hello, Here is a patch to implement embedding width and count options in the md and mm commands. The patch is against KDB v1.8. As Keith put it elsewhere, some hardware requires that accesses be a specific width, this can be achieved by setting BYTESPERWORD but it is awkward. We want md1 to read one byte, md2, md4, md8 commands. All can have a count field, e.g. md1c8 reads 8 bytes one at a time. mm1, mm2, mm4, mm8 to set memory no count field. The implementation tries to make minimal modifications to the existing code. In addition to the relatively simple changes to kdb_md and kdb_mm, I had to modify kdb_parse so that it can parse "md1c20" to be the "md" command. For a normal cmd shortcut, the typed in command length is less than the length of the actual command, whereas in this case, it is the opposite, that needed another loop over all commands in kdb_parse. Comments? Regards, Vamsi Krishna S. Linux Technology Center, IBM Software Labs, Bangalore. --- 246-kdb-pure/kdb/kdbmain.c Tue Aug 28 19:00:26 2001 +++ 246-kdb/kdb/kdbmain.c Wed Aug 29 10:08:37 2001 @@ -620,6 +620,23 @@ } } } + + /* + * If we don't find a command by this name, see if the first + * few characters of this match any of the known commands. + * e.g., md1c20 should match md. + */ + if (i == KDB_MAX_COMMANDS) { + for(tp=kdb_commands, i=0; i < KDB_MAX_COMMANDS; i++,tp++) { + if (tp->cmd_name) { + if (strncmp(argv[0], + tp->cmd_name, + strlen(tp->cmd_name))==0) { + break; + } + } + } + } if (i < KDB_MAX_COMMANDS) { int result, no_watchdog; @@ -1460,9 +1477,13 @@ /* * kdb_md * - * This function implements the 'md', 'mdr' and 'mds' commands. + * This function implements the 'md', 'md1', 'md2', 'md4', 'md8' + * 'mdr' and 'mds' commands. * * md|mds [ [ []]] + * mdWcN [ [ []]] + * where W = is the width (1, 2, 4 or 8) and N is the count. + * for eg., md1c20 reads 20 bytes, 1 at a time. * mdr , * * Inputs: @@ -1484,7 +1505,6 @@ { char fmtchar; char fmtstr[64]; - int radix, count, width; kdb_machreg_t addr; unsigned long word; long offset = 0; @@ -1493,50 +1513,62 @@ int nextarg; int nosect = 0; static kdb_machreg_t lastaddr; - static unsigned long lastcount; + static unsigned long last_line_count; static unsigned long lastradix; - char lastbuf[50]; int symbolic = 0; + int line_count = 8; + int radix = 16; + int width = sizeof(kdb_machreg_t); - /* - * Defaults in case the relevent environment variables are unset - */ - radix = 16; - count = 8; - width = sizeof(kdb_machreg_t); + kdbgetintenv("BYTESPERWORD", &width); + kdbgetintenv("MDCOUNT", &line_count); + kdbgetintenv("RADIX", &radix); + kdbgetintenv("NOSECT", &nosect); - if (strcmp(argv[0], "mdr") == 0 && argc != 2) - return KDB_ARGCOUNT; + if (strcmp(argv[0], "mdr") == 0) { + if (argc != 2) + return KDB_ARGCOUNT; + } else if (argv[0][2]) { + width = (int)(argv[0][2] - '0'); + if (argv[0][3] == 'c') { + int count; + count = simple_strtoul(&argv[0][4], 0, 0); + line_count = ((count * width) + 15) / 16; + } + } if (argc == 0) { if (lastaddr == 0) return KDB_ARGCOUNT; - sprintf(lastbuf, kdb_machreg_fmt, lastaddr); - argv[1] = lastbuf; - argc = 1; - count = lastcount; + addr = lastaddr; + line_count = last_line_count; radix = lastradix; } else { kdb_machreg_t val; - if (argc >= 2) { + nextarg = 1; + diag = kdbgetaddrarg(argc, argv, &nextarg, &addr, &offset, NULL, regs); + if (diag) + return diag; + if (argc > nextarg+2) + return KDB_ARGCOUNT; - diag = kdbgetularg(argv[2], &val); + if (argc >= nextarg) { + diag = kdbgetularg(argv[nextarg], &val); if (!diag) - count = (int) val; - } else { - diag = kdbgetintenv("MDCOUNT", &count); + line_count = (int) val; } - - if (argc >= 3) { - diag = kdbgetularg(argv[3], &val); + if (argc >= nextarg+1) { + diag = kdbgetularg(argv[nextarg+1], &val); if (!diag) radix = (int) val; - } else { - diag = kdbgetintenv("RADIX",&radix); } } + if (strcmp(argv[0], "mdr") == 0) { + return(kdb_mdr(addr, line_count)); + } + switch (radix) { case 10: fmtchar = 'd'; @@ -1551,9 +1583,6 @@ return KDB_BADRADIX; } - kdbgetintenv("BYTESPERWORD", &width); - kdbgetintenv("NOSECT", &nosect); - if (strcmp(argv[0], "mds") == 0) { symbolic = 1; width = sizeof(kdb_machreg_t); @@ -1577,26 +1606,17 @@ } - nextarg = 1; - diag = kdbgetaddrarg(argc, argv, &nextarg, &addr, &offset, NULL, regs); - if (diag) - return diag; - - if (strcmp(argv[0], "mdr") == 0) { - return(kdb_mdr(addr, count)); - } - /* Round address down modulo BYTESPERWORD */ addr &= ~(width-1); /* - * Remember count and radix for next 'md' + * Remember line_count and radix for next 'md' */ - lastcount = count; + last_line_count = line_count; lastradix = radix; - while (count--) { + while (line_count--) { int num = (symbolic?1 :(16 / width)); char cbuf[32]; char *c = cbuf; @@ -1664,7 +1684,6 @@ } kdb_printf(" %s\n", cbuf); } - lastaddr = addr; return 0; @@ -1701,8 +1720,9 @@ unsigned long contents; unsigned long word; int nextarg; + int width; - if (argc != 2) { + if (argc < 2) { return KDB_ARGCOUNT; } @@ -1721,16 +1741,18 @@ if (nextarg != argc + 1) return KDB_ARGCOUNT; + width = argv[0][2] ? (argv[0][2] - '0') : (sizeof(kdb_machreg_t)); + /* * To prevent modification of invalid addresses, check first. */ - word = kdba_getword(addr, sizeof(word)); + word = kdba_getword(addr, width); if (KDB_STATE(SUPPRESS)) { KDB_STATE_CLEAR(SUPPRESS); return 0; } - diag = kdba_putword(addr, sizeof(contents), contents); + diag = kdba_putword(addr, width, contents); kdb_printf(kdb_machreg_fmt " = " kdb_machreg_fmt "\n", addr, contents);