From: Pete Zaitcev <zaitcev@metabyte.com>
To: ultralinux@vger.kernel.org
Subject: SBus in 2.3
Date: Mon, 18 Oct 1999 02:17:49 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-94021308306451@msgid-missing> (raw)
Fellow 64 bit enabled hackers,
If I understand correctly, 2.3 is in use on sparc64 for some time.
Do you guys have any problems on Ultra-1/140?
I did regressions on sparc64 for my sparc putback today as it touches
some common files and there was some strage problem on U-1,
which looks like this:
[root@iolab130 /root]# ifconfig eth0 up
IRQ: Trying to share non-PCI bucket.
Lance: Can't get irq 5,7e1
SIOCSIFFLAGS: Resource temporarily unavailable
Hmm... I would track it down myself but I do not have good
access to sparc64's. Any ideas?
--Pete
next reply other threads:[~1999-10-18 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-18 2:17 Pete Zaitcev [this message]
1999-10-18 5:53 ` SBus in 2.3 David S. Miller
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=marc-linux-ultrasparc-94021308306451@msgid-missing \
--to=zaitcev@metabyte.com \
--cc=ultralinux@vger.kernel.org \
/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