From owner-lkcd@oss.sgi.com Thu Jun  1 08:19:23 2000
Received:  by oss.sgi.com id <S42352AbQFAPTN>;
	Thu, 1 Jun 2000 08:19:13 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:501 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42350AbQFAPSo>;
	Thu, 1 Jun 2000 08:18:44 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id KAA02462;
	Thu, 1 Jun 2000 10:18:40 -0600 (MDT)
Message-ID: <XFMail.20000601101837.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <39359B62.F543E00B@sgi.com>
Date:   Thu, 01 Jun 2000 10:18:37 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     Tom Morano <tjm@sgi.com>
Subject: Re: FW: Re: Home from vacation
Cc:     lkcd@oss.sgi.com, yakker@turbolinux.com
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

Commented out the kl_signal problem references, and applied the change to
alloc.c. Clapped a little when it actually linked. I had high hopes, but it
looks like I still have the same problem as before I left on vacation (actually
slightly worse, before I got to get_page index=4):

(gdb) run
Starting program: /usr/src/linux/cmd/lcrash/./lcrash
map = /boot/System.map, vmdump = /dev/mem, outfile = stdout
 
Please wait...................
Program received signal SIGSEGV, Segmentation fault.
0x1200278d0 in enqueue (list=0x12024d898, new=0x20251000) at alloc.c:58
58      alloc.c: No such file or directory.
(gdb) where full
#0  0x1200278d0 in enqueue (list=0x12024d898, new=0x20251000) at alloc.c:58
        head = (element_t *) 0x0
#1  0x120028930 in get_page (index=3) at alloc.c:441
        i = 0
        b = (block_t *) 0x20251000
        page = (void *) 0x120028e04
        p = (page_t *) 0x12024d880
#2  0x1200292ac in alloc_block (size=80, flag=2, ra=0x0) at alloc.c:698
        i = 3
        j = 0
        blk = (void *) 0x11ffffaf0
        p = (page_t *) 0x120034e44
        b = (block_t *) 0x0
#3  0x120003c48 in kl_block_alloc_func (size=80, flag=2, ra=0x0) at util.c:303
        b = (void *) 0x120038494
#4  0x1200384ec in _kl_alloc_block (size=80, flags=2, ra=0x0) at kl_alloc.c:22
        blk = (void *) 0x1200040b0
#5  0x1200040d0 in register_cmds (cmds=0x120153350) at command.c:20
        i = 0
        ret = 1
        max_depth = 539181536
        cmd_rec = (cmd_rec_t *) 0x100000000
#6  0x120002d90 in main (argc=1, argv=0x11ffffc18) at main.c:205
        i = 1
        c = 512
        errflg = 0
(gdb)                             

