From: "Thierry SIMONNET" <t.simonnet@esiee.fr>
To: <parisc-linux@thepuffingroup.com>
Subject: [parisc-linux] Eth0 trouble
Date: Thu, 23 Mar 2000 20:05:44 +0100 [thread overview]
Message-ID: <00ca01bf94fa$ca500580$0a14d793@esiee.fr> (raw)
In-Reply-To: 20000322220229.D10226@thepuffingroup.com
I have generated new lifimages with differents methods (ramdisk, nfsroot and
disk) using palo.
I have the following messages :
eth0: receive unit error
eth0: Null rbd - oops!
eth0: receive unit error
eth0: Null rbd - oops!
eth0: receive unit error
eth0: Null rbd - oops!
eth0: receive unit error
eth0: Null rbd - oops!
....
Before this messages, everything is OK. sash works fine, and I can execute
some test programs. After that, I lost LAN connectivity.
My config is : 712/80 Workstation, with latest binutils, gcc, linux-2.3 and
palo.
Have an idea?
THX
Th. SIMONNET
prev parent reply other threads:[~2000-03-23 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 17:44 [parisc-linux] PALO and ramdisk micro-howto Paul Bame
2000-03-21 21:40 ` Paul Bame
2000-03-22 22:33 ` 5116
2000-03-23 3:02 ` willy
2000-03-23 19:05 ` Thierry SIMONNET [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ca01bf94fa$ca500580$0a14d793@esiee.fr' \
--to=t.simonnet@esiee.fr \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox