From owner-linux-origin@oss.sgi.com Wed Aug 9 15:35:45 2000 Received: by oss.sgi.com id ; Wed, 9 Aug 2000 15:35:36 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:29994 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 9 Aug 2000 15:35:24 -0700 Received: from google.engr.sgi.com (google.engr.sgi.com [163.154.10.145]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA28141; Wed, 9 Aug 2000 15:27:20 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id PAA51876; Wed, 9 Aug 2000 15:33:38 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008092233.PAA51876@google.engr.sgi.com> Subject: Re: CVS Update@oss.sgi.com: linux To: ralf@oss.sgi.com (Ralf Baechle) Date: Wed, 9 Aug 2000 15:33:38 -0700 (PDT) Cc: linux-origin@oss.sgi.com In-Reply-To: <20000810002624.C11585@bacchus.dhis.org> from "Ralf Baechle" at Aug 10, 2000 12:26:24 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing > > On Wed, Aug 09, 2000 at 03:08:55PM -0700, Kanoj Sarcar wrote: > > > > CVSROOT: /home/pub/cvs > > > Module name: linux > > > Changes by: ralf@oss.sgi.com 00/08/09 15:04:42 > > > > > > Modified files: > > > include/asm-mips: stat.h > > > include/asm-mips64: stat.h > > > > > > Log message: > > > Kill st_fstype member. > > > > > > > > > > Will any of the stat.h changes break my current disk? > > Only if you are using glibc 2.2. But that was broken before ... > > Ralf > How would I find out whether I am using glibc 2.2? What if I am using something older? Do you have a _tested_ glibc that I can use to work with the changed stat.h? Kanoj From owner-linux-origin@oss.sgi.com Wed Aug 9 15:51:46 2000 Received: by oss.sgi.com id ; Wed, 9 Aug 2000 15:51:36 -0700 Received: from u-22.karlsruhe.ipdial.viaginterkom.de ([62.180.19.22]:49669 "EHLO u-22.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Wed, 9 Aug 2000 15:51:19 -0700 Received: (ralf@lappi) by lappi.waldorf-gmbh.de id ; Thu, 10 Aug 2000 00:50:27 +0200 Date: Thu, 10 Aug 2000 00:50:27 +0200 From: Ralf Baechle To: Kanoj Sarcar Cc: linux-origin@oss.sgi.com Subject: Re: CVS Update@oss.sgi.com: linux Message-ID: <20000810005027.D11585@bacchus.dhis.org> References: <20000810002624.C11585@bacchus.dhis.org> <200008092233.PAA51876@google.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008092233.PAA51876@google.engr.sgi.com>; from kanoj@google.engr.sgi.com on Wed, Aug 09, 2000 at 03:33:38PM -0700 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Wed, Aug 09, 2000 at 03:33:38PM -0700, Kanoj Sarcar wrote: > How would I find out whether I am using glibc 2.2? What if I am > using something older? Do you have a _tested_ glibc that I can use > to work with the changed stat.h? [ralf@lappi ralf]$ ls -l /lib/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 27 12:05 /lib/libc.so.6 -> libc-2.1.3.so* -> this system is using glibc 2.1.3. You should be using some 2.0.x version. If you're using some 2.1 or 2.2 version then mail me again. Ralf From owner-linux-origin@oss.sgi.com Wed Aug 9 16:04:16 2000 Received: by oss.sgi.com id ; Wed, 9 Aug 2000 16:04:08 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:4914 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 9 Aug 2000 16:03:31 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA02051; Wed, 9 Aug 2000 15:55:22 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: from google.engr.sgi.com ([163.154.10.145]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id QAA34505; Wed, 9 Aug 2000 16:02:25 -0700 (PDT) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id PAA23735; Wed, 9 Aug 2000 15:59:55 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008092259.PAA23735@google.engr.sgi.com> Subject: Re: CVS Update@oss.sgi.com: linux To: ralf@oss.sgi.com (Ralf Baechle) Date: Wed, 9 Aug 2000 15:59:55 -0700 (PDT) Cc: linux-origin@oss.sgi.com In-Reply-To: <20000810005027.D11585@bacchus.dhis.org> from "Ralf Baechle" at Aug 10, 2000 12:50:27 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing > > On Wed, Aug 09, 2000 at 03:33:38PM -0700, Kanoj Sarcar wrote: > > > How would I find out whether I am using glibc 2.2? What if I am > > using something older? Do you have a _tested_ glibc that I can use > > to work with the changed stat.h? > > [ralf@lappi ralf]$ ls -l /lib/libc.so.6 > lrwxrwxrwx 1 root root 13 Jul 27 12:05 /lib/libc.so.6 -> libc-2.1.3.so* > > -> this system is using glibc 2.1.3. > > You should be using some 2.0.x version. If you're using some 2.1 or 2.2 > version then mail me again. > > Ralf > On one system (posix0) [root@posix0-41 /lib]# ls -l /lib/libc.so* lrwxrwxrwx 1 root root 12 Jun 13 18:52 /lib/libc.so.6 -> libc.so.6.VJ -rwxr-xr-x 1 root root 3343805 Feb 10 2000 /lib/libc.so.6.ORIG -rwxr-xr-x 1 root root 3137841 Feb 10 2000 /lib/libc.so.6.VJ On the other (trillium) bash# ls -l /lib/libc.so* lrwxrwxrwx 1 root root 13 Jun 15 22:19 /lib/libc.so.6 -> libc-2.0.6.so -rwxr-xr-x 1 root root 3343805 Feb 10 2000 /lib/libc.so.6.ORIG -rwxr-xr-x 1 root root 3137841 Feb 10 2000 /lib/libc.so.6.VJ bash# ls -l /lib/libc-2.0.6.so -rwxr-xr-x 1 root root 3573525 Jun 15 22:10 /lib/libc-2.0.6.so Hence, it looks like I am using some 2.0.6 version. I should be okay then? Kanoj From owner-linux-origin@oss.sgi.com Wed Aug 9 16:11:45 2000 Received: by oss.sgi.com id ; Wed, 9 Aug 2000 16:11:38 -0700 Received: from u-22.karlsruhe.ipdial.viaginterkom.de ([62.180.19.22]:49925 "EHLO u-22.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Wed, 9 Aug 2000 16:11:21 -0700 Received: (ralf@lappi) by lappi.waldorf-gmbh.de id ; Thu, 10 Aug 2000 01:10:26 +0200 Date: Thu, 10 Aug 2000 01:10:26 +0200 From: Ralf Baechle To: Kanoj Sarcar Cc: linux-origin@oss.sgi.com Subject: Re: CVS Update@oss.sgi.com: linux Message-ID: <20000810011026.A13580@bacchus.dhis.org> References: <20000810005027.D11585@bacchus.dhis.org> <200008092259.PAA23735@google.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008092259.PAA23735@google.engr.sgi.com>; from kanoj@google.engr.sgi.com on Wed, Aug 09, 2000 at 03:59:55PM -0700 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Wed, Aug 09, 2000 at 03:59:55PM -0700, Kanoj Sarcar wrote: > Hence, it looks like I am using some 2.0.6 version. I should be okay then? Yes. Glibc 2.2 should also be ok but only for non-LFS code. Ralf From owner-linux-origin@oss.sgi.com Thu Aug 10 11:03:28 2000 Received: by oss.sgi.com id ; Thu, 10 Aug 2000 11:03:18 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:28464 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 10 Aug 2000 11:02:46 -0700 Received: from google.engr.sgi.com (google.engr.sgi.com [163.154.10.145]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA08303 for ; Thu, 10 Aug 2000 11:08:19 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id LAA50412 for linux-origin@oss.sgi.com; Thu, 10 Aug 2000 11:01:00 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008101801.LAA50412@google.engr.sgi.com> Subject: ethernet To: linux-origin@oss.sgi.com Date: Thu, 10 Aug 2000 11:01:00 -0700 (PDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Ralf, Not that it is bothering me greatly right now (at least not more than the RX overflow messages), but with late kernels, I think I sometimes have trouble telneting/pinging mips64 machines. Things seem to get fixed though once I log in to the mips64 machine, and ping the other one from it, that seems to clean up the line. Recent developement. Kanoj From owner-linux-origin@oss.sgi.com Thu Aug 10 15:56:28 2000 Received: by oss.sgi.com id ; Thu, 10 Aug 2000 15:56:19 -0700 Received: from ppp0.ocs.com.au ([203.34.97.3]:64517 "HELO mail.ocs.com.au") by oss.sgi.com with SMTP id ; Thu, 10 Aug 2000 15:55:40 -0700 Received: (qmail 10730 invoked from network); 10 Aug 2000 22:54:58 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 10 Aug 2000 22:54:58 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Kanoj Sarcar cc: linux-origin@oss.sgi.com Subject: Re: ethernet In-reply-to: Your message of "Thu, 10 Aug 2000 11:01:00 MST." <200008101801.LAA50412@google.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Aug 2000 08:54:56 +1000 Message-ID: <11989.965948096@ocs3.ocs-net> Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Thu, 10 Aug 2000 11:01:00 -0700 (PDT), Kanoj Sarcar wrote: >Not that it is bothering me greatly right now (at least not more than >the RX overflow messages), but with late kernels, I think I sometimes >have trouble telneting/pinging mips64 machines. Things seem to get fixed >though once I log in to the mips64 machine, and ping the other one from >it, that seems to clean up the line. Recent developement. The symptoms sound like the ARP reply is getting lost. I have seen this on some network cards (especially NetGear FA310TX) where the RX data is much longer than it should be and is split over multiple input buffers which confuses the kernel. When you get this symptom, check arp -an on both machines. I expect that the mips64 box will have the hardware address of the source machine but the other machine will be missing the hardware address of the mips64 box. Doing the traffic in reverse automatically fills in the hardware address of the machine that the arp request came from. This tends to hide the RX overrun problem. From owner-linux-origin@oss.sgi.com Thu Aug 10 16:59:58 2000 Received: by oss.sgi.com id ; Thu, 10 Aug 2000 16:59:41 -0700 Received: from u-213.karlsruhe.ipdial.viaginterkom.de ([62.180.21.213]:9988 "EHLO u-213.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Thu, 10 Aug 2000 16:59:17 -0700 Received: (ralf@lappi) by lappi.waldorf-gmbh.de id ; Fri, 11 Aug 2000 01:51:14 +0200 Date: Fri, 11 Aug 2000 01:51:14 +0200 From: Ralf Baechle To: Keith Owens Cc: Kanoj Sarcar , linux-origin@oss.sgi.com Subject: Re: ethernet Message-ID: <20000811015114.C2199@bacchus.dhis.org> References: <200008101801.LAA50412@google.engr.sgi.com> <11989.965948096@ocs3.ocs-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <11989.965948096@ocs3.ocs-net>; from kaos@ocs.com.au on Fri, Aug 11, 2000 at 08:54:56AM +1000 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Fri, Aug 11, 2000 at 08:54:56AM +1000, Keith Owens wrote: > Doing the traffic in reverse automatically fills in the hardware > address of the machine that the arp request came from. This tends to > hide the RX overrun problem. And indeed we tend to have RX overrun problem with this driver. I can easily blow my Origin off the net by just floodpinging it for a few seconds. In such a case the IOC3 will deactivate RX and signal an interrupt. The driver handles this by trying to reinitialize everything but somehow this often doesn't work. It also print a message, so you may want to check syslog / dmesg for kernel messages. I've once again starred for a while on the driver code but nothing obvious. Ralf From owner-linux-origin@oss.sgi.com Thu Aug 10 19:43:39 2000 Received: by oss.sgi.com id ; Thu, 10 Aug 2000 19:43:20 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:23321 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 10 Aug 2000 19:42:54 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id TAA22296; Thu, 10 Aug 2000 19:34:49 -0700 (PDT) mail_from (dagum@barrel.engr.sgi.com) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id TAA03418; Thu, 10 Aug 2000 19:41:53 -0700 (PDT) Received: from barrel.engr.sgi.com (barrel.engr.sgi.com [163.154.5.63]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id TAA62550; Thu, 10 Aug 2000 19:40:21 -0700 (PDT) mail_from (dagum@barrel.engr.sgi.com) Received: (from dagum@localhost) by barrel.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA20056; Thu, 10 Aug 2000 19:38:47 -0700 Date: Thu, 10 Aug 2000 19:38:47 -0700 From: dagum@barrel.engr.sgi.com (Leo Dagum) Message-Id: <200008110238.TAA20056@barrel.engr.sgi.com> To: Keith Owens , Ralf Baechle Subject: Re: ethernet Cc: linux-origin@oss.sgi.com, Kanoj Sarcar References: <200008101801.LAA50412@google.engr.sgi.com> <11989.965948096@ocs3.ocs-net> Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing > On Fri, Aug 11, 2000 at 08:54:56AM +1000, Keith Owens wrote: > > > Doing the traffic in reverse automatically fills in the hardware > > address of the machine that the arp request came from. This tends to > > hide the RX overrun problem. > > And indeed we tend to have RX overrun problem with this driver. I can > easily blow my Origin off the net by just floodpinging it for a few > seconds. In such a case the IOC3 will deactivate RX and signal an > interrupt. The driver handles this by trying to reinitialize everything > but somehow this often doesn't work. When the driver reinitializes everything, that includes the dma buffers. So if, e.g. the driver is also xmit'ing a packet when it gets the error, the xmit will fail and panic the system because the dma buffer disappears between getting set up and getting xmitted. Not sure if that's the problem you see, but I've certainly seen that happen. - leo > It also print a message, so you > may want to check syslog / dmesg for kernel messages. I've once again > starred for a while on the driver code but nothing obvious. > > Ralf > Leo Dagum SGI Mountain View, CA 94043 (650-933-2179) From owner-linux-origin@oss.sgi.com Thu Aug 10 20:42:10 2000 Received: by oss.sgi.com id ; Thu, 10 Aug 2000 20:42:00 -0700 Received: from u-91.karlsruhe.ipdial.viaginterkom.de ([62.180.10.91]:15108 "EHLO u-91.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Thu, 10 Aug 2000 20:41:30 -0700 Received: (ralf@lappi) by lappi.waldorf-gmbh.de id ; Fri, 11 Aug 2000 05:40:34 +0200 Date: Fri, 11 Aug 2000 05:40:34 +0200 From: Ralf Baechle To: Leo Dagum Cc: Keith Owens , linux-origin@oss.sgi.com, Kanoj Sarcar Subject: Re: ethernet Message-ID: <20000811054034.B2480@bacchus.dhis.org> References: <200008101801.LAA50412@google.engr.sgi.com> <11989.965948096@ocs3.ocs-net> <200008110238.TAA20056@barrel.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008110238.TAA20056@barrel.engr.sgi.com>; from dagum@barrel.engr.sgi.com on Thu, Aug 10, 2000 at 07:38:47PM -0700 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Thu, Aug 10, 2000 at 07:38:47PM -0700, Leo Dagum wrote: > > > Doing the traffic in reverse automatically fills in the hardware > > > address of the machine that the arp request came from. This tends to > > > hide the RX overrun problem. > > > > And indeed we tend to have RX overrun problem with this driver. I can > > easily blow my Origin off the net by just floodpinging it for a few > > seconds. In such a case the IOC3 will deactivate RX and signal an > > interrupt. The driver handles this by trying to reinitialize everything > > but somehow this often doesn't work. > > When the driver reinitializes everything, that includes the dma buffers. > So if, e.g. the driver is also xmit'ing a packet when it gets the > error, the xmit will fail and panic the system because the dma > buffer disappears between getting set up and getting xmitted. > > Not sure if that's the problem you see, but I've certainly seen > that happen. That's definately not what's going on in this case. Ralf From owner-linux-origin@oss.sgi.com Thu Aug 24 10:27:41 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 10:27:31 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:41281 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 10:27:03 -0700 Received: from google.engr.sgi.com (google.engr.sgi.com [163.154.10.145]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA07594 for ; Thu, 24 Aug 2000 10:32:51 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id KAA51643; Thu, 24 Aug 2000 10:25:16 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008241725.KAA51643@google.engr.sgi.com> Subject: mips64 upgrade To: ralf@uni-koblenz.de Date: Thu, 24 Aug 2000 10:25:16 -0700 (PDT) Cc: linux-origin@oss.sgi.com X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Ralf, Are you planning on doing an upgrade of the tree? We are not even at pre6, and pre7 just came out yesterday ... If you do this while in MtView, I will be able to help with some of the mm conflicts that you will run into ... Kanoj From owner-linux-origin@oss.sgi.com Thu Aug 24 12:16:42 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 12:16:32 -0700 Received: from sgigate.SGI.COM ([204.94.209.1]:19755 "EHLO gate-sgigate.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 12:16:09 -0700 Received: (ralf@lappi) by lappi.waldorf-gmbh.de id ; Thu, 24 Aug 2000 12:12:28 -0700 Date: Thu, 24 Aug 2000 12:12:28 -0700 From: Ralf Baechle To: Kanoj Sarcar Cc: linux-origin@oss.sgi.com Subject: Re: mips64 upgrade Message-ID: <20000824121228.A1027@bacchus.dhis.org> References: <200008241725.KAA51643@google.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008241725.KAA51643@google.engr.sgi.com>; from kanoj@google.engr.sgi.com on Thu, Aug 24, 2000 at 10:25:16AM -0700 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Thu, Aug 24, 2000 at 10:25:16AM -0700, Kanoj Sarcar wrote: > Are you planning on doing an upgrade of the tree? We are not even at pre6, > and pre7 just came out yesterday ... > > If you do this while in MtView, I will be able to help with some of the > mm conflicts that you will run into ... I actually even have a number of patches that I created in during one of the flights on my disk but I want to test them first before I commit them. Ralf From owner-linux-origin@oss.sgi.com Thu Aug 24 12:28:11 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 12:28:02 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:62290 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 12:27:36 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA08171; Thu, 24 Aug 2000 12:33:24 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: from google.engr.sgi.com ([163.154.10.145]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id MAA90645; Thu, 24 Aug 2000 12:26:35 -0700 (PDT) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id MAA34325; Thu, 24 Aug 2000 12:24:03 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008241924.MAA34325@google.engr.sgi.com> Subject: Re: mips64 upgrade To: ralf@oss.sgi.com (Ralf Baechle) Date: Thu, 24 Aug 2000 12:24:03 -0700 (PDT) Cc: linux-origin@oss.sgi.com In-Reply-To: <20000824121228.A1027@bacchus.dhis.org> from "Ralf Baechle" at Aug 24, 2000 12:12:28 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing > > On Thu, Aug 24, 2000 at 10:25:16AM -0700, Kanoj Sarcar wrote: > > > Are you planning on doing an upgrade of the tree? We are not even at pre6, > > and pre7 just came out yesterday ... > > > > If you do this while in MtView, I will be able to help with some of the > > mm conflicts that you will run into ... > > I actually even have a number of patches that I created in during one of > the flights on my disk but I want to test them first before I commit them. > > Ralf > The tree seems broken right now (at least SMP), so lets coordinate offline about the order of the upgrade and fixing SMP. Kanoj From owner-linux-origin@oss.sgi.com Thu Aug 24 13:08:33 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 13:08:23 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:13085 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 13:08:07 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA25460 for ; Thu, 24 Aug 2000 12:59:56 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: from google.engr.sgi.com ([163.154.10.145]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id NAA54550 for ; Thu, 24 Aug 2000 13:05:46 -0700 (PDT) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id NAA62429 for linux-origin@oss.sgi.com; Thu, 24 Aug 2000 13:03:16 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008242003.NAA62429@google.engr.sgi.com> Subject: penguin4 To: linux-origin@oss.sgi.com Date: Thu, 24 Aug 2000 13:03:16 -0700 (PDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing If anyone was using penguin4, I have retargetted /dev/console from major/minor 5, 1 to 4, 64. Kanoj From owner-linux-origin@oss.sgi.com Thu Aug 24 13:35:23 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 13:35:13 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:24614 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 13:34:56 -0700 Received: from google.engr.sgi.com (google.engr.sgi.com [163.154.10.145]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id NAA29816 for ; Thu, 24 Aug 2000 13:26:48 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id NAA09061 for linux-origin@oss.sgi.com; Thu, 24 Aug 2000 13:33:09 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008242033.NAA09061@google.engr.sgi.com> Subject: o200s To: linux-origin@oss.sgi.com Date: Thu, 24 Aug 2000 13:33:09 -0700 (PDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Why is the state of the o200s used for the mips64 port so pitiable? One of penguin2/penguin4 is now called something like "ice", and the others reset line seems to have been stolen away from it. That seems to only leave penguin3 as the only healthy o200 with a Linux disk ... Does anyone have any clues about whats going on? Kanoj From owner-linux-origin@oss.sgi.com Thu Aug 24 13:45:03 2000 Received: by oss.sgi.com id ; Thu, 24 Aug 2000 13:44:53 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:60768 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 24 Aug 2000 13:44:27 -0700 Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA03482 for ; Thu, 24 Aug 2000 13:50:15 -0700 (PDT) mail_from (dagum@barrel.engr.sgi.com) Received: from barrel.engr.sgi.com (barrel.engr.sgi.com [163.154.5.63]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id NAA92082 for <@cthulhu.engr.sgi.com:linux-origin@oss.sgi.com>; Thu, 24 Aug 2000 13:43:41 -0700 (PDT) mail_from (dagum@barrel.engr.sgi.com) Received: (from dagum@localhost) by barrel.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA17427; Thu, 24 Aug 2000 13:43:05 -0700 From: "Leo Dagum" Message-Id: <10008241343.ZM17425@barrel.engr.sgi.com> Date: Thu, 24 Aug 2000 13:43:05 -0700 In-Reply-To: Kanoj Sarcar "o200s" (Aug 24, 1:33pm) References: <200008242033.NAA09061@google.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Kanoj Sarcar , linux-origin@oss.sgi.com Subject: Re: o200s Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Aug 24, 1:33pm, Kanoj Sarcar wrote: > Subject: o200s > Why is the state of the o200s used for the mips64 port so pitiable? > > One of penguin2/penguin4 is now called something like "ice", and > the others reset line seems to have been stolen away from it. That > seems to only leave penguin3 as the only healthy o200 with a Linux > disk ... > > Does anyone have any clues about whats going on? penguin2 has a hub extender board in it, and has it's xtalk clocked up so it could talk to an ibrick. Unfortunately the prom seems to have gotten hosed at some point and it won't boot to the prom prompt. Since we're not doing any o200/ibrick work anymore, anyone who has the time and inclination is free to get the xtalk clocked back down (ask Dean Olson in mft to do it), remove the hub extender board and flash a good prom. Then it should be good to go again. - leo > > Kanoj >-- End of excerpt from Kanoj Sarcar -- Leo Dagum SGI Mountain View, CA 94043 (650-933-2179) From owner-linux-origin@oss.sgi.com Sun Aug 27 09:59:08 2000 Received: by oss.sgi.com id ; Sun, 27 Aug 2000 09:58:58 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:15655 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Sun, 27 Aug 2000 09:58:29 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA03179; Sun, 27 Aug 2000 09:50:21 -0700 (PDT) mail_from (kanoj@google.engr.sgi.com) Received: from google.engr.sgi.com ([163.154.10.145]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id JAA95252; Sun, 27 Aug 2000 09:57:28 -0700 (PDT) Received: (from kanoj@localhost) by google.engr.sgi.com (SGI-8.9.3/8.9.3) id JAA38150; Sun, 27 Aug 2000 09:54:57 -0700 (PDT) From: Kanoj Sarcar Message-Id: <200008271654.JAA38150@google.engr.sgi.com> Subject: Re: CVS Update@oss.sgi.com: linux To: ralf@oss.sgi.com (Ralf Baechle) Date: Sun, 27 Aug 2000 09:54:57 -0700 (PDT) Cc: linux-origin@oss.sgi.com In-Reply-To: <20000827000332Z42234-31375+281@oss.sgi.com> from "Ralf Baechle" at Aug 26, 2000 05:03:31 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing > > CVSROOT: /home/pub/cvs > Module name: linux > Changes by: ralf@oss.sgi.com 00/08/26 17:03:21 > > Modified files: > arch/mips64/arc: Makefile console.c > arch/mips64/kernel: setup.c > arch/mips64/sgi-ip27: Makefile ip27-setup.c > Added files: > arch/mips64/sgi-ip27: ip27-console.c > > Log message: > Desinfect console code from #ifdefmania. > > Ralf, This does not work, I tried it before I checked the console init code in. It _seems_ to be working, it is not _really_ working. This is part of the work I am doing to determine serial port addresses at run time. In any case, I am trying to work around other ioc3 oddities currently. Once I resolve that, I will most probably revert the code back to the original form I checked it in (after I convince myself, again, that the console init setup in ip27_setup will not work). More discussions of this deferred till that time ... If you want to argue what I am saying is wrong, here's a simple experiment: change ip27prom_console_write to do prom_printf("IP27 CON: %s", s); Then all kernel printks should print the "IP27 CON" before the printk strings. The register_console at least must be done after the paging_init() has completed in setup_arch(). Kanoj