On 31-May-2000 Tom Morano wrote:
> Brian Hall wrote:
>> 
>> Local consensus is to stick with 2.2 for now. I think I have done most of
>> the
>> changes necessary in my 2.2 tree to work with 64 bit already, since I can
>> successfully (though possibly not correctly, still unverified) create a
>> dump.
>> My problem has been getting lcrash to work.
>> 
>> OK, I've gotten the 2.2 and 2.3 trees from SourceForge. I've updated my tree
>> to
>> match as closely as possible, and brought the relevant arch changes over to
>> the Alpha tree also. However, I'm having a new problem with the build in
>> libklib. The new signal handler stuff, kl_signal.c, can't find a definition
>> for
>> "greg_t", and neither can I. Doesn't seem to be defined in the 2.2 or 2.3
>> cvs
>> trees.
>> 
>> [root@localhost libklib]# mm
>> /bin/rm -f include/asm
>> (cd include ; /bin/ln -s asm-alpha asm; cd ..)
>> cc -gstabs -D__KERNEL__ -I/usr/src/linux/include -I. -Iinclude   -c -o
>> kl_signal.o kl_signal.c
>> kl_signal.c: In function `klib_sig_handler':
>> kl_signal.c:70: `greg_t' undeclared (first use in this function)
>> kl_signal.c:70: (Each undeclared identifier is reported only once
>> kl_signal.c:70: for each function it appears in.)
>> kl_signal.c:70: `gregs' undeclared (first use in this function)
>> kl_signal.c:70: structure has no member named `gregs'
>> kl_signal.c:71: parse error before `esi'
>> kl_signal.c:73: `esi' undeclared (first use in this function)
>> kl_signal.c:73: `ESI' undeclared (first use in this function)
>> kl_signal.c:74: `esp' undeclared (first use in this function)
>> kl_signal.c:74: `ESP' undeclared (first use in this function)
>> kl_signal.c:76: `badaddr' undeclared (first use in this function)
>> kl_signal.c:76: parse error before `sip'
>> make: *** [kl_signal.o] Error 1
>> 
> 
> Brian,
> 
> I had this same problem when working on ia64 stuff in the 2.3 tree. It's
> because
> the signal handler has i386 specific stuff in it. I got around this by moving
> the kl_signal.c module into the arch specific portion of the tree. I haven't
> rearranged the 2.2 tree to be 64 bit friendly yet (or non i386 architecture
> friendly for that matter), since I've been doing all my recent work in
> the 2.3 tree. I guess I'm going to have to do this soon. In the mean time,
> I would just comment out the portions of the code which are breaking your
> build (the references to esi, esp, etc.). Also, I found a problem with the
> alloc.c module that was really a pain to track down (you might have been
> bitten by this one already). The minimum size bucket is hard coded at 8
> bytes. Since the buckets get strung on a doubly linked list, the prev
> pointer overshoots the end of the bucket (2 64-bit points are > 8 bytes). 
> Just make the smallest bucket in the bucket_size[] array be 16 bytes. I'll
> let you know when I get my 2.3 arch related changes back ported to the 2.2
> tree so you can stay in synch with what I have. Sorry, but it's sometimes
> a pain keeping two moving targets lined up with each other. :]
> 
> Tom

-- 

From owner-lkcd@oss.sgi.com Thu Jun  1 08:43:13 2000
Received:  by oss.sgi.com id <S42356AbQFAPnD>;
	Thu, 1 Jun 2000 08:43:03 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:6653 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42353AbQFAPmq>;
	Thu, 1 Jun 2000 08:42:46 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id KAA08938
	for <lkcd@oss.sgi.com>; Thu, 1 Jun 2000 10:42:44 -0600 (MDT)
Message-ID: <XFMail.20000601104241.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date:   Thu, 01 Jun 2000 10:42:41 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     lkcd@oss.sgi.com
Subject: Alpha LKCD development machine available again
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

If you can't find the problem, blame the ISP, right? Bzzzzt. My fault, I had
turned off routed for some reason. Works fine now, check
http://pcisys.net/~brihall/as200 for the current IP.

-- 

From owner-lkcd@oss.sgi.com Fri Jun  2 16:57:02 2000
Received:  by oss.sgi.com id <S42268AbQFBX4x>;
	Fri, 2 Jun 2000 16:56:53 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:3256 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42238AbQFBX4b>;
	Fri, 2 Jun 2000 16:56:31 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id SAA23661
	for <lkcd@oss.sgi.com>; Fri, 2 Jun 2000 18:56:28 -0600 (MDT)
Message-ID: <XFMail.20000602185633.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.20000601104241.brianwhall@pcisys.net>
Date:   Fri, 02 Jun 2000 18:56:33 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     lkcd@oss.sgi.com
Subject: Use ssh to logon to Alpha LKCD development machine
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

I have rearranged my LAN and connected the AS200 to the switch inside the
firewall. This required me to forward a port from the firewall to the AS200,
which I have now done. Initially this was done with telnet (eeek!), but I have
gotten ssh configured, so everyone will have to login with ssh. Hopefully the
compression will help speed up remote editing sessions.

I have also greatly increased the ipmasq keepalive time on the firewall; remote
logons should no longer terminate after 15 minutes or so of being connected
through the firewall (note the as200 wasn't connected in this way before).
Please let me know if this happens often- the only reason it should happen now
is for the infrequent IP change (oh, the joys of DHCP).

On 01-Jun-2000 Brian Hall wrote:
> If you can't find the problem, blame the ISP, right? Bzzzzt. My fault, I had
> turned off routed for some reason. Works fine now, check
> http://pcisys.net/~brihall/as200 for the current IP.

-- 

From owner-lkcd@oss.sgi.com Sat Jun  3 05:44:35 2000
Received:  by oss.sgi.com id <S42279AbQFCMoP>;
	Sat, 3 Jun 2000 05:44:15 -0700
Received: from pluto.skyweb.net ([205.216.244.31]:9226 "EHLO pluto.skyweb.net")
	by oss.sgi.com with ESMTP id <S42280AbQFCMoC>;
	Sat, 3 Jun 2000 05:44:02 -0700
Received: from skyweb (06-077.028.popsite.net [216.126.181.77])
	by pluto.skyweb.net (8.9.3/8.9.0) with SMTP id IAA51159
	for <lkcd@oss.sgi.com>; Sat, 3 Jun 2000 08:47:11 -0500 (EST)
Date:   Sat, 3 Jun 2000 08:47:11 -0500 (EST)
Message-Id: <200006031347.IAA51159@pluto.skyweb.net>
MIME-Version: 1.0
From:   Drive.Storage.Technology@dst3.com
Reply-To: Drive.Storage.Technology@dst3.com
To:     lkcd@oss.sgi.com
Subject: DST-Pocket MirrorDrive, as requested
Mime-Version: 1.0 
Content-Type: text/html; charset="us-ascii"
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>DST - Drive Storage Technology Corporation</TITLE>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2314.1000" name=GENERATOR><!-- saved from url=(0029)http://www.dst3.com/email.htm --></HEAD>
<BODY bgColor=#336699 text=#ffffff><B>From:</B> 
Drive.Storage.Technology@dst3.com<BR><B>Sent:</B> Thursday, June 01, 2000 4:06 
AM<BR><B>To:</B> mirrordrive@earthlink.net<BR><B>Subject:</B> Put your subject 
line here<BR>
<DIV class=OutlookMessageHeader dir=ltr>
<TABLE border=0 cellPadding=2 width=500>
  <CAPTION>
  <TBODY><BR></TBODY></CAPTION>
  <TBODY>
  <TR>
    <TD vAlign=top><IMG align=bottom border=0 height=38 
      src="http://www.dst3.com/images/drivsto1white.gif" width=415 NOSEND="1"><A 
      href="http://www.dst3.com/pmd.htm"><IMG alt="" border=0 height=57 
      src="http://www.dst3.com/images/image001.gif" width=72 NOSEND="1"></A><A 
      href="http://www.dst3.com/pmd.htm"></A></TD></TR></TBODY></TABLE><FONT 
face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; Thank you for your 
recent inquiry regarding the <B>"AWARD WINNING" Pocket MirrorDrive 
PMD).</B></FONT></FONT> <BR><FONT face=Arial,Helvetica><FONT 
size=-1>&nbsp;&nbsp;&nbsp;&nbsp; Many of our customers originally purchased the 
<B>PMD and DataMirror Software</B> to create</FONT></FONT> <BR><FONT 
face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; an <B>exact and 
bootable</B> copy of their computers hard drive.</FONT></FONT> 
<P><FONT face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; This pocket 
size device is <B>DOS, Windows 95/98, NT and 2000 compliant</B>.&nbsp; The 
<B>PMD</B></FONT></FONT> <BR><FONT face=Arial,Helvetica><FONT 
size=-1>&nbsp;&nbsp;&nbsp;&nbsp; connects to any portable or desktop PC and is 
immediately recognized as a logical drive in</FONT></FONT> <BR><FONT 
face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; Windows 95/98 
without any software or drivers.</FONT></FONT> <BR><FONT 
face=Arial,Helvetica><FONT size=-1>&nbsp;</FONT></FONT> <BR><FONT 
face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; You can create a 
<B>bootable and exact copy</B> of your portable and desktop 
computer</FONT></FONT> <BR><FONT face=Arial,Helvetica><FONT 
size=-1>&nbsp;&nbsp;&nbsp;&nbsp; on one <B>PMD.</B> Today the <B>PMD </B>is 
regarded as a <B>"must have"</B> backup recovery device for</FONT></FONT> 
<BR><FONT face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; emergency 
hard drive restore, routine back up or to transport large data files 
between&nbsp;</FONT></FONT> <BR><FONT face=Arial,Helvetica><FONT 
size=-1>&nbsp;&nbsp;&nbsp;&nbsp; home and office.</FONT></FONT> 
<P><FONT face=Arial,Helvetica><FONT size=-1>&nbsp;&nbsp;&nbsp;&nbsp; Please 
click on the Pocket MirrorDrive picture, <STRONG>Laptop or Portable 
Computing</STRONG></FONT></FONT><STRONG> <BR></STRONG><FONT 
face=Arial,Helvetica><FONT size=-1><STRONG>&nbsp;&nbsp;&nbsp;&nbsp; 
</STRONG>editorial reviews below, or email us for further 
information.</FONT></FONT></P></DIV>
<DIV class=OutlookMessageHeader dir=ltr>&nbsp; 
<TABLE border=0 cellPadding=2 width=500>
  <CAPTION></CAPTION>
  <TBODY>
  <TR>
    <TD vAlign=top><IMG align=bottom border=0 height=38 
      src="http://www.dst3.com/images/drivsto1white.gif" width=415 NOSEND="1"><A 
      href="http://www.dst3.com/pmd.htm"><IMG alt="" border=0 height=57 
      src="http://www.dst3.com/images/image001.gif" width=72 
      NOSEND="1"></A>&nbsp; <BR><IMG alt="" border=0 height=152 
      src="http://www.dst3.com/images/dst200.jpg" width=200 NOSEND="1">&nbsp;<A 
      href="http://www.dst3.com/story2.htm"><IMG alt="" border=0 height=138 
      src="http://www.dst3.com/images/image002.gif" width=99 
      NOSEND="1"></A>&nbsp;<A href="http://www.dst3.com/story.htm"><IMG alt="" 
      border=0 height=138 src="http://www.dst3.com/images/image003.gif" width=99 
      NOSEND="1"></A>&nbsp; 
      <P><IMG align=bottom border=0 height=28 
      src="http://www.dst3.com/images/dstwhite.gif" width=75 NOSEND="1"><SPAN 
      style="FONT-SIZE: 24pt"><B><FONT face="Arial Black">P</SPAN><SPAN 
      style="FONT-SIZE: 18pt">OCKET&nbsp;</SPAN><SPAN 
      style="FONT-SIZE: 24pt">M</SPAN><SPAN 
      style="FONT-SIZE: 18pt">IRROR</SPAN><SPAN 
      style="FONT-SIZE: 24pt">D</SPAN><SPAN 
      style="FONT-SIZE: 18pt">RIVE</SPAN></FONT><FONT face=Arial><FONT 
      size=-1>&#8482;<SPAN style="FONT-SIZE: 18pt"></FONT></FONT><FONT 
      face="Arial Black">&nbsp;</SPAN></FONT></B>&nbsp; <BR>&nbsp; 
      <CENTER>
      <TABLE border=0 width="92%">
        <CAPTION>
        <CENTER></CENTER>
        <TBODY></CENTER>
        <CENTER></TBODY></CENTER></CAPTION>
        <TBODY>
        <TR>
          <TD>
            <CENTER><B><I><FONT face=Arial><FONT color=#99ffff>" THE ULTIMATE 
            POCKET SIZE REMOVABLE HARD DRIVE AND BACK UP STORAGE SOLUTION FOR 
            LAPTOP AND DESKTOP COMPUTERS AVAILABLE FROM 2GB TO OVER 
            25GB"</FONT></FONT></I></B></CENTER>
            <CENTER>&nbsp;</CENTER>
            <CENTER><SPAN class=340450715-31052000><B><FONT face=Arial>The DST 
            12GB Pocket MirrorDrive is now on sale for under $600.00 with your 
            choice of PCMCIA, Parallel , USB cable or desktop 
            cradle&nbsp;</SPAN>&nbsp;<SPAN class=340450715-31052000>for a direct 
            IDE connection.</FONT></B></SPAN></CENTER>
            <CENTER><SPAN 
        class=340450715-31052000></SPAN>&nbsp;</CENTER></TD></TR></TBODY></TABLE>
      <CENTER></CENTER>
      <CENTER><SPAN style="FONT-SIZE: 14pt"><B><FONT 
      face=Arial>CALL&nbsp;</SPAN><FONT face=Arial size=2><IMG align=bottom 
      border=0 height=16 src="http://www.dst3.com/images/dstwhite.gif" width=40 
      NOSEND="1"></FONT><SPAN style="FONT-SIZE: 14pt"> DIRECT TOLL FREE 
      800-218-8000</FONT></B></SPAN></CENTER>
      <P><IMG align=right border=0 height=152 
      src="http://www.dst3.com/images/dst200.jpg" width=200 NOSEND="1"><B><FONT 
      face=Arial><FONT size=-1>&nbsp;The&nbsp;<FONT face=Arial size=2><IMG 
      align=bottom border=0 height=16 
      src="http://www.dst3.com/images/dstwhite.gif" width=40 NOSEND="1"></FONT> 
      Pocket Mirror Drive&#8482;&nbsp;</FONT></FONT></B>&nbsp; <BR><B><FONT 
      face=Arial><FONT size=-1>is the only portable hard 
      drive&nbsp;</FONT></FONT></B>&nbsp; <BR><B><FONT face=Arial><FONT 
      size=-1>back up solution that creates an&nbsp;</FONT></FONT></B>&nbsp; 
      <BR><B><FONT face=Arial><FONT size=-1><I><FONT color=#ffff00>"exact and 
      bootable mirror copy"</FONT></I>&nbsp;</FONT></FONT></B>&nbsp; 
      <BR><B><FONT face=Arial><FONT size=-1>of the computers entire hard drive 
      including the OS, applications, data, screen savers and all user settings. 
      The&nbsp;<FONT face=Arial size=2><IMG align=bottom border=0 height=16 
      src="http://www.dst3.com/images/dstwhite.gif" width=40 
      NOSEND="1"></FONT>-Data Mirror Software&#8482; offers the most comprehensive and 
      automatic user programmable back routine available in the computer 
      industry today.&nbsp;</FONT></FONT></B>&nbsp; 
      <P><B><FONT face=Arial><FONT color=#99ffff><FONT size=-1>This 
      revolutionary storage product is cost effective, 10 times faster, has 
      greater capacity and is more versatile than any other removable storage 
      product including Jaz, Onstream, Orb, Syquest and 
      Zip.&nbsp;</FONT></FONT></FONT></B>&nbsp; 
      <P><B><FONT face=Arial><FONT color=#ffff00><FONT size=-1>You can travel 
      with the ability to connect to any notebook or desktop PC via PCMCIA, USB 
      and or Parallel Cable and access your proposals, applications and data 
      files exactly the way you left them.&nbsp;</FONT></FONT></FONT></B>&nbsp; 
      <P><B><FONT face=Arial><FONT size=-1>The software creates an exact copy of 
      your hard drive and makes it fast and simple to routinely back up 
      your&nbsp;<FONT face=Arial size=2><IMG align=bottom border=0 height=16 
      src="http://www.dst3.com/images/dstwhite.gif" width=40 NOSEND="1"></FONT> 
      Pocket Mirror Drive</FONT></FONT></B>.&nbsp; 
      <P><B><FONT face=Arial><FONT color=#99ffff><FONT size=-1>DON'T RISK LOSING 
      YOUR PRECIOUS DATA TO A VIRUS!!</FONT></FONT></FONT></B>&nbsp; <BR><FONT 
      face=Arial size=2><IMG align=bottom border=0 height=16 
      src="http://www.dst3.com/images/dstwhite.gif" width=40 
      NOSEND="1"></FONT><B><FONT face=Arial><FONT size=-1>&nbsp;<FONT 
      color=#99ffff>MAKES BACKUPS AND RESTORING QUICK AND 
      EASY!</FONT></FONT></FONT></B>&nbsp; 
      <P><FONT face=ARIAL><FONT size=+1>Could this happen to 
      you?</FONT></FONT>&nbsp; 
      <UL>
        <LI><FONT face=Arial><FONT size=-1>Your computer has developed an 
        <B>unknown virus!</B></FONT></FONT>&nbsp; 
        <LI><FONT face=Arial><FONT size=-1>Your hard drive has<B> 
        crashed.</B>..with no back up!</FONT></FONT>&nbsp; 
        <LI><FONT face=Arial><FONT size=-1>You unexpectedly lose your job! 
        You'll lose your computer, database of contacts, phone numbers, email 
        addresses, virtually..........&nbsp;</FONT></FONT> <BR><B><I><FONT 
        face=Arial><FONT color=#99ffff><FONT size=-1>YOUR WHOLE 
        WORLD!&nbsp;</FONT></FONT></FONT></I></B>&nbsp; 
        <P><IMG align=bottom border=0 height=28 
        src="http://www.dst3.com/images/dstwhite.gif" width=75 NOSEND="1"><FONT 
        face=ARIAL><FONT size=+2>&nbsp;<FONT color=#99ffff>IS THE ONLY 
        SOLUTION!</FONT></FONT></FONT>&nbsp;</P></LI></UL>
      <DIV><SPAN 
      class=500215013-31052000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      <B><FONT face=Arial><FONT color=#ffffff><FONT size=+1><A 
      href="http://www.dst3.com">http://www.dst3.com</A></FONT></FONT></FONT></B>&nbsp;</SPAN><SPAN 
      class=500215013-31052000><SPAN 
      class=340450715-31052000>&nbsp;</SPAN></SPAN></DIV>
      <DIV><SPAN class=500215013-31052000><SPAN 
      class=340450715-31052000></SPAN></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=500215013-31052000><SPAN 
      class=340450715-31052000>&nbsp;&nbsp;&nbsp;&nbsp;<SPAN 
      class=410101410-01062000><A 
      href="mailto:sales@dst3.com">sales@dst3.com</A>&nbsp;</SPAN>&nbsp;&nbsp; 
      <FONT color=#ffffff><A 
      href="mailto:info@dst3.com">info@dst3.com</A>&nbsp;</FONT></SPAN>&nbsp;</SPAN><SPAN 
      class=340450715-31052000>&nbsp;&nbsp;<SPAN class=410101410-01062000><A 
      href="mailto:tech@dst3.com">tech@dst3.com</A></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></DIV>
      <DIV>© <FONT size=-1>2000 Drive Storage Technology Corporation, All Rights 
      Reserved 
      <DIV><SPAN class=340450715-31052000></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=340450715-31052000>&nbsp;&nbsp;&nbsp; <FONT 
      color=#ffffff><A href="http://www.dst3.com/email.htm#top">Top of 
      Page</A></FONT></SPAN></FONT></DIV></DIV></TD></TR></TBODY></TABLE>&nbsp;</DIV>&nbsp; 
</BODY></HTML>



From owner-lkcd@oss.sgi.com Tue Jun  6 11:53:25 2000
Received:  by oss.sgi.com id <S42432AbQFFSxP>;
	Tue, 6 Jun 2000 11:53:15 -0700
Received:  by oss.sgi.com id <S42292AbQFFSw4>;
	Tue, 6 Jun 2000 11:52:56 -0700
Received: from deliverator.sgi.com ([204.94.214.10]:23922 "EHLO
        deliverator.sgi.com") by oss.sgi.com with ESMTP id <S42432AbQFFSwj>;
	Tue, 6 Jun 2000 11:52:39 -0700
Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA22530
	for <oss-projects@oss.sgi.com>; Tue, 6 Jun 2000 11:47:43 -0700 (PDT)
	mail_from (trev@sgi.com)
Received: from cromlech.corp.sgi.com (cromlech.corp.sgi.com [150.166.181.83]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA38039 for <@relay.corp.sgi.com:oss-projects@oss.sgi.com>; Tue, 6 Jun 2000 11:52:37 -0700 (PDT)
Received: from sgi.com (localhost [127.0.0.1]) by cromlech.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id LAA46389 for <oss-projects@oss.sgi.com>; Tue, 6 Jun 2000 11:50:17 -0700 (PDT)
Message-ID: <393D47E9.60C4DF94@sgi.com>
Date:   Tue, 06 Jun 2000 11:50:17 -0700
From:   Trevor Hurst <trev@sgi.com>
Organization: SGI
X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5 IP32)
X-Accept-Language: en
MIME-Version: 1.0
To:     oss-projects@oss.sgi.com
Subject: [oss.sgi.com] status update:
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing



 Hello,

This is a status update for oss.sgi.com.

The system has been moved to a different
ip address and the DNS and reverse DNS 
should be fully propagated. We experienced
some problems over this last weekend which
was most likely due to this change. If you
are still having problems connecting please
send an email message to root@oss.sgi.com and
we will help resolve the problems as quickly
as we possibly can.

Thanks and have a great day!

 -- Trev


-- 
Trevor Hurst
Senior Systems Administrator               _ 
Server Operations/Corp. IS       ___  __ _(_)
Silicon Graphics                / __|/ _` | |	
Office Ph: 650.933.6144         \__ \ (_| | |
e-mail: trev@sgi.com            |___/\__, |_|
pager: trev_p@pager.sgi.com          |___/   

--
We are Pentium of Borg. You will be approximated.
Division is futile!  -- Unknown

From owner-lkcd@oss.sgi.com Fri Jun  9 17:36:06 2000
Received:  by oss.sgi.com id <S42225AbQFJAfq>;
	Fri, 9 Jun 2000 17:35:46 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:1013 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42199AbQFJAfN>;
	Fri, 9 Jun 2000 17:35:13 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id SAA06478;
	Fri, 9 Jun 2000 18:35:11 -0600 (MDT)
Message-ID: <XFMail.20000609183513.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <394153F3.5A02BEE5@sgi.com>
Date:   Fri, 09 Jun 2000 18:35:13 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     lkcd@oss.sgi.com, axp-list@redhat.com
Subject: Login problems with 2.3.x
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

I installed 2.3.99pre9 on my Alpha, and now the only way I can log in remotely
is via ssh! The serial console comes up with the login prompt, but refuses my
password (times out after 60 seconds). Once I'm root via ssh, trying to su to
another user has the same problem. This occurs also with the 2.4.0test1 kernel,
but it doesn't with the 2.2.13 kernel. Is there something I need to change
along these lines to get this to work? I did not choose the /dev filesystem
when configuring the 2.3.x kernel.

On 09-Jun-2000 Tom Morano wrote:
> Hi Brian,
> 
> The ia64 work I've been doing has been checked into the 2.3 LKCD tree on
> SourceForge
> (which is CVS controlled). As for development kernel, it depends upon if you
> are 
> talking about the kernel portion of LKCD or LCRASH. With the kernel part,
> much
> of what Matt has done has been checked in. He's been using 2.3.99-pre9 as a
> base.
> With LCRASH, it's a lot more flexible (It runs on both 2.3.50 and
> 2.3.99-pre9).
> And
> yes, you can just copy the /2.3 files over a kernel source tree. The 2.3
> directory
> is relative to /usr/src/linux. 
> 
> Tom

