From owner-lkcd@oss.sgi.com Thu Nov 4 02:42:11 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 02:42:02 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:38269 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 02:41:38 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id CAA03582 for ; Thu, 4 Nov 1999 02:47:17 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id CAA87204; Thu, 4 Nov 1999 02:44:55 -0800 (PST) Date: Thu, 4 Nov 1999 02:44:55 -0800 (PST) From: Matt Robinson To: lkcd@oss.sgi.com cc: yakker@sgi.com Subject: Version 1.0 of LKCD Available Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Please go to: http://oss.sgi.com/projects/lkcd/ for more information. Also be sure to review the FAQ if you have any questions. Thanks! --Matt From owner-lkcd@oss.sgi.com Thu Nov 4 06:59:52 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 06:59:33 -0800 Received: from biff.ibm.net.il ([192.115.72.164]:40836 "HELO biff.ibm.net.il") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 06:59:12 -0800 Received: from mucom.co.il (host13.mucom.co.il [192.115.216.45]) by biff.ibm.net.il (Postfix) with ESMTP id 6D2751075 for ; Thu, 4 Nov 1999 17:03:34 +0200 (IST) Message-ID: <3820F723.D805B79@mucom.co.il> Date: Thu, 04 Nov 1999 03:01:55 +0000 From: Marc SPARC X-Mailer: Mozilla 4.6 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: lkcd@oss.sgi.com Subject: lkcd and mainstream kernels. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Hello, I'm hoping to see lkcd incorporated in 2.2.x, is it going to happen? It will be great, as it's often qutie hard to debug a kernel panic w/o hading an actual dump by just looking at Oops output. Thank you for your great work guys, this feature will bring up Linux a couple more stages up, in terms of maturity, (IMHO). Marc Esipovich. -- root is only a few clicks away... From owner-lkcd@oss.sgi.com Thu Nov 4 09:42:42 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 09:42:33 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:11815 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 09:42:13 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA8912724 for ; Thu, 4 Nov 1999 12:45:37 -0500 (EST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id JAA99985; Thu, 4 Nov 1999 09:44:19 -0800 (PST) Date: Thu, 4 Nov 1999 09:44:19 -0800 (PST) From: Matt Robinson To: Marc SPARC cc: lkcd@oss.sgi.com Subject: Re: lkcd and mainstream kernels. In-Reply-To: <3820F723.D805B79@mucom.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Cool, thanks, Marc. I hope to get it incorporated as soon as we can. You should try it out, there's code on the FAQ page which can show you examples on how to crash your machine (if that's what you want to do). I'll be announcing to the lkml later today. Thanks again! --Matt On Thu, 4 Nov 1999, Marc SPARC wrote: |>Hello, |> |> I'm hoping to see lkcd incorporated in 2.2.x, is it going to happen? |> |> It will be great, as it's often qutie hard to debug a kernel panic w/o hading an actual dump |> |> by just looking at Oops output. |> |>Thank you for your great work guys, this feature will bring up Linux a couple more stages up, in |> |>terms of maturity, (IMHO). |> |> |> Marc Esipovich. |> |>-- |>root is only a few clicks away... |> |> |> From owner-lkcd@oss.sgi.com Thu Nov 4 14:07:04 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:06:55 -0800 Received: from mailext03.compaq.com ([207.18.199.41]:46805 "HELO mailext03.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 14:06:39 -0800 Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext03.compaq.com (Postfix) with ESMTP id E3AB3152195 for ; Thu, 4 Nov 1999 16:11:19 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id DA6D84FB15; Thu, 4 Nov 1999 16:11:09 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint12.im.hou.compaq.com (Postfix) with SMTP id 765474C901 for ; Thu, 4 Nov 1999 16:11:09 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04487; Thu, 4 Nov 1999 15:11:18 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA18638; Thu, 4 Nov 1999 15:11:18 -0700 Content-Length: 1794 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 15:11:52 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: lcrash build Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing OK, I've applied the patches and I'm rebuilding my kernel. How do I build the lcrash utility? A simple "make" in /usr/src/linux/cmd or in /usr/src/linux/cmd/lcrash fails to work. >pwd /usr/src/linux/cmd >make Makefile:12: /Rules.make: No such file or directory make: *** No rule to make target `/Rules.make'. Stop. >cd lcrash/ >make /bin/rm -f ./include/arch (cd include ; /bin/ln -sf arch- arch) for dir in scripts man lib arch/ cmds ; do \ ( cd $dir ; make TOPDIR= ARCH=; cd .. ); \ done make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/scripts' Makefile:23: /Rules.make: No such file or directory make[1]: *** No rule to make target `/Rules.make'. Stop. make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/scripts' make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/man' Makefile:17: /Rules.make: No such file or directory make[1]: *** No rule to make target `/Rules.make'. Stop. make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/man' make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/lib' Makefile:30: /Rules.make: No such file or directory make[1]: *** No rule to make target `/Rules.make'. Stop. make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/lib' make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/arch' make[1]: *** No targets. Stop. make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/arch' make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/cmds' Makefile:36: /Rules.make: No such file or directory make[1]: *** No rule to make target `/Rules.make'. Stop. make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/cmds' make: *** No rule to make target `include/arch/trace.h', needed by `main.o'. Stop. > -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 14:14:24 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:14:05 -0800 Received: from mailext03.compaq.com ([207.18.199.41]:42711 "HELO mailext03.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 14:13:51 -0800 Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext03.compaq.com (Postfix) with ESMTP id 20A44152027 for ; Thu, 4 Nov 1999 16:18:32 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id 198E84FB15; Thu, 4 Nov 1999 16:18:22 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint12.im.hou.compaq.com (Postfix) with SMTP id 961184C901 for ; Thu, 4 Nov 1999 16:18:21 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04118; Thu, 4 Nov 1999 15:18:30 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA02963; Thu, 4 Nov 1999 15:18:30 -0700 Content-Length: 376 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 15:19:04 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: make bzlilo doesn't build properly (nevermind) Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing OK, nevermind. Once I stopped trying to compile lcrash myself, and let the kernel built do it, everything built fine. A "make clean" for /usr/src/linux/cmd allowed "make bzlilo" to proceed. Perhaps this could have been made a little more clear in the FAQ; I sure got the impression I needed to build lcrash seperately. -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 14:18:35 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:18:25 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:23063 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 14:18:19 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id RAA8530768 for ; Thu, 4 Nov 1999 17:22:30 -0500 (EST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id OAA89266; Thu, 4 Nov 1999 14:21:13 -0800 (PST) Date: Thu, 4 Nov 1999 14:21:13 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: lcrash build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing It happens automatically when you build your kernel. If you want to build the 'lcrash' binary separately, you can just run "cd cmd/lcrash; make TOPDIR=/usr/src/linux ARCH=i386" or whatever your TOPDIR is. A simple "make" and "make install" from your top of trunk Linux tree should be sufficient to build and install both the kernel and the new 'lcrash' binary. Let me know if I can help with anything else. :) --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>OK, I've applied the patches and I'm rebuilding my kernel. How do I build the |>lcrash utility? A simple "make" in /usr/src/linux/cmd or in |>/usr/src/linux/cmd/lcrash fails to work. |> |>>pwd |>/usr/src/linux/cmd |>>make |>Makefile:12: /Rules.make: No such file or directory |>make: *** No rule to make target `/Rules.make'. Stop. |>>cd lcrash/ |>>make |>/bin/rm -f ./include/arch |>(cd include ; /bin/ln -sf arch- arch) |>for dir in scripts man lib arch/ cmds ; do \ |> ( cd $dir ; make TOPDIR= ARCH=; cd .. ); \ |>done |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/scripts' |>Makefile:23: /Rules.make: No such file or directory |>make[1]: *** No rule to make target `/Rules.make'. Stop. |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/scripts' |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/man' |>Makefile:17: /Rules.make: No such file or directory |>make[1]: *** No rule to make target `/Rules.make'. Stop. |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/man' |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/lib' |>Makefile:30: /Rules.make: No such file or directory |>make[1]: *** No rule to make target `/Rules.make'. Stop. |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/lib' |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/arch' |>make[1]: *** No targets. Stop. |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/arch' |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash/cmds' |>Makefile:36: /Rules.make: No such file or directory |>make[1]: *** No rule to make target `/Rules.make'. Stop. |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash/cmds' |>make: *** No rule to make target `include/arch/trace.h', needed by `main.o'. |>Stop. |>> |> |>-- |>Brian Hall |>Linux Consultant |> From owner-lkcd@oss.sgi.com Thu Nov 4 14:19:24 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:19:04 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:35351 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 14:18:50 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id RAA8923628 for ; Thu, 4 Nov 1999 17:23:02 -0500 (EST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id OAA00741; Thu, 4 Nov 1999 14:21:46 -0800 (PST) Date: Thu, 4 Nov 1999 14:21:46 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: make bzlilo doesn't build properly (nevermind) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I'll add it to the FAQ today. Thanks! --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>OK, nevermind. Once I stopped trying to compile lcrash myself, and let the |>kernel built do it, everything built fine. A "make clean" for |>/usr/src/linux/cmd allowed "make bzlilo" to proceed. Perhaps this could have |>been made a little more clear in the FAQ; I sure got the impression I needed to |>build lcrash seperately. |> |>-- |>Brian Hall |>Linux Consultant |> From owner-lkcd@oss.sgi.com Thu Nov 4 14:20:24 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:20:04 -0800 Received: from mailext02.compaq.com ([207.18.199.33]:12975 "HELO mailext02.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 14:19:57 -0800 Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext02.compaq.com (Postfix) with ESMTP id A64999A93D for ; Thu, 4 Nov 1999 16:24:34 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id A4B774FB15; Thu, 4 Nov 1999 16:24:24 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint12.im.hou.compaq.com (Postfix) with SMTP id 31F884C901 for ; Thu, 4 Nov 1999 16:24:24 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04705; Thu, 4 Nov 1999 15:24:33 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA29114; Thu, 4 Nov 1999 15:24:32 -0700 Content-Length: 440 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 15:25:06 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: "make modules" fails Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing make[1]: Entering directory `/usr/src/linux-2.2.13/cmd' make -C lcrash modules make[2]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash' make[2]: *** No rule to make target `modules'. Stop. make[2]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash' make[1]: *** [_modsubdir_lcrash] Error 2 make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd' make: *** [_mod_cmd] Error 2 -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 14:39:14 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:39:04 -0800 Received: from mail.intercomp-sys.com ([194.90.152.9]:48396 "EHLO mail.intercomp-sys.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 14:38:41 -0800 Received: from cobol2java.com ([213.8.4.126]) by mail.intercomp-sys.com (8.9.3/8.8.7) with ESMTP id XAA32582 for ; Thu, 4 Nov 1999 23:45:42 -0500 Message-ID: <38220C3D.8E2317DC@cobol2java.com> Date: Fri, 05 Nov 1999 00:44:13 +0200 From: Hetz Ben Hamo X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: lkcd@oss.sgi.com Subject: Small question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Hi, Did you contact Linus? Are those patches going into kernel 2.2.x or to 2.3.x or it is waiting for the new dev. kernel (2.5.x)? Also, do u provide help in the kernel configuration menu? (I see there are kernel patches) Thanks Hetz From owner-lkcd@oss.sgi.com Thu Nov 4 14:49:34 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 14:49:25 -0800 Received: from biff.ibm.net.il ([192.115.72.164]:54418 "HELO biff.ibm.net.il") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 14:49:08 -0800 Received: from host13.mucom.co.il (host13.mucom.co.il [192.115.216.45]) by biff.ibm.net.il (Postfix) with ESMTP id 5300D102F; Fri, 5 Nov 1999 00:53:45 +0200 (IST) Date: Thu, 4 Nov 1999 12:51:54 +0200 (IST) From: Marc Esipovich X-Sender: marc@moose.roadkill.com To: Hetz Ben Hamo Cc: lkcd@oss.sgi.com Subject: Re: Small question In-Reply-To: <38220C3D.8E2317DC@cobol2java.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing > Hi, > > Did you contact Linus? Are those patches going into kernel 2.2.x or to > 2.3.x or it is waiting for the new dev. kernel (2.5.x)? I sure hope so, I know I'd love to see them there. > > Also, do u provide help in the kernel configuration menu? (I see there > are kernel patches) Some help is provided, I'm sure it will be extended shortly ;) But all the help you might need is provided in the FAQ, the kernel configuration help is just a short description of the feature, not a full help/readme file. Marc Esipovich. -- root is only a few clicks away... From owner-lkcd@oss.sgi.com Thu Nov 4 15:06:25 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:06:15 -0800 Received: from mailext12.compaq.com ([207.18.199.188]:58602 "HELO mailext12.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 15:05:53 -0800 Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext12.compaq.com (Postfix) with ESMTP id 9069B578D9 for ; Thu, 4 Nov 1999 17:10:34 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id CEFF6BC4C7; Thu, 4 Nov 1999 17:10:22 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint02.im.hou.compaq.com (Postfix) with SMTP id 6FFC3B2A42 for ; Thu, 4 Nov 1999 17:10:22 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04573; Thu, 4 Nov 1999 16:10:33 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA08859; Thu, 4 Nov 1999 16:10:33 -0700 Content-Length: 1394 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 16:11:06 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: setpriority kernel mod test doesn't compile Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I modified sys_setpriority as shown in the FAQ, but the kernel compile fails: sys.c: In function `sys_setpriority': sys.c:92: parse error before `}' sys.c:78: warning: unused variable `error' sys.c:77: warning: unused variable `priority' sys.c:76: warning: unused variable `p' sys.c:93: warning: control reaches end of non-void function sys.c: At top level: sys.c:97: warning: type defaults to `int' in declaration of `error' sys.c:97: warning: data definition has no type or storage class sys.c:98: warning: type defaults to `int' in declaration of `priority' sys.c:98: `niceval' undeclared here (not in a function) sys.c:98: warning: data definition has no type or storage class sys.c:99: parse error before `if' sys.c:103: warning: type defaults to `int' in declaration of `priority' sys.c:103: redefinition of `priority' sys.c:98: `priority' previously defined here sys.c:103: initializer element is not constant sys.c:103: warning: data definition has no type or storage class sys.c:105: parse error before `if' sys.c:112: parse error before `=' make[2]: *** [sys.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.2.13/kernel' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/linux-2.2.13/kernel' make: *** [_dir_kernel] Error 2 Also, the panic call is pretty obvious, but what does the assembler do? -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 15:15:05 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:14:55 -0800 Received: from mailext04.compaq.com ([207.18.199.42]:13718 "HELO mailext04.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 15:14:39 -0800 Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id 7AB60104B87 for ; Thu, 4 Nov 1999 17:19:20 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id BDFBABC4C7; Thu, 4 Nov 1999 17:19:08 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint02.im.hou.compaq.com (Postfix) with SMTP id 58EFFB2A42 for ; Thu, 4 Nov 1999 17:19:08 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04600; Thu, 4 Nov 1999 16:19:19 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA23018; Thu, 4 Nov 1999 16:19:18 -0700 Content-Length: 274 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 16:19:52 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: Crossplatform kernel crash utilities? Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Are there plans to port lkcd to other platforms, such as PowerPC and Alpha? It would be nice to examine a crash from a different platform (for example, walk through a Linux Alpha crash dump on a Linux Intel machine). -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 15:27:55 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:27:45 -0800 Received: from biff.ibm.net.il ([192.115.72.164]:29331 "HELO biff.ibm.net.il") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 15:27:33 -0800 Received: from host13.mucom.co.il (host13.mucom.co.il [192.115.216.45]) by biff.ibm.net.il (Postfix) with ESMTP id 4D764102B; Fri, 5 Nov 1999 01:32:10 +0200 (IST) Date: Thu, 4 Nov 1999 13:30:20 +0200 (IST) From: Marc Esipovich X-Sender: marc@moose.roadkill.com To: Brian Hall Cc: lkcd@oss.sgi.com Subject: Re: Crossplatform kernel crash utilities? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Thu, 4 Nov 1999, Brian Hall wrote: > Are there plans to port lkcd to other platforms, such as PowerPC and Alpha? It > would be nice to examine a crash from a different platform (for example, walk > through a Linux Alpha crash dump on a Linux Intel machine). Examining crashdump data of other architecture on a different architecture than the origin of the crashdump data will require a big amount of code and adjustments, why bother? Crashdumps contain data which is highly platform/software dependent. For example, Solaris' crashdumps should be examined on the same architecture/solaris version where the crashdump came from, otherwise it's. Marc Esipovich. -- root is only a few clicks away... From owner-lkcd@oss.sgi.com Thu Nov 4 15:31:05 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:30:55 -0800 Received: from mailext12.compaq.com ([207.18.199.188]:16623 "HELO mailext12.compaq.com") by oss.sgi.com with SMTP id ; Thu, 4 Nov 1999 15:30:39 -0800 Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext12.compaq.com (Postfix) with ESMTP id 1B39C57820; Thu, 4 Nov 1999 17:35:20 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 5E0C7BC4C7; Thu, 4 Nov 1999 17:35:08 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint02.im.hou.compaq.com (Postfix) with SMTP id DC816B2A42; Thu, 4 Nov 1999 17:35:07 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA04863; Thu, 4 Nov 1999 16:35:18 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA31329; Thu, 4 Nov 1999 16:35:14 -0700 Content-Length: 1394 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 04 Nov 1999 16:35:48 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com, Marc Esipovich Subject: setpriority kernel mod test doesn't compile Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I modified sys_setpriority as shown in the FAQ, but the kernel compile fails: sys.c: In function `sys_setpriority': sys.c:92: parse error before `}' sys.c:78: warning: unused variable `error' sys.c:77: warning: unused variable `priority' sys.c:76: warning: unused variable `p' sys.c:93: warning: control reaches end of non-void function sys.c: At top level: sys.c:97: warning: type defaults to `int' in declaration of `error' sys.c:97: warning: data definition has no type or storage class sys.c:98: warning: type defaults to `int' in declaration of `priority' sys.c:98: `niceval' undeclared here (not in a function) sys.c:98: warning: data definition has no type or storage class sys.c:99: parse error before `if' sys.c:103: warning: type defaults to `int' in declaration of `priority' sys.c:103: redefinition of `priority' sys.c:98: `priority' previously defined here sys.c:103: initializer element is not constant sys.c:103: warning: data definition has no type or storage class sys.c:105: parse error before `if' sys.c:112: parse error before `=' make[2]: *** [sys.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.2.13/kernel' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/linux-2.2.13/kernel' make: *** [_dir_kernel] Error 2 Also, the panic call is pretty obvious, but what does the assembler do? -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 15:39:45 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:39:36 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:45886 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 15:39:25 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA05246 for ; Thu, 4 Nov 1999 15:45:07 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id PAA90852; Thu, 4 Nov 1999 15:42:49 -0800 (PST) Date: Thu, 4 Nov 1999 15:42:49 -0800 (PST) From: Matt Robinson To: Hetz Ben Hamo cc: lkcd@oss.sgi.com Subject: Re: Small question In-Reply-To: <38220C3D.8E2317DC@cobol2java.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Most of the help is contained on the web page. I'll probably release a 1.0.1 either tomorrow or on Monday that contains a better README (it needs to be updated), and fixes a couple of bugs I uncovered in the process of testing (and the one Brian found). I'll be sending the announcement out to the Linux Kernel Mailing List tonight, so we'll see what Linus thinks from there. --Matt On Fri, 5 Nov 1999, Hetz Ben Hamo wrote: |>Hi, |> |>Did you contact Linus? Are those patches going into kernel 2.2.x or to |>2.3.x or it is waiting for the new dev. kernel (2.5.x)? |> |>Also, do u provide help in the kernel configuration menu? (I see there |>are kernel patches) |> |>Thanks |>Hetz From owner-lkcd@oss.sgi.com Thu Nov 4 15:41:56 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:41:46 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:49728 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 15:41:37 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA01647 for ; Thu, 4 Nov 1999 15:47:19 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id PAA90333; Thu, 4 Nov 1999 15:45:01 -0800 (PST) Date: Thu, 4 Nov 1999 15:45:01 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: setpriority kernel mod test doesn't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing It's just a little hack to create an exception panic. You can accomplish the same thing with the call that Scott mentioned earlier: char *a = (char *)0x0; *a = 0; So just replace the __asm__ call with the stuff above. I'm surprised you weren't able to compile -- I've been copying that code in for a long time, and haven't had any problem whatsoever. --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>I modified sys_setpriority as shown in the FAQ, but the kernel compile fails: |> |>sys.c: In function `sys_setpriority': |>sys.c:92: parse error before `}' |>sys.c:78: warning: unused variable `error' |>sys.c:77: warning: unused variable `priority' |>sys.c:76: warning: unused variable `p' |>sys.c:93: warning: control reaches end of non-void function |>sys.c: At top level: |>sys.c:97: warning: type defaults to `int' in declaration of `error' |>sys.c:97: warning: data definition has no type or storage class |>sys.c:98: warning: type defaults to `int' in declaration of `priority' |>sys.c:98: `niceval' undeclared here (not in a function) |>sys.c:98: warning: data definition has no type or storage class |>sys.c:99: parse error before `if' |>sys.c:103: warning: type defaults to `int' in declaration of `priority' |>sys.c:103: redefinition of `priority' |>sys.c:98: `priority' previously defined here |>sys.c:103: initializer element is not constant |>sys.c:103: warning: data definition has no type or storage class |>sys.c:105: parse error before `if' |>sys.c:112: parse error before `=' |>make[2]: *** [sys.o] Error 1 |>make[2]: Leaving directory `/usr/src/linux-2.2.13/kernel' |>make[1]: *** [first_rule] Error 2 |>make[1]: Leaving directory `/usr/src/linux-2.2.13/kernel' |>make: *** [_dir_kernel] Error 2 |> |> |>Also, the panic call is pretty obvious, but what does the assembler do? |> |>-- |>Brian Hall |>Linux Consultant |> From owner-lkcd@oss.sgi.com Thu Nov 4 15:46:16 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:45:56 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:16951 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 15:45:47 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id SAA8925001 for ; Thu, 4 Nov 1999 18:50:21 -0500 (EST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id PAA89269; Thu, 4 Nov 1999 15:49:03 -0800 (PST) Date: Thu, 4 Nov 1999 15:49:03 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: Crossplatform kernel crash utilities? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Some of this has to be leveraged by the other companies and users working on the Linux product for different processors. Unfortunately, I don't have a PowerPC box, or an Alpha box, or even a Sparc box for that matter. The structure of the cmd/lcrash and arch//kernel/ code should be easy to leverage from one release to another. As for the 'lcrash' binary, you'll need to use the one that was built with the kernel. That's the whole reason for putting the 'lcrash' code into the kernel tree in the first place. Because symbol table data isn't available in the vmlinu{x,z}, there's no good way to understand what a "struct task" is, for example, from an Alpha to a PowerPC to a ... --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>Are there plans to port lkcd to other platforms, such as PowerPC and Alpha? It |>would be nice to examine a crash from a different platform (for example, walk |>through a Linux Alpha crash dump on a Linux Intel machine). From owner-lkcd@oss.sgi.com Thu Nov 4 15:59:46 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 15:59:36 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:18555 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 15:59:23 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA22301 for ; Thu, 4 Nov 1999 15:59:59 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id QAA95014; Thu, 4 Nov 1999 16:02:47 -0800 (PST) Date: Thu, 4 Nov 1999 16:02:47 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: make bzlilo doesn't build properly (nevermind) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I put the new information under the step 2.3: What are the steps for configuring LKCD vmdumps on my system? This should hopefully answer the question for most users. --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>OK, nevermind. Once I stopped trying to compile lcrash myself, and let the |>kernel built do it, everything built fine. A "make clean" for |>/usr/src/linux/cmd allowed "make bzlilo" to proceed. Perhaps this could have |>been made a little more clear in the FAQ; I sure got the impression I needed to |>build lcrash seperately. |> |>-- |>Brian Hall |>Linux Consultant From owner-lkcd@oss.sgi.com Thu Nov 4 17:19:06 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 17:18:56 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:63324 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 17:18:41 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id RAA01051 for ; Thu, 4 Nov 1999 17:24:23 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id RAA01511; Thu, 4 Nov 1999 17:22:04 -0800 (PST) Date: Thu, 4 Nov 1999 17:22:04 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: "make modules" fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Hmmm. I've fixed this (for modules and modules_install) and I've created a 1.0.1 directory at the download location. You can grab the latest version and try it out; it should eliminate this problem. Also, 'make bzlilo' and 'make lilo' now do a proper install of the 'lcrash' binary. They didn't before (I assumed people would do a 'make install' all the time ... a bad assumption). --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>make[1]: Entering directory `/usr/src/linux-2.2.13/cmd' |>make -C lcrash modules |>make[2]: Entering directory `/usr/src/linux-2.2.13/cmd/lcrash' |>make[2]: *** No rule to make target `modules'. Stop. |>make[2]: Leaving directory `/usr/src/linux-2.2.13/cmd/lcrash' |>make[1]: *** [_modsubdir_lcrash] Error 2 |>make[1]: Leaving directory `/usr/src/linux-2.2.13/cmd' |>make: *** [_mod_cmd] Error 2 From owner-lkcd@oss.sgi.com Thu Nov 4 17:19:56 1999 Received: by oss.sgi.com id ; Thu, 4 Nov 1999 17:19:46 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:3165 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 4 Nov 1999 17:19:37 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id RAA05747 for ; Thu, 4 Nov 1999 17:25:19 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id RAA01169; Thu, 4 Nov 1999 17:22:59 -0800 (PST) Date: Thu, 4 Nov 1999 17:22:59 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com, Marc Esipovich Subject: Re: setpriority kernel mod test doesn't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing FYI, I've updated the FAQ to use the more straightforward: char *a = 0x0; *a = 0; Instead of the __asm__() directive. That way it's universal from one architecture to another (in the future). --Matt On Thu, 4 Nov 1999, Brian Hall wrote: |>I modified sys_setpriority as shown in the FAQ, but the kernel compile fails: From owner-lkcd@oss.sgi.com Fri Nov 5 10:15:27 1999 Received: by oss.sgi.com id ; Fri, 5 Nov 1999 10:15:18 -0800 Received: from mailext04.compaq.com ([207.18.199.42]:43148 "HELO mailext04.compaq.com") by oss.sgi.com with SMTP id ; Fri, 5 Nov 1999 10:14:56 -0800 Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id A66D3104C1E for ; Fri, 5 Nov 1999 12:19:40 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 5801CBC4D0; Fri, 5 Nov 1999 12:19:27 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint02.im.hou.compaq.com (Postfix) with SMTP id DACDEB2A45 for ; Fri, 5 Nov 1999 12:19:26 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA08265; Fri, 5 Nov 1999 11:19:39 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA30416; Fri, 5 Nov 1999 11:19:38 -0700 Content-Length: 3140 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Fri, 05 Nov 1999 11:20:03 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: modifications to sys.c still fail to compile Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Maybe I'm missing something obvious, but even the simpler test mod to sys.c as in the FAQ fails on make bzlilo: gcc -D__KERNEL__ -I/usr/src/linux-2.2.13/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -c -o sys.o sys.c sys.c: In function `sys_setpriority': sys.c:86: warning: control reaches end of non-void function sys.c: At top level: sys.c:94: warning: type defaults to `int' in declaration of `error' sys.c:94: warning: data definition has no type or storage class sys.c:95: warning: type defaults to `int' in declaration of `priority' sys.c:95: conflicting types for `priority' sys.c:90: previous declaration of `priority' sys.c:95: `niceval' undeclared here (not in a function) sys.c:95: warning: data definition has no type or storage class sys.c:96: parse error before `if' sys.c:100: warning: type defaults to `int' in declaration of `priority' sys.c:100: redefinition of `priority' sys.c:95: `priority' previously defined here sys.c:100: initializer element is not constant sys.c:100: warning: data definition has no type or storage class sys.c:102: parse error before `if' sys.c:109: parse error before `=' make[2]: *** [sys.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.2.13/kernel' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/linux-2.2.13/kernel' make: *** [_dir_kernel] Error 2 The function in sys.c looks like this: asmlinkage int sys_setpriority(int which, int who, int niceval) { struct task_struct *p; unsigned int priority; int error; #if 0 if (which > 2 || which < 0) return -EINVAL; #else if (which == -1) { panic("User created crash dump"); } else if (which == -2) { char *a = 0x0; *a = 0; }; } #endif /* normalize: avoid signed division (rounding problems) */ error = ESRCH; priority = niceval; if (niceval < 0) priority = -niceval; if (priority > 20) priority = 20; priority = (priority * DEF_PRIORITY + 10) / 20 + DEF_PRIORITY; if (niceval >= 0) { priority = 2*DEF_PRIORITY - priority; if (!priority) priority = 1; } read_lock(&tasklist_lock); for_each_task(p) { if (!proc_sel(p, which, who)) continue; if (p->uid != current->euid && p->uid != current->uid && !capable(CAP_SYS_NICE)) { error = EPERM; continue; } if (error == ESRCH) error = 0; if (priority > p->priority && !capable(CAP_SYS_NICE)) error = EACCES; else p->priority = priority; } read_unlock(&tasklist_lock); return -error; } -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Fri Nov 5 10:18:37 1999 Received: by oss.sgi.com id ; Fri, 5 Nov 1999 10:18:27 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:61959 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Fri, 5 Nov 1999 10:18:20 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA9560538 for ; Fri, 5 Nov 1999 10:22:50 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id KAA89994; Fri, 5 Nov 1999 10:21:31 -0800 (PST) Date: Fri, 5 Nov 1999 10:21:31 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com Subject: Re: modifications to sys.c still fail to compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Are your #if 0 and #endif's all correct? Can you send me a copy of your sys.c? --Matt On Fri, 5 Nov 1999, Brian Hall wrote: |>Maybe I'm missing something obvious, but even the simpler test mod to sys.c as |>in the FAQ fails on make bzlilo: |> |>gcc -D__KERNEL__ -I/usr/src/linux-2.2.13/include -Wall -Wstrict-prototypes -O2 |>-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 |>-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -c -o sys.o |>sys.c |>sys.c: In function `sys_setpriority': |>sys.c:86: warning: control reaches end of non-void function |>sys.c: At top level: |>sys.c:94: warning: type defaults to `int' in declaration of `error' |>sys.c:94: warning: data definition has no type or storage class |>sys.c:95: warning: type defaults to `int' in declaration of `priority' |>sys.c:95: conflicting types for `priority' |>sys.c:90: previous declaration of `priority' |>sys.c:95: `niceval' undeclared here (not in a function) |>sys.c:95: warning: data definition has no type or storage class |>sys.c:96: parse error before `if' |>sys.c:100: warning: type defaults to `int' in declaration of `priority' |>sys.c:100: redefinition of `priority' |>sys.c:95: `priority' previously defined here |>sys.c:100: initializer element is not constant |>sys.c:100: warning: data definition has no type or storage class |>sys.c:102: parse error before `if' |>sys.c:109: parse error before `=' |>make[2]: *** [sys.o] Error 1 |>make[2]: Leaving directory `/usr/src/linux-2.2.13/kernel' |>make[1]: *** [first_rule] Error 2 |>make[1]: Leaving directory `/usr/src/linux-2.2.13/kernel' |>make: *** [_dir_kernel] Error 2 |> |>The function in sys.c looks like this: |> |>asmlinkage int sys_setpriority(int which, int who, int niceval) |>{ |> struct task_struct *p; |> unsigned int priority; |> int error; |> |>#if 0 |> if (which > 2 || which < 0) |> return -EINVAL; |>#else |> if (which == -1) { |> panic("User created crash dump"); |> } else if (which == -2) { |> char *a = 0x0; |> *a = 0; |> }; |> } |>#endif |> |> /* normalize: avoid signed division (rounding problems) */ |> error = ESRCH; |> priority = niceval; |> if (niceval < 0) |> priority = -niceval; |> if (priority > 20) |> priority = 20; |> priority = (priority * DEF_PRIORITY + 10) / 20 + DEF_PRIORITY; |> |> if (niceval >= 0) { |> priority = 2*DEF_PRIORITY - priority; |> if (!priority) |> priority = 1; |> } |> |> read_lock(&tasklist_lock); |> for_each_task(p) { |> if (!proc_sel(p, which, who)) |> continue; |> if (p->uid != current->euid && |> p->uid != current->uid && !capable(CAP_SYS_NICE)) { |> error = EPERM; |> continue; |> } |> if (error == ESRCH) |> error = 0; |> if (priority > p->priority && !capable(CAP_SYS_NICE)) |> error = EACCES; |> else |> p->priority = priority; |> } |> read_unlock(&tasklist_lock); |> |> return -error; |>} |> |>-- |>Brian Hall |>Linux Consultant |> From owner-lkcd@oss.sgi.com Fri Nov 5 13:02:39 1999 Received: by oss.sgi.com id ; Fri, 5 Nov 1999 13:02:30 -0800 Received: from mailhub.scl.ameslab.gov ([147.155.137.127]:7699 "EHLO mailhub.scl.ameslab.gov") by oss.sgi.com with ESMTP id ; Fri, 5 Nov 1999 13:02:07 -0800 Received: from phantasm.scl.ameslab.gov ([147.155.137.74] helo=scl.ameslab.gov) by mailhub.scl.ameslab.gov with esmtp (Exim 3.02 #1) id 11jqZQ-000KBa-00; Fri, 05 Nov 1999 15:06:52 -0600 Message-ID: <382346E6.551AC903@scl.ameslab.gov> Date: Fri, 05 Nov 1999 15:06:46 -0600 From: Troy Benjegerdes X-Mailer: Mozilla 4.6 [en] (X11; I; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: lkcd@oss.sgi.com Subject: PPC support? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I just saw the announcement on slashdot, forgive me if this has been asked already. Does this patch support PPC machines, and if not, what will I need to write/change to make it do so? Thanks. -- Troy Benjegerdes troybenj@scl.ameslab.gov Scalable Computing Lab hozer@drgw.net From owner-lkcd@oss.sgi.com Fri Nov 5 13:13:29 1999 Received: by oss.sgi.com id ; Fri, 5 Nov 1999 13:13:20 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:52589 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Fri, 5 Nov 1999 13:13:14 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA04022 for ; Fri, 5 Nov 1999 13:18:57 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id NAA04867; Fri, 5 Nov 1999 13:16:37 -0800 (PST) Date: Fri, 5 Nov 1999 13:16:37 -0800 (PST) From: Matt Robinson To: Troy Benjegerdes cc: lkcd@oss.sgi.com Subject: Re: PPC support? In-Reply-To: <382346E6.551AC903@scl.ameslab.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing There'd be a bit of work to do: 1) The arch/ppc/kernel code needs to be finished. This is pretty straightforward, as most of the current stuff for i386 should translate over well. This also requires putting in the hooks for dump_execute() into the PPC exception code. For i386, we added a hook in die(). Note that the header files, etc., might also have to change. 2) The arch specific code of cmd/lcrash needs to be done. This is a lot of work. The disassembler needs to be completed, and stack trace code needs to be changed to handle the way in which the register set saves things such as return addresses, program counters, stack pointers, etc. If you need tips on what to do, let me know. I'd say you should examine the i386 architecture specific stuff both in the kernel and in the lcrash directory for how we did it. I can answer whatever questions you have and try to point you in the right direction if you want to do the work. Right now, we're trying to work on future processor ports. :) --Matt On Fri, 5 Nov 1999, Troy Benjegerdes wrote: |>I just saw the announcement on slashdot, forgive me if this has been |>asked already. |> |>Does this patch support PPC machines, and if not, what will I need to |>write/change to make it do so? |> |>Thanks. |> |>-- |>Troy Benjegerdes troybenj@scl.ameslab.gov |>Scalable Computing Lab hozer@drgw.net From owner-lkcd@oss.sgi.com Fri Nov 5 15:55:20 1999 Received: by oss.sgi.com id ; Fri, 5 Nov 1999 15:55:10 -0800 Received: from hqinbh1-e1.ms.com ([205.228.12.65]:51851 "EHLO hqinbh1.ms.com") by oss.sgi.com with ESMTP id ; Fri, 5 Nov 1999 15:54:51 -0800 Received: (from uucp@localhost) by hqinbh1.ms.com (8.8.6/fw v1.30) id SAA11835 for ; Fri, 5 Nov 1999 18:59:31 -0500 (EST) Received: from unknown(144.14.193.5) by hqinbh1 via smap (4.1) id xma011803; Fri, 5 Nov 99 18:59:30 -0500 Received: from bigboy (bigboy.morgan.com [144.14.36.197]) by sasmh4.ms.com (8.8.5/imap+ldap v2.4) with SMTP id SAA14092 for ; Fri, 5 Nov 1999 18:59:30 -0500 (EST) Date: Fri, 5 Nov 1999 18:59:30 -0500 (EST) From: Mike Sklar X-Sender: sklarm@bigboy To: lkcd@oss.sgi.com Subject: thanks (I mean it) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I work at a large SGI shop, with a good deal of linux desktops. Just wanted to thanks from all us syad's that are tired of having mystery hangs and panics on our linux boxes. From owner-lkcd@oss.sgi.com Mon Nov 8 10:52:39 1999 Received: by oss.sgi.com id ; Mon, 8 Nov 1999 10:52:29 -0800 Received: from ad.splitinfinity.net ([216.188.68.16]:25106 "EHLO smtp.adultstorage.com") by oss.sgi.com with ESMTP id ; Mon, 8 Nov 1999 10:52:13 -0800 Received: from nuclei by smtp.adultstorage.com with local (Exim 3.01 #1) id 11ku05-0001D8-00 for lkcd@oss.sgi.com; Mon, 08 Nov 1999 10:58:45 -0800 From: info@cgiscan.com To: lkcd@oss.sgi.com Subject: CGI Developers and Users Message-Id: Date: Mon, 08 Nov 1999 10:58:45 -0800 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Good day, I am writing to several people listed on various CGI resource sites to let you know there is a hot new resource to list your programs and get more traffic, sales, etc. The URL is http://cgiscan.com Please feel free to list any CGI scripts or resources pertaining to CGI development or training as well. Anyone interested in inexpensive, targetted advertising space can check out our rates at the website. Thanks Guys & Gals. From owner-lkcd@oss.sgi.com Mon Nov 8 16:49:50 1999 Received: by oss.sgi.com id ; Mon, 8 Nov 1999 16:49:40 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:22075 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Mon, 8 Nov 1999 16:49:34 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id QAA08032 for ; Mon, 8 Nov 1999 16:55:40 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id QAA05303 for ; Mon, 8 Nov 1999 16:53:18 -0800 (PST) Date: Mon, 8 Nov 1999 16:53:18 -0800 (PST) From: Matt Robinson To: lkcd@oss.sgi.com Subject: Test -- please ignore Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Testing archiving lists ... --Matt From owner-lkcd@oss.sgi.com Mon Nov 8 17:50:52 1999 Received: by oss.sgi.com id ; Mon, 8 Nov 1999 17:50:42 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:39181 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Mon, 8 Nov 1999 17:50:23 -0800 Received: (qmail 16333 invoked by uid 502); 9 Nov 1999 01:55:17 -0000 Message-ID: <19991109015517.16332.qmail@mail.ocs.com.au> Received: (qmail 16326 invoked from network); 9 Nov 1999 01:55:16 -0000 Received: from ocs4.ocs-net (192.168.255.4) by mail.ocs.com.au with SMTP; 9 Nov 1999 01:55:16 -0000 X-Mailer: exmh version 2.0.2 From: Keith Owens To: lkcd@oss.sgi.com Subject: Porting to kernel 2.3.x Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Nov 1999 12:55:15 +1100 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I started porting lkcd to 2.3.26 and hit a problem in sd.c. The patch refers to iobufp->pagelist which does not exist in 2.3.26. Before I spend too much time on this, has anybody already ported to 2.3? Or can you suggest the required changes? From owner-lkcd@oss.sgi.com Tue Nov 9 00:17:02 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 00:16:52 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:21777 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 00:16:36 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id AAA14891 for ; Tue, 9 Nov 1999 00:21:36 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id AAA04635; Tue, 9 Nov 1999 00:20:18 -0800 (PST) Date: Tue, 9 Nov 1999 00:20:18 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: Keith Owens cc: lkcd@oss.sgi.com Subject: Re: Porting to kernel 2.3.x In-Reply-To: <19991109015517.16332.qmail@mail.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I haven't ported it yet, so I'm not sure what happened to page lists. They were supposed to be kept around to have representations of each page (and associated mapping). The big key is making sure that Stephen and Scott's respective raw I/O patches make the appropriate translation into the 2.3.X tree. If you need help with that, let me know. I'll try to put a public list of the features we'd like to work on (or see if others are interested in working on). There's lots of cool stuff to do. --Matt On Tue, 9 Nov 1999, Keith Owens wrote: |>I started porting lkcd to 2.3.26 and hit a problem in sd.c. The patch |>refers to iobufp->pagelist which does not exist in 2.3.26. Before I |>spend too much time on this, has anybody already ported to 2.3? Or can |>you suggest the required changes? From owner-lkcd@oss.sgi.com Tue Nov 9 05:01:41 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 05:01:31 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:21776 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Tue, 9 Nov 1999 05:01:13 -0800 Received: (qmail 20066 invoked by uid 502); 9 Nov 1999 13:06:10 -0000 Message-ID: <19991109130609.20065.qmail@mail.ocs.com.au> Received: (qmail 20058 invoked from network); 9 Nov 1999 13:06:07 -0000 Received: from ocs4.ocs-net (192.168.255.4) by mail.ocs.com.au with SMTP; 9 Nov 1999 13:06:07 -0000 X-Mailer: exmh version 2.0.2 From: Keith Owens To: lkcd@oss.sgi.com Subject: Minor bug in 1.0.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Nov 1999 00:06:06 +1100 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Missing { } in sd.c, SCSI blkdev was not being unregistered correctly. Index: 13.2/drivers/scsi/sd.c --- 13.2/drivers/scsi/sd.c Fri, 05 Nov 1999 23:27:35 +1100 keith (linux-2.2/d/b/42_sd.c 1.2.1.5 644) +++ 13.2(w)/drivers/scsi/sd.c Wed, 10 Nov 1999 00:03:41 +1100 keith (linux-2.2/d/b/42_sd.c 1.2.1.5 644) @@ -2571,11 +2571,12 @@ scsi_unregister_module(MODULE_SCSI_DEV, &sd_template); - for (i=0; i <= (sd_template.dev_max - 1) / SCSI_DISKS_PER_MAJOR; i++) + for (i=0; i <= (sd_template.dev_max - 1) / SCSI_DISKS_PER_MAJOR; i++) { #if defined(CONFIG_RAW) unregister_chrdev(SD_MAJOR(i),"sd"), #endif unregister_blkdev(SD_MAJOR(i),"sd"); + } sd_registered--; if( rscsi_disks != NULL ) From owner-lkcd@oss.sgi.com Tue Nov 9 07:10:02 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 07:09:52 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:64890 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 07:09:37 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA92394 for ; Tue, 9 Nov 1999 07:14:31 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id HAA11967; Tue, 9 Nov 1999 07:13:11 -0800 (PST) Date: Tue, 9 Nov 1999 07:13:10 -0800 (PST) From: Matt Robinson To: Keith Owens cc: lkcd@oss.sgi.com Subject: Re: Minor bug in 1.0.2 In-Reply-To: <19991109130609.20065.qmail@mail.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing I've forwarded this on to Scott. I could fix it in my patch, but my suspicion is it should be corrected in his patch. --Matt On Wed, 10 Nov 1999, Keith Owens wrote: |>Missing { } in sd.c, SCSI blkdev was not being unregistered correctly. |> |>Index: 13.2/drivers/scsi/sd.c |>--- 13.2/drivers/scsi/sd.c Fri, 05 Nov 1999 23:27:35 +1100 keith (linux-2.2/d/b/42_sd.c 1.2.1.5 644) |>+++ 13.2(w)/drivers/scsi/sd.c Wed, 10 Nov 1999 00:03:41 +1100 keith (linux-2.2/d/b/42_sd.c 1.2.1.5 644) |>@@ -2571,11 +2571,12 @@ |> |> scsi_unregister_module(MODULE_SCSI_DEV, &sd_template); |> |>- for (i=0; i <= (sd_template.dev_max - 1) / SCSI_DISKS_PER_MAJOR; i++) |>+ for (i=0; i <= (sd_template.dev_max - 1) / SCSI_DISKS_PER_MAJOR; i++) { |> #if defined(CONFIG_RAW) |> unregister_chrdev(SD_MAJOR(i),"sd"), |> #endif |> unregister_blkdev(SD_MAJOR(i),"sd"); |>+ } |> |> sd_registered--; |> if( rscsi_disks != NULL ) |> From owner-lkcd@oss.sgi.com Tue Nov 9 09:05:12 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 09:05:03 -0800 Received: from mailext03.compaq.com ([207.18.199.41]:54234 "HELO mailext03.compaq.com") by oss.sgi.com with SMTP id ; Tue, 9 Nov 1999 09:04:41 -0800 Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext03.compaq.com (Postfix) with ESMTP id D32171520E3 for ; Tue, 9 Nov 1999 11:09:44 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id CBC784FB06; Tue, 9 Nov 1999 11:09:26 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint12.im.hou.compaq.com (Postfix) with SMTP id 605BA4C905 for ; Tue, 9 Nov 1999 11:09:26 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA20730; Tue, 9 Nov 1999 10:09:43 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA31120; Tue, 9 Nov 1999 10:09:43 -0700 Content-Length: 630 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Tue, 09 Nov 1999 11:11:19 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: lkcd@oss.sgi.com Subject: testing lkcd Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing OK, I have tested lkcd as described in the FAQ and it works well, so now I have some questions. Will the crash dump work if the interrupt handler dies? I have a script that will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to do that with 2.2.13. Can someone tell me how to cause this? I'd like to test this case. What is the purpose of the lcrash.# executables in /var/log/vmdump? How do you use lcrash to debug a crash dump ? I see how to invoke it against the dump files, but I could use some documentation about the internal lcrash commands. -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Tue Nov 9 09:52:12 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 09:52:02 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:2375 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 09:51:39 -0800 Received: from loco.csd.sgi.com (loco.csd.sgi.com [150.166.1.62]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA14785 for ; Tue, 9 Nov 1999 09:52:38 -0800 (PST) mail_from (tjm@sgi.com) Received: from sgi.com (localhost.csd.sgi.com [127.0.0.1]) by loco.csd.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id JAA66728; Tue, 9 Nov 1999 09:56:38 -0800 (PST) Message-ID: <38286055.1CBFB5EF@sgi.com> Date: Tue, 09 Nov 1999 09:56:37 -0800 From: Tom Morano X-Mailer: Mozilla 4.61C-SGI [en] (X11; I; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: Brian Hall CC: lkcd@oss.sgi.com Subject: Re: testing lkcd References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Brian Hall wrote: > > OK, I have tested lkcd as described in the FAQ and it works well, so now I have > some questions. > > Will the crash dump work if the interrupt handler dies? I have a script that > will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to do > that with 2.2.13. Can someone tell me how to cause this? I'd like to test this > case. > > What is the purpose of the lcrash.# executables in /var/log/vmdump? The lcrash utility includes kernel header files and directly references kernel data structures (within the lcrash address space). In addition to that, certain kernel build options (__SMP__ for example) may change the makeup of some kernel structures (e.g. task_struct). Because of this, it is important that you have the lcrash binary that matches the kernel you are trying to analyze. Otherwise you may find that the definition of a struct in lcrash does not map to what is in kernel memory. The numbered lcrash executables in /var/log/vmdump should be used with their respective dump and map files. > > How do you use lcrash to debug a crash dump ? I see how to invoke it against > the dump files, but I could use some documentation about the internal lcrash > commands. Some information is contained in the FAQ in our website http://oss.sgi.com/projects/lkcd/faq.html You should always start out with the report command. It will provide you with a top-level view of how the kernel died. For example: >> report ======================= LCRASH CORE FILE REPORT ======================= GENERATED ON: Tue Nov 9 09:42:54 1999 TIME OF CRASH: Mon Sep 13 17:39:36 1999 PANIC STRING: Oops MAP: map.20 VMDUMP: vmdump.20 ================ COREFILE SUMMARY ================ The system died due to a software failure. =================== UTSNAME INFORMATION =================== sysname : Linux nodename : peak-pc.engr.sgi.com release : 2.2.10 version : #218 Mon Sep 13 17:22:25 PDT 1999 machine : i686 domainname : engr.sgi.com =============== LOG BUFFER DUMP =============== <4>Linux version 2.2.10 (root@peak-pc.engr.sgi.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #218 Mon Sep 13 17:22:25 PDT 1999 <4>Detected 348932846 Hz processor. <4>Console: colour VGA+ 80x25 <4>Calibrating delay loop... 348.16 BogoMIPS <4>Memory: 95284k/98304k available (1056k kernel code, 408k reserved, 1500k data, 56k init) <4>CPU: Intel Pentium II (Deschutes) stepping 02 <6>Checking 386/387 coupling... OK, FPU using exception 16 error reporting. <6>Checking 'hlt' instruction... OK. <4>POSIX conformance testing by UNIFIX <4>PCI: PCI BIOS revision 2.10 entry at 0xfcaee <4>PCI: Using configuration type 1 <4>PCI: Probing PCI hardware <6>Linux NET4.0 for Linux 2.2 <6>Based upon Swansea University Computer Society NET3.039 <6>NET4: Unix domain sockets 1.0 for Linux NET4.0. <6>NET4: Linux TCP/IP 1.0 for NET4.0 <6>IP Protocols: ICMP, UDP, TCP <4>Starting kswapd v 1.5 <6>Detected PS/2 Mouse Port. <6>Serial driver version 4.27 with no serial options enabled <6>ttyS00 at 0x03f8 (irq = 4) is a 16550A <6>ttyS01 at 0x02f8 (irq = 3) is a 16550A <4>pty: 256 Unix98 ptys configured <4>PIIX4: IDE controller on PCI bus 00 dev 39 <4>PIIX4: not 100% native mode: will probe irqs later <4> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio <4>hda: WDC AC24300L, ATA DISK drive <4>hdc: NEC CD-ROM DRIVE:28C, ATAPI CDROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: WDC AC24300L, 4112MB w/256kB Cache, CHS=524/255/63, UDMA <4>hdc: ATAPI 32X CD-ROM drive, 128kB Cache <6>Uniform CDROM driver Revision: 2.55 <6>Floppy drive(s): fd0 is 1.44M <6>FDC 0 is a National Semiconductor PC87306 <6>(scsi0) found at PCI 14/0 <6>(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs <6>(scsi0) Warning - detected auto-termination <6>(scsi0) Please verify driver detected settings are correct. <6>(scsi0) If not, then please properly set the device termination <6>(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted <6>(scsi0) during machine bootup. <6>(scsi0) Cables present (Int-50 YES, Ext-50 NO) <6>(scsi0) Downloading sequencer code... 413 instructions downloaded <4>scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.17/3.2.4 <4> <4>scsi : 1 host. <6>(scsi0:0:6:0) Synchronous at 20.0 Mbyte/sec, offset 15. <4> Vendor: IBM Model: DDRS-34560 Rev: S97B <4> Type: Direct-Access ANSI SCSI revision: 02 <4>Detected scsi disk sda at scsi0, channel 0, id 6, lun 0 <4>scsi : detected 1 SCSI disk total. <4>SCSI device sda: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB] <6>3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html <6>eth0: 3Com 3c905B Cyclone 100baseTx at 0xdc00, 00:c0:4f:90:6e:54, IRQ 11 <6> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. <6> MII transceiver found at address 24, status 786d. <6> MII transceiver found at address 0, status 786d. <6> Enabling bus-master transmits and whole-frame receives. <4>Partition check: <4> sda: sda1 sda2 sda3 <4> hda: hda1 hda2 < hda5 hda6 > <4>VFS: Mounted root (ext2 filesystem) readonly. <4>Freeing unused kernel memory: 56k freed <6>dump_open(): dump device opened: 0x803 [sd(8,3)] <4>nfs warning: mount version older than kernel <1>Unable to handle kernel NULL pointer dereference at virtual address 00000008 <1>current->tss.cr3 = 00484000, %cr3 = 00484000 <1>*pde = 00000000 <4>PANIC: Oops (0002) - software fault <4>Registers: <4>CPU: 0 <4>EIP: 0010:[] <4>EFLAGS: 00010246 <4>eax: c0487fa4 ebx: c0486000 ecx: 00000000 edx: 00000018 <4>esi: bffffd64 edi: 00000001 ebp: fffffffe esp: c0487fac <4>ds: 0018 es: 0018 ss: 0018 <4>Process crashdump2 (pid: 879, process nr: 54, stackpage=c0487000) <4>Stack: c0486000 bffffd64 00000001 bffffd18 c0487fc4 c01079bc fffffffe 00000000 <4> 00000002 bffffd64 00000001 bffffd18 00000061 0000002b 0000002b 00000061 <4> 400c2254 00000023 00000202 bffffd04 0000002b <4>Call Trace: [] <4>Code: 29 05 08 00 00 00 8b 18 89 dd 5b 58 bf 03 00 00 00 89 c6 85 <4>Dumping to device 0x803 [sd(8,3)] ... <4>Writing dump header ... <4>Writing dump pages ... ==================== CURRENT SYSTEM TASKS ==================== ADDR UID PID PPID STATE PRI FLAGS MM NAME ============================================================================== c0252000 0 0 0 0 0 0 c023aa20 swapper c009c000 0 1 0 1 20 100 c025b060 init c039c000 0 2 1 1 20 40 c023aa20 kflushd c039a000 0 3 1 1 20 840 c023aa20 kpiod c0398000 0 4 1 1 20 840 c023aa20 kswapd c5dc4000 1 262 1 1 20 140 c025b2e0 portmap c5d46000 0 277 1 1 20 140 c025b360 ypbind c5dfa000 0 284 277 1 20 140 c025b460 ypbind c5db8000 0 338 1 1 20 140 c025b260 syslogd c5db4000 0 349 1 1 20 140 c025b3e0 klogd c501a000 0 363 1 1 20 40 c025b4e0 atd c512c000 0 377 1 1 20 40 c025b560 crond c514c000 0 395 1 1 20 140 c025b5e0 inetd c515a000 0 409 1 1 20 140 c025b660 snmpd c5232000 0 423 1 1 20 40 c025b6e0 named c520a000 0 437 1 1 20 140 c025b760 routed c53ca000 0 451 1 1 20 140 c025b7e0 xntpd c555e000 0 465 1 1 20 140 c025b860 lpd c535e000 0 483 1 1 20 140 c025b8e0 rpc.statd c5684000 0 494 1 1 20 40 c025b960 rpc.rquotad c562c000 0 505 1 1 20 40 c025b9e0 rpc.mountd c56c4000 0 529 1 1 20 140 c025bae0 rpc.rstatd c56bc000 0 543 1 1 20 140 c025ba60 rpc.rusersd c568c000 99 557 1 1 20 40 c025bb60 rpc.rwalld c5616000 0 571 1 1 20 140 c025bbe0 rwhod c5ee8000 0 591 1 1 20 140 c025b1e0 rpc.yppasswdd c55f2000 0 603 1 1 20 140 c025bce0 amd c5700000 0 605 1 1 20 40 c023aa20 rpciod c5714000 0 606 1 1 20 40 c023aa20 lockd c583c000 0 631 1 1 20 140 c58500c0 automount c570a000 0 644 395 1 20 100 c025bde0 in.rlogind c5790000 0 658 644 1 20 100 c025bd60 login c56d8000 0 659 658 1 20 100 c025bee0 tcsh c56dc000 0 681 1 1 20 140 c025bf60 sendmail c5a40000 0 701 1 1 20 140 c5850040 gpm c571c000 0 715 1 1 20 140 c5850140 httpd c56ea000 99 718 715 1 20 140 c025be60 httpd c5ae2000 99 719 715 1 20 140 c58501c0 httpd c59a4000 99 720 715 1 20 140 c5850240 httpd c5b6c000 99 721 715 1 20 140 c58502c0 httpd c5d48000 99 722 715 1 20 140 c5850340 httpd c5d0a000 99 723 715 1 20 140 c58503c0 httpd c5cc8000 99 724 715 1 20 140 c5850440 httpd c5c14000 99 725 715 1 20 140 c58504c0 httpd c5bcc000 99 726 715 1 20 140 c5850540 httpd c5ab0000 99 727 715 1 20 140 c58505c0 httpd c5d96000 100 745 1 1 20 40 c5850740 xfs c5446000 0 760 1 1 20 140 c5850640 smbd c05cc000 0 771 1 1 20 140 c58506c0 nmbd c0a3c000 9 825 1 1 20 40 c5850b40 innd c5f48000 9 831 1 1 20 40 c58507c0 actived c5ce2000 0 869 1 1 20 100 c025bc60 mingetty c08f0000 0 870 1 1 20 100 c025b160 mingetty c0504000 0 871 1 1 20 100 c5850a40 mingetty c04b0000 0 872 1 1 20 100 c5850840 mingetty c0836000 0 873 1 1 20 100 c5850bc0 mingetty c0940000 0 874 1 1 20 100 c58508c0 mingetty c0956000 0 875 1 1 20 100 c58509c0 getty c0b8c000 0 877 1 1 20 140 c5850c40 update c0486000 0 879 659 0 20 0 c025b0e0 crashdump2 =========================== STACK TRACE OF FAILING TASK =========================== ================================================================ STACK TRACE FOR TASK: 0xc0486000 (crashdump2) 0 sys_setpriority+41 [0xc01122a1] 1 system_call+45 [0xc01079b5] ================================================================ Plus, there is online help for each command via the help command. You can issue the help command without any arguments (or '?') to see a list of available lcrash commands (note that some of the displayed commands are aliases). >> help ? history p stab addtypes i386dis page stat bt id po strace deftask idis ps sym dis md ptype symbol dt mktrace px t dump mmap q task findsym mt q! trace fsym namelist quit vtop h nmlist report whatis help od sizeof You can then issue the help command followed by a command name to see some information about how the command should be used. Here are some examples... >> help task COMMAND: task [-f] [-n] [-w outfile] [task list] Display relevant information for each entry in task_list. If no entries are specified, display information for all active tasks. Entries in task_list can take the form of a virtual address or a PID (following a '#'). >> task ADDR UID PID PPID STATE PRI FLAGS MM NAME ============================================================================== c0252000 0 0 0 0 0 0 c023aa20 swapper c009c000 0 1 0 1 20 100 c025b060 init c039c000 0 2 1 1 20 40 c023aa20 kflushd c039a000 0 3 1 1 20 840 c023aa20 kpiod . . . c0956000 0 875 1 1 20 100 c58509c0 getty c0b8c000 0 877 1 1 20 140 c5850c40 update c0486000 0 879 659 0 20 0 c025b0e0 crashdump2 ============================================================================== 60 active task structs found >> task -f c039c000 ADDR UID PID PPID STATE PRI FLAGS MM NAME ============================================================================== c039c000 0 2 1 1 20 40 c023aa20 kflushd TSS: ESP0:0xc039e000, ESP:0xc039df7c, EIP:0xc010f38b, EBP:0x0 EAX:0x0, ECX:0x0, EBX:0x0 ============================================================================== 1 active task struct found >> help trace COMMAND: trace [-a] [-f] [-w outfile] [[task_list] | [-t tracerec_list] Displays a stack trace for each task included in task_list. If task_list is empty and deftask is set, then a stack trace for the default task is displayed. If deftask is not set, then a trace will be displayed for the task running at the time of a system PANIC. If the command is issued with the -t command line option, additional items on the command line will be treated as pointers to lcrash stack trace records (prevously allocated using the mktrace command). >> t c039c000 ================================================================ STACK TRACE FOR TASK: 0xc039c000 (kflushd) 0 schedule+339 [0xc010f38b] 1 interruptible_sleep_on+49 [0xc010f6e9] 2 bdflush+571 [0xc0125aa7] 3 kernel_thread+33 [0xc0106521] ================================================================ >> t -f c039c000 ================================================================ STACK TRACE FOR TASK: 0xc039c000 (kflushd) 0 schedule+339 [0xc010f38b] RA=0xc010f6ee, SP=0xc039df7c, FP=0xc039dfa4, SIZE=44 c039df7c: c039dfa0 0000003b c0252000 c039dfb0 c039df8c: 00000286 00000003 0000003b c0252000 c039df9c: c0262000 c039dfb8 c010f6ee 1 interruptible_sleep_on+49 [0xc010f6e9] RA=0xc0125aac, SP=0xc039dfa8, FP=0xc039dfbc, SIZE=24 c039dfa8: c17b7380 00003913 c039c000 c023fcec c039dfb8: 000001f4 c0125aac 2 bdflush+571 [0xc0125aa7] RA=0xc0106523, SP=0xc039dfc0, FP=0xc039dff0, SIZE=52 c039dfc0: c039c000 00000f00 c009dfcc c0106000 c039dfd0: 00000000 c0106000 c17b70e0 00003b08 c039dfe0: 00000008 c039c000 00000003 c17b7380 c039dff0: c0106523 3 kernel_thread+33 [0xc0106521] RA=0x0, SP=0xc039dfc0, FP=0xc039dffc, SIZE=16 c039dfc0: 00000000 00000f00 c0253fd8 00000000 ================================================================ >> help dump COMMAND: dump [-d] [-o] [-x] [-B] [-D] [-H] [-W] [-w outfile] addr [count] Display count values starting at kernel virtual address addr in one of the following formats: decimal (-d), octal (-o), or hexadecimal (-x). The default format is hexidecimal, and the default count is 1. If addr is preceeded by a pound sign ('#'), it will be treated as a page number (PFN). >> dump c039dfc0 20 0xc039dfc0: c039c000 00000f00 c009dfcc c0106000 : ..9..........`.. 0xc039dfd0: 00000000 c0106000 c17b70e0 00003b08 : .....`...p{..;.. 0xc039dfe0: 00000008 c039c000 00000003 c17b7380 : ......9......s{. 0xc039dff0: c0106523 00000000 00000f00 c0253fd8 : #e...........?%. 0xc039e000: 00000000 00000000 00000000 00000000 : ................ >> help dis COMMAND: dis [-f] [-w outfile] [-F funcname]|addr[count|[bcount acount]] Display the disassembled code for addr for count instructions (the default count is 1). Alternately, display the disassembled code for addr with bcount instructions before and acount instructions after. If bcount or acount is zero, then no instructions will be displayed before or after respectively. If the dis command is issued with the -f command line option, additional information will be displayed (opcode and byte size). If the dis command is issued with the -F option followed by funcname, disassembled code will be displayed for all instructions in the function. >> dis 0xc0106521 3 5 0xc0106521 : call *%edx 0xc0106523 : movl $0x1,%eax 0xc0106528 : int $0x80 0xc010652a : movl %eax,%edx 0xc010652c : popl %ebx 0xc010652d : popl %esi These are examples of some of the more useful commands (from a debugging point of view). If you notice any problems with any of the commands, can't figure out what a particular command is supposed to do, have an idea for a useful command, etc. please let us know. Thanks for taking the time to try these facilities out... Tom From owner-lkcd@oss.sgi.com Tue Nov 9 11:13:54 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 11:13:44 -0800 Received: from mailext02.compaq.com ([207.18.199.33]:22479 "HELO mailext02.compaq.com") by oss.sgi.com with SMTP id ; Tue, 9 Nov 1999 11:13:21 -0800 Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext02.compaq.com (Postfix) with ESMTP id 58A899A972; Tue, 9 Nov 1999 13:18:25 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id D7FC84FB0C; Tue, 9 Nov 1999 13:18:07 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint12.im.hou.compaq.com (Postfix) with SMTP id 5B7984C902; Tue, 9 Nov 1999 13:18:07 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA21059; Tue, 9 Nov 1999 12:18:24 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA25300; Tue, 9 Nov 1999 12:18:23 -0700 Content-Length: 561 Message-Id: X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 In-Reply-To: <38286055.1CBFB5EF@sgi.com> Date: Tue, 09 Nov 1999 13:19:59 -0700 (MST) Reply-To: Brian Hall From: Brian Hall To: Tom Morano Subject: Re: testing lkcd Cc: lkcd@oss.sgi.com Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Thanks for the detailed reply. But will lkcd work if there is a big crash and interrupts can't be handled? The worst crashes in Linux usually end with "Aieee, killing interrupt handler" ! On 09-Nov-99 Tom Morano wrote: > Brian Hall wrote: >> >> Will the crash dump work if the interrupt handler dies? I have a script that >> will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to >> do >> that with 2.2.13. Can someone tell me how to cause this? I'd like to test >> this >> case. -- Brian Hall Linux Consultant From owner-lkcd@oss.sgi.com Tue Nov 9 11:53:09 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 11:52:59 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:5153 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 11:52:46 -0800 Received: from loco.csd.sgi.com (loco.csd.sgi.com [150.166.1.62]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA01234 for ; Tue, 9 Nov 1999 11:58:57 -0800 (PST) mail_from (tjm@sgi.com) Received: from sgi.com (localhost.csd.sgi.com [127.0.0.1]) by loco.csd.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA69133; Tue, 9 Nov 1999 11:57:40 -0800 (PST) Message-ID: <38287CB2.11C28A40@sgi.com> Date: Tue, 09 Nov 1999 11:57:38 -0800 From: Tom Morano X-Mailer: Mozilla 4.61C-SGI [en] (X11; I; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: Brian Hall CC: lkcd@oss.sgi.com Subject: Re: testing lkcd References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Brian Hall wrote: > > Thanks for the detailed reply. But will lkcd work if there is a big crash and > interrupts can't be handled? The worst crashes in Linux usually end with > "Aieee, killing interrupt handler" ! It SHOULD work. If it doesn't, we consider that a bug and will work to fix it. If you have details of cases where the dump doesn't get created, we need to know about it. Since Matt has done most of the work in the kernel (where this is an issue), I'll let him chew on this one... Thanks, Tom > > On 09-Nov-99 Tom Morano wrote: > > Brian Hall wrote: > >> > >> Will the crash dump work if the interrupt handler dies? I have a script that > >> will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to > >> do > >> that with 2.2.13. Can someone tell me how to cause this? I'd like to test > >> this > >> case. > > -- > Brian Hall > Linux Consultant From owner-lkcd@oss.sgi.com Tue Nov 9 12:10:49 1999 Received: by oss.sgi.com id ; Tue, 9 Nov 1999 12:10:40 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:63270 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 12:10:14 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA00033 for ; Tue, 9 Nov 1999 12:16:20 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id MAA16499; Tue, 9 Nov 1999 12:13:54 -0800 (PST) Date: Tue, 9 Nov 1999 12:13:53 -0800 (PST) From: Matt Robinson To: Brian Hall cc: lkcd@oss.sgi.com, torvalds@transmeta.com Subject: Re: testing lkcd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Tue, 9 Nov 1999, Brian Hall wrote: |>Thanks for the detailed reply. But will lkcd work if there is a big crash and |>interrupts can't be handled? The worst crashes in Linux usually end with |>"Aieee, killing interrupt handler" ! Right now, there's not a hook in do_exit(), but there is in die(). The real issue is making sure we put the dump_execute() in the right location if do_exit() is called directly from a driver. We might also want to make crash dumping in interrupt handlers optional (configurable from user-land). Under normal circumstances, if die() is called, we actually never get to the "Aieee" message -- we'll dump system memory and exit. There are some cases where die() isn't referred to directly, but those shouldn't matter too much (like sys_reboot()). If you have suggestions, let me know. I'd typically add it before we lock the kernel, and not terminate anything (as far as files, timers, etc. are concerned), so we catch as much of the screwed up system state as possible. Of course, doing this means that you eliminate a whole lot of clean-up work. Remember, there is a hook in die(). This catches a TON of cases. I'm looking to find dumps where die() isn't called. Again, we expect that most dumps will be saved correctly. The biggest issue as far as we are concerned is making sure 'lcrash' can read the stack trace and give you output as to what happened both in the interrupt handler and the kernel stack page for the associated task. If you have a very good example for an interrupt handler panic, pass it on. I'm in the process of doing a number of things all at once, and I haven't created one yet. Thanks for the feedback, and let us know what else we can provide. Also, for everyone else on this list, we'll be releasing a LKCD development priority list in the next day or so which will list out what our biggest concerns for future development are, and where we are focusing our efforts. If you have any desire to do development, speak up, we're more than happy to share the load. We feel this product has tremendous potential in the future for commercial customers and support companies who want reliable and fast ways of getting system crash information. Time to start asking Linus for acceptance ... :) --Matt P.S. For Linus, the link is http://oss.sgi.com/projects/lkcd/ ... |>On 09-Nov-99 Tom Morano wrote: |>> Brian Hall wrote: |>>> |>>> Will the crash dump work if the interrupt handler dies? I have a script that |>>> will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to |>>> do |>>> that with 2.2.13. Can someone tell me how to cause this? I'd like to test |>>> this |>>> case. |> |>-- |>Brian Hall |>Linux Consultant From owner-lkcd@oss.sgi.com Wed Nov 10 07:28:01 1999 Received: by oss.sgi.com id ; Wed, 10 Nov 1999 07:27:50 -0800 Received: from smtp.stna.dgac.fr ([143.196.40.29]:61127 "EHLO smtp.stna.dgac.fr") by oss.sgi.com with ESMTP id ; Wed, 10 Nov 1999 07:27:42 -0800 Received: from email.stna.dgac.fr (email [143.196.40.31]) by smtp.stna.dgac.fr (8.9.1a/8.9.1) with ESMTP id QAA25298 for ; Wed, 10 Nov 1999 16:32:34 +0100 (MET) Received: from jordan.stna.dgac.fr (jordan.stna.dgac.fr [143.196.38.154]) by email.stna.dgac.fr (8.9.1a/8.9.1) with ESMTP id QAA26399 for ; Wed, 10 Nov 1999 16:32:30 +0100 (MET) Received: from stna.dgac.fr (localhost [127.0.0.1]) by jordan.stna.dgac.fr (8.8.8/8.8.3) with ESMTP id QAA11788 for ; Wed, 10 Nov 1999 16:32:28 +0100 (MET) Message-ID: <3829900C.262B233C@stna.dgac.fr> Date: Wed, 10 Nov 1999 16:32:28 +0100 From: DUFOUR Laurent Organization: ATOS 7SB K167 tel: 05.62.14.50.36 X-Mailer: Mozilla 4.61 [fr] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: lkcd@oss.sgi.com Subject: lkcd with IDE disk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Hi, I've discovered your kernel dump feature, but I can't use it on my system which is based on IDE disk. Why lkcd work only with SCSI disk ? Thank you for your great work. Linux will become more "professional" now ! Laurent Dufour. From owner-lkcd@oss.sgi.com Wed Nov 10 10:38:51 1999 Received: by oss.sgi.com id ; Wed, 10 Nov 1999 10:38:41 -0800 Received: from mailext02.compaq.com ([207.18.199.33]:22669 "HELO mailext02.compaq.com") by oss.sgi.com with SMTP id ; Wed, 10 Nov 1999 10:38:28 -0800 Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext02.compaq.com (Postfix) with ESMTP id 2AADE9AA11; Wed, 10 Nov 1999 12:43:37 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id 89EBEBC4D8; Wed, 10 Nov 1999 12:43:13 -0600 (CST) Received: from cxo3ns.cxo.dec.com (cxo3ns.cxo.dec.com [16.63.0.10]) by mailint02.im.hou.compaq.com (Postfix) with SMTP id DC0CAB2A42; Wed, 10 Nov 1999 12:43:12 -0600 (CST) Received: from brownfur.cxo.dec.com by cxo3ns.cxo.dec.com; (5.65v4.0/1.1.8.2/11Apr96-1001AM) id AA25796; Wed, 10 Nov 1999 11:43:35 -0700 Received: from dhcp96-64.cxo.dec.com by brownfur.cxo.dec.com (5.65v4.0/1.1.10.5/17Feb98-0753AM) id AA03379; Wed, 10 Nov 1999 11:43:34 -0700 Content-Length: 2739 X-Mailer: XFMail 1.4.0 on Linux X-Priority: 3 (Normal) X-Imap-Num: 8 Received: from mailint11.im.hou.compaq.com ([172.18.229.189]) by exchou-gh01.cca.cpqcorp.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2559.0) id WQG0ZWSX; Tue, 9 Nov 1999 14:15:56 -0600 Received: by mailint11.im.hou.compaq.com (Postfix, from userid 12345) id DE6FF55F0A; Tue, 9 Nov 1999 14:15:48 -0600 (CST) Received: from mailext01.compaq.com (mailext01.compaq.com [207.18.199.32]) by mailint11.im.hou.compaq.com (Postfix) with ESMTP id CFC9F52D01 for ; Tue, 9 Nov 1999 14:15:48 -0600 (CST) Received: from oss.sgi.com (oss.sgi.com [216.32.174.118]) by mailext01.compaq.com (Postfix) with ESMTP id 0D83444CD0F for ; Tue, 9 Nov 1999 14:15:56 -0600 (CST) Received: by oss.sgi.com id ; Tue, 9 Nov 1999 12:10:40 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:63270 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 9 Nov 1999 12:10:14 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA00033 for ; Tue, 9 Nov 1999 12:16:20 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id MAA16499; Tue, 9 Nov 1999 12:13:54 -0800 (PST) Date: Tue, 9 Nov 1999 12:13:53 -0800 (PST) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From: Matt Robinson To: Brian Hall Subject: Re: testing lkcd Cc: lkcd@oss.sgi.com, torvalds@transmeta.com Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Tue, 9 Nov 1999, Brian Hall wrote: |>Thanks for the detailed reply. But will lkcd work if there is a big crash and |>interrupts can't be handled? The worst crashes in Linux usually end with |>"Aieee, killing interrupt handler" ! Right now, there's not a hook in do_exit(), but there is in die(). The real issue is making sure we put the dump_execute() in the right location if do_exit() is called directly from a driver. We might also want to make crash dumping in interrupt handlers optional (configurable from user-land). Under normal circumstances, if die() is called, we actually never get to the "Aieee" message -- we'll dump system memory and exit. There are some cases where die() isn't referred to directly, but those shouldn't matter too much (like sys_reboot()). If you have suggestions, let me know. I'd typically add it before we lock the kernel, and not terminate anything (as far as files, timers, etc. are concerned), so we catch as much of the screwed up system state as possible. Of course, doing this means that you eliminate a whole lot of clean-up work. Remember, there is a hook in die(). This catches a TON of cases. I'm looking to find dumps where die() isn't called. Again, we expect that most dumps will be saved correctly. The biggest issue as far as we are concerned is making sure 'lcrash' can read the stack trace and give you output as to what happened both in the interrupt handler and the kernel stack page for the associated task. If you have a very good example for an interrupt handler panic, pass it on. I'm in the process of doing a number of things all at once, and I haven't created one yet. Thanks for the feedback, and let us know what else we can provide. Also, for everyone else on this list, we'll be releasing a LKCD development priority list in the next day or so which will list out what our biggest concerns for future development are, and where we are focusing our efforts. If you have any desire to do development, speak up, we're more than happy to share the load. We feel this product has tremendous potential in the future for commercial customers and support companies who want reliable and fast ways of getting system crash information. Time to start asking Linus for acceptance ... :) --Matt P.S. For Linus, the link is http://oss.sgi.com/projects/lkcd/ ... |>On 09-Nov-99 Tom Morano wrote: |>> Brian Hall wrote: |>>> |>>> Will the crash dump work if the interrupt handler dies? I have a script that |>>> will kill a 2.2.5-2.2.10 kernel via a TCP exploit, but I don't know a way to |>>> do |>>> that with 2.2.13. Can someone tell me how to cause this? I'd like to test |>>> this |>>> case. |> |>-- |>Brian Hall |>Linux Consultant From owner-lkcd@oss.sgi.com Wed Nov 10 12:37:00 1999 Received: by oss.sgi.com id ; Wed, 10 Nov 1999 12:36:51 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:62998 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Wed, 10 Nov 1999 12:36:26 -0800 Received: from awesome.engr.sgi.com ([150.166.49.119]) by sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA860374 for ; Wed, 10 Nov 1999 12:41:21 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id MAA20300; Wed, 10 Nov 1999 12:39:57 -0800 (PST) Date: Wed, 10 Nov 1999 12:39:57 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: DUFOUR Laurent cc: lkcd@oss.sgi.com Subject: Re: lkcd with IDE disk In-Reply-To: <3829900C.262B233C@stna.dgac.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing A number of people are looking at the IDE port right now. The reason for the lack of IDE support is that raw I/O currently only works for SCSI disks (as covered by FAQ question #2.2): http://oss.sgi.com/projects/lkcd/faq.html#2.2 We're working to make the product better ... Tom and I will release our set of priorities later today which will include what we are working on and what we'd like to see for the next release. We hope to have IDE support as soon as possible. Thanks! --Matt P.S. Thanks to Marc Esipovich for working with us on IDE. On Wed, 10 Nov 1999, DUFOUR Laurent wrote: |>Hi, |> |>I've discovered your kernel dump feature, but I can't use it on my system which |>is based on IDE disk. |>Why lkcd work only with SCSI disk ? |> |>Thank you for your great work. Linux will become more "professional" now ! |> |>Laurent Dufour. From owner-lkcd@oss.sgi.com Thu Nov 11 16:39:28 1999 Received: by oss.sgi.com id ; Thu, 11 Nov 1999 16:39:19 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:56861 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 11 Nov 1999 16:38:58 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id QAA05186 for ; Thu, 11 Nov 1999 16:40:08 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id QAA83222 for ; Thu, 11 Nov 1999 16:42:58 -0800 (PST) Date: Thu, 11 Nov 1999 16:42:58 -0800 (PST) From: Matt Robinson To: lkcd@oss.sgi.com Subject: LKCD Priority List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Here is our current set of priorities for work we'd like to do in the LKCD project. I haven't included them in any specific order: - Create a mechanism for verifying a proper match between the map.N and vmdump.N. There is currently no synchronization method. The intended implementation is to provide a "magic number" which is specific for each kernel build. (DONE) - Add additional commands to 'lcrash' that print out various kernel data structures such as kiobufs, lock structures, files, etc. - Work to develop IDE support for raw I/O. - Provide support for people porting LKCD to new platforms. - Add better namelist support for structure dumping. This will include creating and installing a namelist object on boot, and modifications to the boot-up scripts to copy the namelist and give it a bounds index. - Add CPU specific status in the crash report. This involves creating a processor specific data structure in the kernel that will contain state information about the active task, register values, etc. - Add page typing mechanism to the kernel to take advantage of selective dumping process (e.g., don't dump free pages, user pages, etc.), to eliminate pages not being used in the kernel. - A port to Linux 2.3.X (latest). - Complete full dbx-like print mechanism in 'lcrash'. - Continued bug fixes for any problems found in current version. There may be other points I'm neglecting, so feel free to point out what you feel is missing or something you'd like to see. Thanks. --Matt From owner-lkcd@oss.sgi.com Thu Nov 11 21:49:19 1999 Received: by oss.sgi.com id ; Thu, 11 Nov 1999 21:49:10 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:41996 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Thu, 11 Nov 1999 21:48:51 -0800 Received: (qmail 16033 invoked by uid 502); 12 Nov 1999 05:54:03 -0000 Message-ID: <19991112055403.16032.qmail@mail.ocs.com.au> Received: (qmail 16026 invoked from network); 12 Nov 1999 05:54:02 -0000 Received: from ocs4.ocs-net (192.168.255.4) by mail.ocs.com.au with SMTP; 12 Nov 1999 05:54:02 -0000 X-Mailer: exmh version 2.0.2 From: Keith Owens To: lkcd@oss.sgi.com Subject: Re: LKCD Priority List In-reply-to: Your message of "Thu, 11 Nov 1999 16:42:58 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 16:54:01 +1100 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Thu, 11 Nov 1999 16:42:58 -0800 (PST), Matt Robinson wrote: > - A port to Linux 2.3.X (latest). Done for 2.3.26, bar the lack of kernel mappings for kiobufs. When SCT finishes his new kiobuf mapping mechanism, I'll upgrade my patch, get it working and release it. >There may be other points I'm neglecting, so feel free to point out >what you feel is missing or something you'd like to see. Thanks. Module support. We need to dump pages occupied by modules and construct a merged System.map that includes all the module symbols as well as the kernel symbols. ksymoops -s already builds a merged map from System.map, /proc/ksyms and the module object files, no point in reinventing the wheel. As both the ksymoops and modutils maintainer, I guess I'll volunteer to hook ksymoops and lkcd together. From owner-lkcd@oss.sgi.com Thu Nov 11 22:56:19 1999 Received: by oss.sgi.com id ; Thu, 11 Nov 1999 22:56:10 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:56944 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 11 Nov 1999 22:55:52 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA05452 for ; Thu, 11 Nov 1999 22:57:01 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id WAA23798; Thu, 11 Nov 1999 22:59:49 -0800 (PST) Date: Thu, 11 Nov 1999 22:59:49 -0800 (PST) From: Matt Robinson Reply-To: Matt Robinson To: Keith Owens cc: lkcd@oss.sgi.com Subject: Re: LKCD Priority List In-Reply-To: <19991112055403.16032.qmail@mail.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Fri, 12 Nov 1999, Keith Owens wrote: |>On Thu, 11 Nov 1999 16:42:58 -0800 (PST), |>Matt Robinson wrote: |>> - A port to Linux 2.3.X (latest). |> |>Done for 2.3.26, bar the lack of kernel mappings for kiobufs. When SCT |>finishes his new kiobuf mapping mechanism, I'll upgrade my patch, get |>it working and release it. Cool. It'd be nice to utilize the same thing for 2.2.X, so we don't have the layer violation, but it'l have to do for now. |>>There may be other points I'm neglecting, so feel free to point out |>>what you feel is missing or something you'd like to see. Thanks. |> |>Module support. We need to dump pages occupied by modules and |>construct a merged System.map that includes all the module symbols as |>well as the kernel symbols. ksymoops -s already builds a merged map |>from System.map, /proc/ksyms and the module object files, no point in |>reinventing the wheel. As both the ksymoops and modutils maintainer, I |>guess I'll volunteer to hook ksymoops and lkcd together. Okee, let me know if you need help on this. I'm working with Marc Episovich right now on the IDE port, offering suggestions, etc. We'll also have a 1.0.3 to check in tomorrow with two bug fixes to 'lcrash', a kernel enhancement for the magic_number stuff, and two new 'lcrash' commands. Thanks, Keith and everyone else. --Matt From owner-lkcd@oss.sgi.com Thu Nov 11 23:16:25 1999 Received: by oss.sgi.com id ; Thu, 11 Nov 1999 23:16:15 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:58380 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Thu, 11 Nov 1999 23:15:59 -0800 Received: (qmail 16597 invoked by uid 502); 12 Nov 1999 07:21:13 -0000 Message-ID: <19991112072112.16596.qmail@mail.ocs.com.au> Received: (qmail 16590 invoked from network); 12 Nov 1999 07:21:10 -0000 Received: from ocs4.ocs-net (192.168.255.4) by mail.ocs.com.au with SMTP; 12 Nov 1999 07:21:10 -0000 X-Mailer: exmh version 2.0.2 From: Keith Owens To: lkcd@oss.sgi.com Subject: Re: LKCD Priority List In-reply-to: Your message of "Thu, 11 Nov 1999 22:59:49 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 18:21:10 +1100 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Thu, 11 Nov 1999 22:59:49 -0800 (PST), Matt Robinson wrote: >Cool. It'd be nice to utilize the same thing for 2.2.X... Which brings up a question. Why bother with lkcd for 2.2. kernels? IMHO, there is little or no chance that a change of this magnitude will be accepted into the stable, production kernel tree. Especially when the 2.3 freeze followed by the release of 2.4 is getting ever closer. If you concentrate on 2.2, you will only have to redo all the work for 2.3, taking into account the 2.3 kernel changes. You might be better off concentrating on 2.3. I know that most distributions are using 2.2 kernels but that is irrelevant for a patch like this. Users who just install from a distribution and run it will not bother getting a new kernel and they definitely will not apply a 26,000 line patch. The sort of user who will apply a big patch, install new programs, change init scripts etc. is almost certainly running 2.3 kernels already. Get the patch into 2.3 now so it appears on distributions when 2.4 comes out. From owner-lkcd@oss.sgi.com Thu Nov 11 23:31:45 1999 Received: by oss.sgi.com id ; Thu, 11 Nov 1999 23:31:35 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:59458 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 11 Nov 1999 23:31:15 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id XAA02940 for ; Thu, 11 Nov 1999 23:37:39 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id XAA26792; Thu, 11 Nov 1999 23:35:10 -0800 (PST) Date: Thu, 11 Nov 1999 23:35:10 -0800 (PST) From: Matt Robinson To: Keith Owens cc: torvalds@transmeta.com, lkcd@oss.sgi.com Subject: Re: LKCD Priority List In-Reply-To: <19991112072112.16596.qmail@mail.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Fri, 12 Nov 1999, Keith Owens wrote: |>On Thu, 11 Nov 1999 22:59:49 -0800 (PST), |>Matt Robinson wrote: |>>Cool. It'd be nice to utilize the same thing for 2.2.X... |> |>Which brings up a question. Why bother with lkcd for 2.2. kernels? |>IMHO, there is little or no chance that a change of this magnitude will |>be accepted into the stable, production kernel tree. Especially when |>the 2.3 freeze followed by the release of 2.4 is getting ever closer. |>If you concentrate on 2.2, you will only have to redo all the work for |>2.3, taking into account the 2.3 kernel changes. You might be better |>off concentrating on 2.3. We intend to concentrate getting this pushed into the 2.3 tree; however, we also want to make sure older releases that are going out in more commercial environments also have as many extended features as possible. It's more an issue with the direction and concentration of porting effort. We can do our work in 2.3, sure; but we can't neglect 2.2 for customers that want this feature and a stable kernel as well. As a general rule, I agree with you. |>I know that most distributions are using 2.2 kernels but that is |>irrelevant for a patch like this. Users who just install from a |>distribution and run it will not bother getting a new kernel and they |>definitely will not apply a 26,000 line patch. The sort of user who |>will apply a big patch, install new programs, change init scripts etc. |>is almost certainly running 2.3 kernels already. Get the patch into |>2.3 now so it appears on distributions when 2.4 comes out. Let's hope Linus lets it in ... We'd love to make it a part of the general release as soon as possible. And we'd do most of our work in the 2.3 tree ... Linus? --Matt From owner-lkcd@oss.sgi.com Fri Nov 12 22:05:51 1999 Received: by oss.sgi.com id ; Fri, 12 Nov 1999 22:05:41 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:7472 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Fri, 12 Nov 1999 22:05:27 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id WAA09294 for ; Fri, 12 Nov 1999 22:11:58 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id WAA30458; Fri, 12 Nov 1999 22:09:32 -0800 (PST) Date: Fri, 12 Nov 1999 22:09:32 -0800 (PST) From: Matt Robinson To: lkcd@oss.sgi.com cc: linux-kernel@vger.rutgers.edu Subject: LKCD Version 1.0.3 Available Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing Version 1.0.3 is now available. Please review the README file in the download directory for more details on what has changed. Also, let us know if there are things you'd like to see added, changed, etc. The download location is: http://oss.sgi.com/projects/lkcd/download/ In addition, Keith Owens is working on the 2.3.X port. Please feel free to download his code from the experimental directory. There's still lots of work to be done on it, but if you'd like to review it and make comments, feel free. Thanks to Keith for all his efforts. For those unfamiliar with LKCD, please go to: http://oss.sgi.com/projects/lkcd/ --Matt From owner-lkcd@oss.sgi.com Tue Nov 23 09:53:58 1999 Received: by oss.sgi.com id ; Tue, 23 Nov 1999 09:53:47 -0800 Received: from [159.199.101.3] ([159.199.101.3]:14782 "EHLO orpheus.amdahl.com") by oss.sgi.com with ESMTP id ; Tue, 23 Nov 1999 09:53:31 -0800 Received: from orpheus.amdahl.com (localhost [127.0.0.1]) by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id JAA07354 for ; Tue, 23 Nov 1999 09:59:44 -0800 (PST) Received: from stella.hook.eur.amdahl.com (stella.hook.eur.amdahl.com [199.228.209.180]) by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id JAA07339; Tue, 23 Nov 1999 09:59:41 -0800 (PST) Received: from amdahl.com by stella.hook.eur.amdahl.com (8.8.8+Sun/SMI-SVR4) id RAA21423; Tue, 23 Nov 1999 17:55:46 GMT Message-ID: <383AD72C.453B3041@amdahl.com> Date: Tue, 23 Nov 1999 18:04:29 +0000 From: bob hubbard X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: lkcd@oss.sgi.com CC: rhubbard@amdahl.com Subject: Whereis /sbin/vmdump ? Content-Type: multipart/mixed; boundary="------------A202DE157F3D51B5E579613C" Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing This is a multi-part message in MIME format. --------------A202DE157F3D51B5E579613C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello , Having downloaded the available patches and files from your web site i cannot find the discussed binary called '/sbin/vmdump' . 1/ Where is this located ? . 2/ Will this function with swapfile located on IDE ? . Thanks - C U - Bob. --------------A202DE157F3D51B5E579613C Content-Type: text/x-vcard; charset=us-ascii; name="rhubbard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for bob hubbard Content-Disposition: attachment; filename="rhubbard.vcf" begin:vcard n:Hubbard;Bob tel;cell:Calling me from USA 011 44 7967 109138 tel;home:Cellular from UK - 07967 109138 tel;work:+44(0)1252 386293 x-mozilla-html:TRUE org:Amdahl version:2.1 email;internet:rhubbard@amdahl.com adr;quoted-printable:;;Note - Please use or contact me on my mobile .=0D=0AAvailable for messages and contactable globally .=0D=0A;;;; x-mozilla-cpt:;-14240 fn:Bob Hubbard end:vcard --------------A202DE157F3D51B5E579613C-- From owner-lkcd@oss.sgi.com Tue Nov 23 16:05:24 1999 Received: by oss.sgi.com id ; Tue, 23 Nov 1999 16:05:05 -0800 Received: from ppp0.ocs.com.au ([203.34.97.3]:44301 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Tue, 23 Nov 1999 16:04:42 -0800 Received: (qmail 9657 invoked by uid 502); 24 Nov 1999 00:10:50 -0000 Message-ID: <19991124001049.9656.qmail@mail.ocs.com.au> Received: (qmail 9645 invoked from network); 24 Nov 1999 00:10:47 -0000 Received: from ocs4.ocs-net (192.168.255.4) by mail.ocs.com.au with SMTP; 24 Nov 1999 00:10:47 -0000 X-Mailer: exmh version 2.0.2 From: Keith Owens To: bob hubbard cc: lkcd@oss.sgi.com Subject: Re: Whereis /sbin/vmdump ? In-reply-to: Your message of "Tue, 23 Nov 1999 18:04:29 -0000." <383AD72C.453B3041@amdahl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Nov 1999 11:10:47 +1100 Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Tue, 23 Nov 1999 18:04:29 +0000, bob hubbard wrote: >Hello , > Having downloaded the available patches and files from your web site i >cannot find the discussed binary >called '/sbin/vmdump' . >1/ Where is this located ? . linux/lcrash/scripts/sbin.vmdump, after applying the patch. "make install" copies sbin.vmdump to /sbin/vmdump. >2/ Will this function with swapfile located on IDE ? . Not at the moment, in progress. ps. When do we get Linux on Amdahl hardware ;)? From owner-lkcd@oss.sgi.com Tue Nov 23 16:30:15 1999 Received: by oss.sgi.com id ; Tue, 23 Nov 1999 16:30:05 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:10064 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 23 Nov 1999 16:29:41 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id QAA28109 for ; Tue, 23 Nov 1999 16:31:46 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id QAA61576; Tue, 23 Nov 1999 16:34:32 -0800 (PST) Date: Tue, 23 Nov 1999 16:34:31 -0800 (PST) From: Matt Robinson To: Keith Owens cc: bob hubbard , lkcd@oss.sgi.com Subject: Re: Whereis /sbin/vmdump ? In-Reply-To: <19991124001049.9656.qmail@mail.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Wed, 24 Nov 1999, Keith Owens wrote: |>On Tue, 23 Nov 1999 18:04:29 +0000, |>bob hubbard wrote: |>>Hello , |>> Having downloaded the available patches and files from your web site i |>>cannot find the discussed binary |>>called '/sbin/vmdump' . |>>1/ Where is this located ? . |> |>linux/lcrash/scripts/sbin.vmdump, after applying the patch. "make |>install" copies sbin.vmdump to /sbin/vmdump. This is correct. You shouldn't see an error if the file doesn't exist, but then again, you need it to configure your system properly. There's also a README in cmd/lcrash/scripts that discusses what each of those files are for. We need to update the READMEs to be more reflective of our move into the kernel. I'll try to have that done for 1.0.4. |>>2/ Will this function with swapfile located on IDE ? . |> |>Not at the moment, in progress. Definitely in progress. I'm working on this with Marc Esipovich, who has been looking at it as of two weeks ago. |>ps. When do we get Linux on Amdahl hardware ;)? Heh. :) The MIPS port shouldn't be that difficult, but other platforms (and the IDE work) are getting in the way. Perhaps soon. You (and Ralf Baechle) have asked for it at this point. By the way, if anyone has any experience whatsoever with IDE device drivers, I have a few questions. :) I'm utilizing do_rw_disk() in the kernel, but there's some race conditions I'm hitting that I'd like to resolve. Right now I have an ide_raw_read() that avoids the buffer cache altogether, but it occasionally hangs. Thanks, all! --Matt From owner-lkcd@oss.sgi.com Tue Nov 23 16:33:56 1999 Received: by oss.sgi.com id ; Tue, 23 Nov 1999 16:33:45 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:5457 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 23 Nov 1999 16:33:24 -0800 Received: from awesome.engr.sgi.com (awesome.engr.sgi.com [150.166.49.119]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id QAA28467 for ; Tue, 23 Nov 1999 16:35:23 -0800 (PST) mail_from (yakker@cthulhu.engr.sgi.com) Received: from localhost (yakker@localhost) by awesome.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id QAA63660; Tue, 23 Nov 1999 16:38:11 -0800 (PST) Date: Tue, 23 Nov 1999 16:38:11 -0800 (PST) From: Matt Robinson To: Matt Robinson cc: Keith Owens , bob hubbard , lkcd@oss.sgi.com Subject: Re: Whereis /sbin/vmdump ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing On Tue, 23 Nov 1999, Matt Robinson wrote: |>|>ps. When do we get Linux on Amdahl hardware ;)? |> |>Heh. :) The MIPS port shouldn't be that difficult, but other |>platforms (and the IDE work) are getting in the way. Perhaps soon. |>You (and Ralf Baechle) have asked for it at this point. As you might imagine, I'm referring to LKCD for MIPS, not necessarily LKCD (or Linux for that matter) for Amdahl specifically. :) --Matt From owner-lkcd@oss.sgi.com Wed Nov 24 01:48:17 1999 Received: by oss.sgi.com id ; Wed, 24 Nov 1999 01:48:07 -0800 Received: from orpheus.amdahl.com ([159.199.101.3]:10391 "EHLO orpheus.amdahl.com") by oss.sgi.com with ESMTP id ; Wed, 24 Nov 1999 01:47:48 -0800 Received: from orpheus.amdahl.com (localhost [127.0.0.1]) by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id BAA12391 for ; Wed, 24 Nov 1999 01:54:00 -0800 (PST) Received: from stella.hook.eur.amdahl.com (stella.hook.eur.amdahl.com [199.228.209.180]) by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id BAA12381; Wed, 24 Nov 1999 01:53:58 -0800 (PST) Received: from amdahl.com by stella.hook.eur.amdahl.com (8.8.8+Sun/SMI-SVR4) id JAA05901; Wed, 24 Nov 1999 09:49:58 GMT Message-ID: <383B20CE.1DD6BBBC@amdahl.com> Date: Tue, 23 Nov 1999 23:18:38 +0000 From: bob hubbard X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Matt Robinson CC: Keith Owens , lkcd@oss.sgi.com Subject: Re: Whereis /sbin/vmdump ? References: Content-Type: multipart/mixed; boundary="------------0296F5DB3A5EEF736BFFB236" Sender: owner-lkcd@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;lkcd-outgoing This is a multi-part message in MIME format. --------------0296F5DB3A5EEF736BFFB236 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Matt Robinson wrote: > On Wed, 24 Nov 1999, Keith Owens wrote: > |>On Tue, 23 Nov 1999 18:04:29 +0000, > |>bob hubbard wrote: > |>>Hello , > |>> Having downloaded the available patches and files from your web site i > |>>cannot find the discussed binary > |>>called '/sbin/vmdump' . > |>>1/ Where is this located ? . > |> > |>linux/lcrash/scripts/sbin.vmdump, after applying the patch. "make > |>install" copies sbin.vmdump to /sbin/vmdump. Thanks - i dumped this down yesterday applied the 'patch' to kernel AND didn't expect to run 'make install' . I just put this in place manually since , thanks . note path to which this patch went to . root@starfire64 scripts]# pwd /usr/src/linux/cmd/lcrash/scripts/Makefile ... > > > This is correct. You shouldn't see an error if the file doesn't exist, > but then again, you need it to configure your system properly. There's > also a README in cmd/lcrash/scripts that discusses what each of those > files are for. > > We need to update the READMEs to be more reflective of our move into > the kernel. I'll try to have that done for 1.0.4. > > |>>2/ Will this function with swapfile located on IDE ? . > |> > |>Not at the moment, in progress. > > Definitely in progress. I'm working on this with Marc Esipovich, who > has been looking at it as of two weeks ago. Mmm &^( , well i'll await this for my laptop playground .... > > > |>ps. When do we get Linux on Amdahl hardware ;)? You already can - ; but then we tout many architectures these days . Intel, sparc64 and 390 . > > > Heh. :) The MIPS port shouldn't be that difficult, but other > platforms (and the IDE work) are getting in the way. Perhaps soon. > You (and Ralf Baechle) have asked for it at this point. > > By the way, if anyone has any experience whatsoever with IDE device > drivers, I have a few questions. :) I'm utilizing do_rw_disk() in > the kernel, but there's some race conditions I'm hitting that I'd like > to resolve. Right now I have an ide_raw_read() that avoids the buffer > cache altogether, but it occasionally hangs. > > Thanks, all! > > --Matt --------------0296F5DB3A5EEF736BFFB236 Content-Type: text/x-vcard; charset=us-ascii; name="rhubbard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for bob hubbard Content-Disposition: attachment; filename="rhubbard.vcf" begin:vcard n:Hubbard;Bob tel;cell:Calling me from USA 011 44 7967 109138 tel;home:Cellular from UK - 07967 109138 tel;work:+44(0)1252 386293 x-mozilla-html:TRUE org:Amdahl version:2.1 email;internet:rhubbard@amdahl.com adr;quoted-printable:;;Note - Please use or contact me on my mobile .=0D=0AAvailable for messages and contactable globally .=0D=0A;;;; x-mozilla-cpt:;-14240 fn:Bob Hubbard end:vcard --------------0296F5DB3A5EEF736BFFB236--