From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] rtl8139 ether driver From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-xapwbsscmvbdcdjmdsdvyembig" Message-Id: <20020626023244.6D92B19A84@mail.cse.psu.edu> Date: Wed, 26 Jun 2002 11:31:20 +0900 Topicbox-Message-UUID: b9605da6-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-xapwbsscmvbdcdjmdsdvyembig Content-Disposition: inline Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Thank you very much, Jim. It may hard to read the error message even if I make it run in debugging mode, because it occures very rarely, and when it happenes, that machine reboots automatically, and then, that neccessary mesage could be hidden among lots of others... When I experienced system crush of our CPU server, I tried to find some other dual Pentium machine for it. I failed to do it, because there may be no Pen III dual motherboard in the market, except only of SuperMicro's Xeon motherbord, which is very very expensive, and beyond my scope of fund. (I was told some $1,200~1,300 for that motherboard!!) So, I had to choose Pen 4 mother for that server. This may also be true for most of Plan 9 users now. How we can enjoy multi-CPU nature of Plan 9. Alas! Kenji --upas-xapwbsscmvbdcdjmdsdvyembig Content-Type: message/rfc822 Content-Disposition: inline Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Wed Jun 26 10:58:40 JST 2002 Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2]) by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id KAA12311 for ; Wed, 26 Jun 2002 10:48:50 +0900 Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-02040219) with ESMTP id KAA05529 for ; Wed, 26 Jun 2002 10:59:22 +0900 (JST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.23.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 8D2E619A6D; Tue, 25 Jun 2002 21:59:13 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from plan9.cs.bell-labs.com (ampl.com [204.178.31.2]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 9127419A6A for <9fans@cse.psu.edu>; Tue, 25 Jun 2002 21:58:37 -0400 (EDT) Message-ID: <7b2da9c3f29b1a4d0c352b4167dd4757@plan9.bell-labs.com> From: jmk@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] rtl8139 ether driver MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 25 Jun 2002 21:58:34 -0400 On Tue Jun 25 21:48:22 EDT 2002, okamoto@granite.cias.osakafu-u.ac.jp wrote: > > I'm now forced to use rtl8139 nic for my new Auth/CPU server ( > it's for 3ed not 4ed. I cannot update our system now, because it's > being used for the platform for our application, and the semester is > still going here). it reboots once a day. :-) > > We had been using dual Pen III on SuperMicro motherboard, but it > crushed about a month ago. Then, I changed that server to a Pen 4 > mother board (1.6GHz) of AOpen AX4B Pro-533 which has on board > nic chip of Realtek 8100BL. It seems to work fine, however, it may > have problem as above. > > When I read the /sys/src/9/pc/ether8139.c, I found the lines of > "Error recovery for the various over/under-flow conditions may need work" > phrase. Does my problem relate to this remark? > > Kenji I only have an 8139C and I've not ever seen an error of any kind on it, hence my comment about work may be required if any error conditions happen. Someone else asked me a similar question some months ago, and I suggested putting in debugging prints in the driver wherever an error is detected. That way you will see something if the card causes any problem and then reboots the machine. There may also be problems with the P4 processor, we don't have any here to run on. --jim --upas-xapwbsscmvbdcdjmdsdvyembig--