-- 

From owner-lkcd@oss.sgi.com Tue Jun 13 14:27:11 2000
Received:  by oss.sgi.com id <S42306AbQFMV0w>;
	Tue, 13 Jun 2000 14:26:52 -0700
Received: from mail.turbolinux.com ([38.170.88.25]:15108 "EHLO
        mail.turbolinux.com") by oss.sgi.com with ESMTP id <S42289AbQFMV0f>;
	Tue, 13 Jun 2000 14:26:35 -0700
Received: from localhost (yakker@localhost)
	by mail.turbolinux.com (8.9.3/8.9.3) with ESMTP id OAA10786;
	Tue, 13 Jun 2000 14:26:24 -0700
Date:   Tue, 13 Jun 2000 14:26:24 -0700 (PDT)
From:   "Matt D. Robinson" <yakker@turbolinux.com>
To:     Brian Hall <brianwhall@pcisys.net>
cc:     Tom Morano <tjm@sgi.com>, lkcd@oss.sgi.com
Subject: Re: 2.3 problems
In-Reply-To: <XFMail.20000613104208.brianwhall@pcisys.net>
Message-ID: <Pine.LNX.4.21.0006131425400.9511-100000@mail.turbolinux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

I can login and check it out.  It should build, but there may
be problems with the sysctl stuff (it didn't fail for me, but ...)

Can you send me the login method again, Brian?

--Matt

On Tue, 13 Jun 2000, Brian Hall wrote:
|>Well, I copied the 2.3 tree over top of my 2.3.99pre9 tree, and I'm having
|>problems building. I manually added the config_vm_dump menuconfig for Alpha in
|>config.in, but turned it off for now. I am having trouble with sysctl.c and .h-
|>it looks to me like somehow the 2.2 kernel versions of sysctl.* are in the 2.3
|>LKCD CVS tree (depends on lists.h vice list.h) ?
|>
|>I've been trying to fix this as each compiler warning comes up, but one of you
|>might want to check this. Something is not right here. Has anyone verified that
|>the CVS 2.3 tree will build properly when copied over 2.3.99pre9 lately?
|>
|>
|>On 09-Jun-2000 Tom Morano wrote:
|>> Brian Hall wrote:
|>>> 
|>>> Had a teleconference with Compaq's Linux Program Office today. One of the
|>>> things to come out of that was the desire to move forward to the 2.4 kernel
|>>> (possibly back porting the Alpha LKCD support to 2.2 if needed), also move
|>>> this
|>>> direction since there are some corporate politics involved now. Even though
|>>> there have been Compaq contributions to Linux before, this situation is
|>>> different so I am a "test case". Boils down to I expect it to be awhile
|>>> before I
|>>> get "permission" to put my work onto Sourceforge (i.e. merge it with your
|>>> tree). I am not at all happy about this, I was under the impression it would
|>>> be
|>>> much more straightforward. At least everyone here is clear that this is
|>>> GPLed, and the source must be released at least by the time Compaq ships
|>>> product.
|>>> 
|>>> Anyway, Tom, is your ia64 work in the 2.3 tree in CVS? Which development
|>>> kernel
|>>> are you using for that (2.3.x, 2.4.0pre, etc.). Hopefully that same kernel
|>>> rev
|>>> will boot on my Alpha... first thing to check, there. To apply LKCD from CVS
|>>> to
|>>> a fresh kernel, I can just copy the /2.3 files over my kernel directory?
|>>> 
|>> 
|>> Hi Brian,
|>> 
|>> The ia64 work I've been doing has been checked into the 2.3 LKCD tree on
|>> SourceForge
|>> (which is CVS controlled). As for development kernel, it depends upon if you
|>> are 
|>> talking about the kernel portion of LKCD or LCRASH. With the kernel part,
|>> much
|>> of what Matt has done has been checked in. He's been using 2.3.99-pre9 as a
|>> base.
|>> With LCRASH, it's a lot more flexible (It runs on both 2.3.50 and
|>> 2.3.99-pre9).
|>> And
|>> yes, you can just copy the /2.3 files over a kernel source tree. The 2.3
|>> directory
|>> is relative to /usr/src/linux. 
|>> 
|>> Tom
|>
|>-- 
|>


From owner-lkcd@oss.sgi.com Tue Jun 13 16:25:31 2000
Received:  by oss.sgi.com id <S42310AbQFMXZV>;
	Tue, 13 Jun 2000 16:25:21 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:38889 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42289AbQFMXZC>;
	Tue, 13 Jun 2000 16:25:02 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id RAA12116;
	Tue, 13 Jun 2000 17:24:58 -0600 (MDT)
Message-ID: <XFMail.20000613172503.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.21.0006131425400.9511-100000@mail.turbolinux.com>
Date:   Tue, 13 Jun 2000 17:25:03 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     "Matt D. Robinson" <yakker@turbolinux.com>
Subject: Re: 2.3 problems
Cc:     lkcd@oss.sgi.com, Tom Morano <tjm@sgi.com>
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

Get the current IP from my webpage at http://pcisys.net/~brihall/as200

login via ssh to that IP


On 13-Jun-2000 Matt D. Robinson wrote:
> I can login and check it out.  It should build, but there may
> be problems with the sysctl stuff (it didn't fail for me, but ...)
> 
> Can you send me the login method again, Brian?
> 
> --Matt
> 
> On Tue, 13 Jun 2000, Brian Hall wrote:
>|>Well, I copied the 2.3 tree over top of my 2.3.99pre9 tree, and I'm having
>|>problems building. I manually added the config_vm_dump menuconfig for Alpha
>|>in
>|>config.in, but turned it off for now. I am having trouble with sysctl.c and
>|>.h-
>|>it looks to me like somehow the 2.2 kernel versions of sysctl.* are in the
>|>2.3
>|>LKCD CVS tree (depends on lists.h vice list.h) ?
>|>
>|>I've been trying to fix this as each compiler warning comes up, but one of
>|>you
>|>might want to check this. Something is not right here. Has anyone verified
>|>that
>|>the CVS 2.3 tree will build properly when copied over 2.3.99pre9 lately?
>|>
>|>
>|>On 09-Jun-2000 Tom Morano wrote:
>|>> Brian Hall wrote:
>|>>> 
>|>>> Had a teleconference with Compaq's Linux Program Office today. One of the
>|>>> things to come out of that was the desire to move forward to the 2.4
>|>>> kernel
>|>>> (possibly back porting the Alpha LKCD support to 2.2 if needed), also
>|>>> move
>|>>> this
>|>>> direction since there are some corporate politics involved now. Even
>|>>> though
>|>>> there have been Compaq contributions to Linux before, this situation is
>|>>> different so I am a "test case". Boils down to I expect it to be awhile
>|>>> before I
>|>>> get "permission" to put my work onto Sourceforge (i.e. merge it with your
>|>>> tree). I am not at all happy about this, I was under the impression it
>|>>> would
>|>>> be
>|>>> much more straightforward. At least everyone here is clear that this is
>|>>> GPLed, and the source must be released at least by the time Compaq ships
>|>>> product.
>|>>> 
>|>>> Anyway, Tom, is your ia64 work in the 2.3 tree in CVS? Which development
>|>>> kernel
>|>>> are you using for that (2.3.x, 2.4.0pre, etc.). Hopefully that same
>|>>> kernel
>|>>> rev
>|>>> will boot on my Alpha... first thing to check, there. To apply LKCD from
>|>>> CVS
>|>>> to
>|>>> a fresh kernel, I can just copy the /2.3 files over my kernel directory?
>|>>> 
>|>> 
>|>> Hi Brian,
>|>> 
>|>> The ia64 work I've been doing has been checked into the 2.3 LKCD tree on
>|>> SourceForge
>|>> (which is CVS controlled). As for development kernel, it depends upon if
>|>> you
>|>> are 
>|>> talking about the kernel portion of LKCD or LCRASH. With the kernel part,
>|>> much
>|>> of what Matt has done has been checked in. He's been using 2.3.99-pre9 as
>|>> a
>|>> base.
>|>> With LCRASH, it's a lot more flexible (It runs on both 2.3.50 and
>|>> 2.3.99-pre9).
>|>> And
>|>> yes, you can just copy the /2.3 files over a kernel source tree. The 2.3
>|>> directory
>|>> is relative to /usr/src/linux. 
>|>> 
>|>> Tom
>|>
>|>-- 
>|>

-- 

From owner-lkcd@oss.sgi.com Fri Jun 16 10:11:44 2000
Received:  by oss.sgi.com id <S42218AbQFPRLe>;
	Fri, 16 Jun 2000 10:11:34 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:46315 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42181AbQFPRLT>;
	Fri, 16 Jun 2000 10:11:19 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id LAA04039;
	Fri, 16 Jun 2000 11:11:14 -0600 (MDT)
Message-ID: <XFMail.20000616111116.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.21.0006131425400.9511-100000@mail.turbolinux.com>
Date:   Fri, 16 Jun 2000 11:11:16 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     "Matt D. Robinson" <yakker@turbolinux.com>
Subject: Re: 2.3 problems
Cc:     lkcd@oss.sgi.com, Tom Morano <tjm@sgi.com>
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

I am still have trouble with the 2.3 sysctl.c. There are missing definitions
that I can't seem to locate with grep and cscope, like KERN_MSGMNI,
KERN_SEM,KERN_MAX_THREADS, etc. Looked in /usr/src/linux as well as
/usr/include. Recognize these? I'm trying to figure out which include is
missing from sysctl.c.

All I have done is copy the 2.3 CVS tree over the 2.3.99pre9 tree; I'm trying
to get it to compile now, it hasn't worked "out of the box".

On 13-Jun-2000 Matt D. Robinson wrote:
> I can login and check it out.  It should build, but there may
> be problems with the sysctl stuff (it didn't fail for me, but ...)
> 
> Can you send me the login method again, Brian?
> 
> --Matt
> 
> On Tue, 13 Jun 2000, Brian Hall wrote:
>|>Well, I copied the 2.3 tree over top of my 2.3.99pre9 tree, and I'm having
>|>problems building. I manually added the config_vm_dump menuconfig for Alpha
>|>in
>|>config.in, but turned it off for now. I am having trouble with sysctl.c and
>|>.h-
>|>it looks to me like somehow the 2.2 kernel versions of sysctl.* are in the
>|>2.3
>|>LKCD CVS tree (depends on lists.h vice list.h) ?
>|>
>|>I've been trying to fix this as each compiler warning comes up, but one of
>|>you
>|>might want to check this. Something is not right here. Has anyone verified
>|>that
>|>the CVS 2.3 tree will build properly when copied over 2.3.99pre9 lately?
>|>
>|>
>|>On 09-Jun-2000 Tom Morano wrote:
>|>> Brian Hall wrote:
>|>>> 
>|>>> Had a teleconference with Compaq's Linux Program Office today. One of the
>|>>> things to come out of that was the desire to move forward to the 2.4
>|>>> kernel
>|>>> (possibly back porting the Alpha LKCD support to 2.2 if needed), also
>|>>> move
>|>>> this
>|>>> direction since there are some corporate politics involved now. Even
>|>>> though
>|>>> there have been Compaq contributions to Linux before, this situation is
>|>>> different so I am a "test case". Boils down to I expect it to be awhile
>|>>> before I
>|>>> get "permission" to put my work onto Sourceforge (i.e. merge it with your
>|>>> tree). I am not at all happy about this, I was under the impression it
>|>>> would
>|>>> be
>|>>> much more straightforward. At least everyone here is clear that this is
>|>>> GPLed, and the source must be released at least by the time Compaq ships
>|>>> product.
>|>>> 
>|>>> Anyway, Tom, is your ia64 work in the 2.3 tree in CVS? Which development
>|>>> kernel
>|>>> are you using for that (2.3.x, 2.4.0pre, etc.). Hopefully that same
>|>>> kernel
>|>>> rev
>|>>> will boot on my Alpha... first thing to check, there. To apply LKCD from
>|>>> CVS
>|>>> to
>|>>> a fresh kernel, I can just copy the /2.3 files over my kernel directory?
>|>>> 
>|>> 
>|>> Hi Brian,
>|>> 
>|>> The ia64 work I've been doing has been checked into the 2.3 LKCD tree on
>|>> SourceForge
>|>> (which is CVS controlled). As for development kernel, it depends upon if
>|>> you
>|>> are 
>|>> talking about the kernel portion of LKCD or LCRASH. With the kernel part,
>|>> much
>|>> of what Matt has done has been checked in. He's been using 2.3.99-pre9 as
>|>> a
>|>> base.
>|>> With LCRASH, it's a lot more flexible (It runs on both 2.3.50 and
>|>> 2.3.99-pre9).
>|>> And
>|>> yes, you can just copy the /2.3 files over a kernel source tree. The 2.3
>|>> directory
>|>> is relative to /usr/src/linux. 
>|>> 
>|>> Tom
>|>
>|>-- 
>|>

-- 

From owner-lkcd@oss.sgi.com Mon Jun 19 09:37:33 2000
Received:  by oss.sgi.com id <S42232AbQFSQhX>;
	Mon, 19 Jun 2000 09:37:23 -0700
Received: from pneumatic-tube.sgi.com ([204.94.214.22]:15671 "EHLO
        pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP
	id <S42186AbQFSQhG>; Mon, 19 Jun 2000 09:37:06 -0700
Received: from localhost.localdomain (root@breakwater.cray.com [128.162.186.95]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA02848
	for <lkcd@oss.sgi.com>; Mon, 19 Jun 2000 09:42:14 -0700 (PDT)
	mail_from (tds@sgi.com)
Received: from sgi.com (IDENT:tds@localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA14600
	for <lkcd@oss.sgi.com>; Mon, 19 Jun 2000 11:44:06 -0500
Message-ID: <394E4DD3.9CEE2E9@sgi.com>
Date:   Mon, 19 Jun 2000 11:44:04 -0500
From:   tds <tds@sgi.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-2SGI_20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To:     lkcd@oss.sgi.com
Subject: Forcing a kernel dump from the keyboard
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

LKCD,

I've got a quick question about LKCD.  Is it possible to force a panic
from the keyboard?  I don't
think the alt-sysrequest "magic key" can generate a panic, but maybe you
know another way.

I'm trying to get a kernel dump from a 4-headed SGI-1400 system which
frequently hangs up while
we're running MPI applications on it.  I can ping  the box, but not
telnet (I get "connected to...",
but no login prompt.)  On the console, I get a login prompt, but never a
password prompt.

So, the keyboard is working, but not much else.   I cannot run the
sys_setprioiry() kludge example shown
in the LKCD FAQ.   I'd love to force a panic from the keyboard so
I could get a dump to look at, but so far no luck.

Any help appreciated,
Tim Sirianni
MPI, SGI


From owner-lkcd@oss.sgi.com Mon Jun 19 09:44:04 2000
Received:  by oss.sgi.com id <S42240AbQFSQnx>;
	Mon, 19 Jun 2000 09:43:53 -0700
Received: from mail.missioncriticallinux.com ([208.51.139.18]:3855 "EHLO
        postal.lowell.mclinux.com") by oss.sgi.com with ESMTP
	id <S42186AbQFSQnd>; Mon, 19 Jun 2000 09:43:33 -0700
Received: from moyer.lowell.mclinux.com (root@moyer.lowell.mclinux.com [10.1.8.50])
	by postal.lowell.mclinux.com (8.9.3/8.9.3) with ESMTP id MAA24234;
	Mon, 19 Jun 2000 12:42:59 -0400
Received: (from moyer@localhost)
	by moyer.lowell.mclinux.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id MAA25336;
	Mon, 19 Jun 2000 12:41:10 -0500
X-Authentication-Warning: moyer.lowell.mclinux.com: moyer set sender to moyer@mclinux.com using -f
From:   Jeff Moyer <moyer@mclinux.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14670.23350.633527.956130@moyer.lowell.mclinux.com>
Date:   Mon, 19 Jun 2000 12:41:10 -0500 (EST)
To:     tds <tds@sgi.com>
Cc:     lkcd@oss.sgi.com
Subject: Forcing a kernel dump from the keyboard
In-Reply-To: <394E4DD3.9CEE2E9@sgi.com>
References: <394E4DD3.9CEE2E9@sgi.com>
X-Mailer: VM 6.75 under Emacs 20.4.1
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

==> Regarding Forcing a kernel dump from the keyboard; tds <tds@sgi.com> adds:

tds> LKCD, I've got a quick question about LKCD.  Is it possible to force a
tds> panic from the keyboard?  I don't think the alt-sysrequest "magic key"
tds> can generate a panic, but maybe you know another way.

    It is trivial to implement such a mechanism via Magic Sysrq.  For an
    example, you can check out
    http://www.missioncriticallinux.com/downloads.  You're looking for the
    in memory core dump patch.  I'm not sure how lkcd will handle taking a
    dump at interrupt level (using Magic Sysrq is in the context of an
    interrupt), but you can give it a try.

    Once you apply the kernel patch, the file you want to look at is
    drivers/char/sysrq.c.

-Jeff

From owner-lkcd@oss.sgi.com Mon Jun 19 13:20:35 2000
Received:  by oss.sgi.com id <S42294AbQFSUUQ>;
	Mon, 19 Jun 2000 13:20:16 -0700
Received: from pneumatic-tube.sgi.com ([204.94.214.22]:62568 "EHLO
        pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP
	id <S42240AbQFSUUG>; Mon, 19 Jun 2000 13:20:06 -0700
Received: from ledzep.cray.com (ledzep.cray.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA04741
	for <lkcd@oss.sgi.com>; Mon, 19 Jun 2000 13:25:14 -0700 (PDT)
	mail_from (tds@sgi.com)
Received: from daisy-e185.americas.sgi.com (daisy.cray.com [128.162.185.214]) by ledzep.cray.com (SGI-SGI-8.9.3/craymail-smart-nospam1.0) with ESMTP id PAA78179; Mon, 19 Jun 2000 15:18:48 -0500 (CDT)
Received: from fsgi972.americas.sgi.com (fsgi972.americas.sgi.com [128.162.186.94]) by daisy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.6) with ESMTP id PAA53393; Mon, 19 Jun 2000 15:18:49 -0500 (CDT)
From:   Timothy Sirianni <tds@sgi.com>
Received: by fsgi972.americas.sgi.com (980427.SGI.8.8.8/SGI-client-1.6c) id PAA07454; Mon, 19 Jun 2000 15:18:49 -0500 (CDT)
Message-Id: <200006192018.PAA07454@fsgi972.americas.sgi.com>
Date:   Mon, 19 Jun 2000 15:18:49 -0500 (CDT)
To:     Jeff Moyer <moyer@mclinux.com>
Subject: Re:  Forcing a kernel dump from the keyboard
Cc:     lkcd@oss.sgi.com
References: <394E4DD3.9CEE2E9@sgi.com>
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

Jeff,

Thanks for the pointer.  I'm putting a call to panic() into 
drivers/char/sysrq.c to see if that does what I need.

Regards,
Tim

> From moyer@mclinux.com  Mon Jun 19 11:43:57 2000
> Cc: lkcd@oss.sgi.com
> 
> ==> Regarding Forcing a kernel dump from the keyboard; tds <tds@sgi.com> adds:
> 
> tds> LKCD, I've got a quick question about LKCD.  Is it possible to force a
> tds> panic from the keyboard?  I don't think the alt-sysrequest "magic key"
> tds> can generate a panic, but maybe you know another way.
> 
>     It is trivial to implement such a mechanism via Magic Sysrq.  For an
>     example, you can check out
>     http://www.missioncriticallinux.com/downloads.  You're looking for the
>     in memory core dump patch.  I'm not sure how lkcd will handle taking a
>     dump at interrupt level (using Magic Sysrq is in the context of an
>     interrupt), but you can give it a try.
> 
>     Once you apply the kernel patch, the file you want to look at is
>     drivers/char/sysrq.c.
> 
> -Jeff

From owner-lkcd@oss.sgi.com Mon Jun 19 15:29:26 2000
Received:  by oss.sgi.com id <S42299AbQFSW3Q>;
	Mon, 19 Jun 2000 15:29:16 -0700
Received: from jerry.pcisys.net ([207.76.102.251]:33274 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42239AbQFSW27>;
	Mon, 19 Jun 2000 15:28:59 -0700
Received: from localhost.localdomain (cosdsl184.pci2.cos.pcisys.net [216.229.43.184])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id QAA11491;
	Mon, 19 Jun 2000 16:28:53 -0600 (MDT)
Message-ID: <XFMail.20000619162829.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.20000613172503.brianwhall@pcisys.net>
Date:   Mon, 19 Jun 2000 16:28:29 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     "Matt D. Robinson" <yakker@turbolinux.com>
Subject: Re: 2.3 problems
Cc:     lkcd@oss.sgi.com
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

Have you had a chance to take a look at this?

On 13-Jun-2000 Brian Hall wrote:
> Get the current IP from my webpage at http://pcisys.net/~brihall/as200
> 
> login via ssh to that IP
> 
> 
> On 13-Jun-2000 Matt D. Robinson wrote:
>> I can login and check it out.  It should build, but there may
>> be problems with the sysctl stuff (it didn't fail for me, but ...)
>> 
>> Can you send me the login method again, Brian?
>> 
>> --Matt
>> 
>> On Tue, 13 Jun 2000, Brian Hall wrote:
>>|>Well, I copied the 2.3 tree over top of my 2.3.99pre9 tree, and I'm having
>>|>problems building. I manually added the config_vm_dump menuconfig for Alpha
>>|>in
>>|>config.in, but turned it off for now. I am having trouble with sysctl.c and
>>|>.h-
>>|>it looks to me like somehow the 2.2 kernel versions of sysctl.* are in the
>>|>2.3
>>|>LKCD CVS tree (depends on lists.h vice list.h) ?
>>|>
>>|>I've been trying to fix this as each compiler warning comes up, but one of
>>|>you
>>|>might want to check this. Something is not right here. Has anyone verified
>>|>that
>>|>the CVS 2.3 tree will build properly when copied over 2.3.99pre9 lately?
>>|>
>>|>
>>|>On 09-Jun-2000 Tom Morano wrote:
>>|>> Brian Hall wrote:
>>|>>> 
>>|>>> Had a teleconference with Compaq's Linux Program Office today. One of
>>|>>> the
>>|>>> things to come out of that was the desire to move forward to the 2.4
>>|>>> kernel
>>|>>> (possibly back porting the Alpha LKCD support to 2.2 if needed), also
>>|>>> move
>>|>>> this
>>|>>> direction since there are some corporate politics involved now. Even
>>|>>> though
>>|>>> there have been Compaq contributions to Linux before, this situation is
>>|>>> different so I am a "test case". Boils down to I expect it to be awhile
>>|>>> before I
>>|>>> get "permission" to put my work onto Sourceforge (i.e. merge it with
>>|>>> your
>>|>>> tree). I am not at all happy about this, I was under the impression it
>>|>>> would
>>|>>> be
>>|>>> much more straightforward. At least everyone here is clear that this is
>>|>>> GPLed, and the source must be released at least by the time Compaq ships
>>|>>> product.
>>|>>> 
>>|>>> Anyway, Tom, is your ia64 work in the 2.3 tree in CVS? Which development
>>|>>> kernel
>>|>>> are you using for that (2.3.x, 2.4.0pre, etc.). Hopefully that same
>>|>>> kernel
>>|>>> rev
>>|>>> will boot on my Alpha... first thing to check, there. To apply LKCD from
>>|>>> CVS
>>|>>> to
>>|>>> a fresh kernel, I can just copy the /2.3 files over my kernel directory?
>>|>>> 
>>|>> 
>>|>> Hi Brian,
>>|>> 
>>|>> The ia64 work I've been doing has been checked into the 2.3 LKCD tree on
>>|>> SourceForge
>>|>> (which is CVS controlled). As for development kernel, it depends upon if
>>|>> you
>>|>> are 
>>|>> talking about the kernel portion of LKCD or LCRASH. With the kernel part,
>>|>> much
>>|>> of what Matt has done has been checked in. He's been using 2.3.99-pre9 as
>>|>> a
>>|>> base.
>>|>> With LCRASH, it's a lot more flexible (It runs on both 2.3.50 and
>>|>> 2.3.99-pre9).
>>|>> And
>>|>> yes, you can just copy the /2.3 files over a kernel source tree. The 2.3
>>|>> directory
>>|>> is relative to /usr/src/linux. 
>>|>> 
>>|>> Tom
>>|>
>>|>-- 
>>|>
> 
> -- 

-- 

From owner-lkcd@oss.sgi.com Mon Jun 19 20:07:57 2000
Received:  by oss.sgi.com id <S42261AbQFTDHs>;
	Mon, 19 Jun 2000 20:07:48 -0700
Received: from mail.turbolinux.com ([38.170.88.25]:6153 "EHLO
        mail.turbolinux.com") by oss.sgi.com with ESMTP id <S42229AbQFTDHY>;
	Mon, 19 Jun 2000 20:07:24 -0700
Received: from localhost (yakker@localhost)
	by mail.turbolinux.com (8.9.3/8.9.3) with ESMTP id UAA26305;
	Mon, 19 Jun 2000 20:07:22 -0700
Date:   Mon, 19 Jun 2000 20:07:22 -0700 (PDT)
From:   "Matt D. Robinson" <yakker@turbolinux.com>
To:     Brian Hall <brianwhall@pcisys.net>
cc:     lkcd@oss.sgi.com
Subject: Re: 2.3 problems
In-Reply-To: <XFMail.20000619162829.brianwhall@pcisys.net>
Message-ID: <Pine.LNX.4.21.0006191530050.9293-100000@mail.turbolinux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

I'm trying to get my own personal DS10 booting TL 6.0 right now.
As soon as that's running, I'll have my own system to use to play
around with.  I just got the system this afternoon, and I'm doing
what I can in the meantime to get it running.

--Matt

On Mon, 19 Jun 2000, Brian Hall wrote:
|>Have you had a chance to take a look at this?


From owner-lkcd@oss.sgi.com Tue Jun 27 13:30:35 2000
Received:  by oss.sgi.com id <S42208AbQF0Ua0>;
	Tue, 27 Jun 2000 13:30:26 -0700
Received: from [207.76.102.251] ([207.76.102.251]:43703 "EHLO jerry.pcisys.net")
	by oss.sgi.com with ESMTP id <S42191AbQF0UaG>;
	Tue, 27 Jun 2000 13:30:06 -0700
Received: from localhost.localdomain (csd107.cos.pcisys.net [207.204.7.107])
	by jerry.pcisys.net (8.9.3/8.9.3) with ESMTP id OAA22862;
	Tue, 27 Jun 2000 14:30:10 -0600 (MDT)
Message-ID: <XFMail.20000627143013.brianwhall@pcisys.net>
X-Mailer: XFMail 1.4.4 on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.21.0006191530050.9293-100000@mail.turbolinux.com>
Date:   Tue, 27 Jun 2000 14:30:13 -0600 (MDT)
Reply-To: Brian Hall <brianwhall@pcisys.net>
Organization: Compaq
From:   Brian Hall <brianwhall@pcisys.net>
To:     "Matt D. Robinson" <yakker@turbolinux.com>
Subject: status (was Re: 2.3 problems)
Cc:     lkcd@oss.sgi.com
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

To try to make some progress, I switched back to my 2.2 tree, and copied over
the arch-independent stuff from lkcd-2.3 CVS to pick up most of the 64-bit
cleanliness. After some minor adjustments and commenting out some things
temporarily, I got lcrash to compile again. Didn't help my problems, though,
lcrash still dies on startup on cmd #3 (as before). I must be missing something
obvious.

I haven't yet fixed the disassembly routines for Alpha yet, I'm still using the
ones for i386. This will have to be fixed eventually, but could that be causing
my problems at this point? My thought was that I'm not getting that far, so the
problem must be elsewhere. My expectation (if lcrash would come up) is that I
could issue some simple commands, show registers, etc. but I would run into
trouble when I tried to print stack traces and so forth.

BTW, let me know if you need some help getting that DS10 to run Linux.

On 20-Jun-2000 Matt D. Robinson wrote:
> I'm trying to get my own personal DS10 booting TL 6.0 right now.
> As soon as that's running, I'll have my own system to use to play
> around with.  I just got the system this afternoon, and I'm doing
> what I can in the meantime to get it running.
> 
> --Matt
> 
> On Mon, 19 Jun 2000, Brian Hall wrote:
>|>Have you had a chance to take a look at this?

-- 

From owner-lkcd@oss.sgi.com Wed Jun 28 07:35:22 2000
Received:  by oss.sgi.com id <S42209AbQF1OfM>;
	Wed, 28 Jun 2000 07:35:12 -0700
Received: from e32.co.us.ibm.com ([32.97.110.130]:65466 "EHLO
        e32.bld.us.ibm.com") by oss.sgi.com with ESMTP id <S42201AbQF1Oez>;
	Wed, 28 Jun 2000 07:34:55 -0700
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.132.205])
	by e32.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id KAA62024
	for <lkcd@oss.sgi.com>; Wed, 28 Jun 2000 10:32:28 -0400
From:   washer@us.ibm.com
Received: from d53mta05h.boulder.ibm.com (d53mta05h.boulder.ibm.com [9.99.142.5])
	by westrelay02.boulder.ibm.com (8.8.8m3/NCO v4.9) with SMTP id IAA65610
	for <lkcd@oss.sgi.com>; Wed, 28 Jun 2000 08:35:03 -0600
Received: by d53mta05h.boulder.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id 8725690C.00501AF5 ; Wed, 28 Jun 2000 08:34:57 -0600
X-Lotus-FromDomain: IBMUS
To:     lkcd@oss.sgi.com
Message-ID: <8725690C.005019EE.00@d53mta05h.boulder.ibm.com>
Date:   Wed, 28 Jun 2000 08:34:53 -0600
Subject: Various comments and questions
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing



Hello,

I'm new to this group, and fairly new to linux, but have been doing crash
dump analysis under UNIX(tm) almost full time for the past 10 years.. I'm
quite happy to find that this effort is under way. I'll do what I can to
contribute to the effort.  Now, a few questions that arose while reading
the FAQ.


The FAQ says that SCSI is required because no raw-io driver exists for IDE
and we don't want to use the buffer cache.  I agree that we don't want to
go through the buffer cache... however..  It seems likely to me that the
existing swap IO does not use the buffer cache. Further, since we are using
a swap volume for the storage of the dump... couldn't we just hi-jack the
swap IO mechanisn? Isn't that doing direct IO to disk? Wouldn't that allow
dumps to ide ( or whatever )?

The FAQ warns that you need to recompile lcrash when you make changes to
the kernel.  I'm not sure I understand why lcrash would have such
dependencies. Can't it get what information it needs from the kernel
elf/dwarf information? What is compiled into lcrash that would change with
kernel builds. Does this dependency imply that a remote system/user would
have to send in his/her lcrash along with the dump, for someone else
(kernel developer) to be able to 'read' the dump?


The FAQ says that all of memory is dumped, because there is no way to
distinguish what the memory is used for ( user/kernel/free/etc ). Again,
I'm new to linux, but in the UNIX(tm) world, the mmap[] datastructure
accounts for all physical memory, and records the current 'owner' or 'use'
of each page.  Is there no equivalent data structure under linux? ( yeah,
I'll go read the source, slowly)


thanks for reading this far. I look forward to your response

 - jim



From owner-lkcd@oss.sgi.com Thu Jun 29 07:33:51 2000
Received:  by oss.sgi.com id <S42200AbQF2Odb>;
	Thu, 29 Jun 2000 07:33:31 -0700
Received: from mail.turbolinux.com ([38.170.88.25]:13582 "EHLO
        mail.turbolinux.com") by oss.sgi.com with ESMTP id <S42194AbQF2Od2>;
	Thu, 29 Jun 2000 07:33:28 -0700
Received: from localhost (yakker@localhost)
	by mail.turbolinux.com (8.9.3/8.9.3) with ESMTP id HAA15402
	for <lkcd@oss.sgi.com>; Thu, 29 Jun 2000 07:33:37 -0700
Date:   Thu, 29 Jun 2000 07:33:37 -0700 (PDT)
From:   "Matt D. Robinson" <yakker@turbolinux.com>
To:     lkcd@oss.sgi.com
Subject: LKCD for 2.3: Update
Message-ID: <Pine.LNX.4.21.0006290730300.15272-100000@mail.turbolinux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-lkcd@oss.sgi.com
Precedence: bulk
Return-Path: <owner-lkcd@oss.sgi.com>
X-Orcpt: rfc822;lkcd-outgoing

Hi, all.  I have a patch available for the 2.3 tree, although it
needs some testing.  If people are willing to try it out, crash
their systems, run 'lcrash', etc., with it, and let myself and
Tom know how well it is or is not working, I can send the patch
to people individually.

The code has changed a little; we now use kiobufs directly, and
we don't require the raw I/O patches from SGI.  We also work on
IDE disks, which is really nice for IA32 systems.

I'm working on the Alpha version, and trying to debug one problem
I have currently in the code (compression turned on seems to cause
occasional data offset problems in the dump).  But with that
excluded, there is a patch ready for test.

Let me know what you think.

--Matt