From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Test second.b for helping to fix initrd problems
Date: Mon, 12 Jul 2004 00:38:17 +0000 [thread overview]
Message-ID: <20040712003817.GC16609@phunnypharm.org> (raw)
I haven't been able to nail down this initrd problem with SILO. No one
else has had time to dig into it either.
I can't reproduce it. Moving dimms around in my machines doesn't cause a
problem.
I've made a second.b that is a little more verbose with the sparc64 memory
finder routine. I'd appreciate it if anyone that is having problems with
initrd could test this so I can see the output. If you happen to be able
to move your dimms around in a way that allows SILO to work, then please
send me the output of both ways so I can compare notes.
I need to get this bug fixed. Quite a few dists are hurting because of it.
http://www.sparc-boot.org/pub/testing/second.b
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next reply other threads:[~2004-07-12 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 0:38 Ben Collins [this message]
2004-07-13 21:54 ` Test second.b for helping to fix initrd problems Ben Collins
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=20040712003817.GC16609@phunnypharm.org \
--to=bcollins@debian.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.