From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] sudden kirkwood problem
Date: Sun, 26 Sep 2010 17:25:16 -0700 [thread overview]
Message-ID: <AANLkTimbZYdhLNaFZee4pjtZa3hiaEqtXVB1yDpkg7L0@mail.gmail.com> (raw)
nandecccorrect: calculated ecc 005b9999 stored ecc 001ba110
nandecccorrect: 2 bit error
(page 0)
can't read 112 bytes from <nil>: i/o error
authid: bootes
authdom: home
secstore key:
password:
nandecccorrect: calculated ecc 005b9999 stored ecc 001ba110
nandecccorrect: 2 bit error
(page 0)
can't write key to nvram: i/o error
version.panic: boot process died: unknown
ktrace /kernel/path 0x60806b98 0x6099ef50 0x6099ef8d # pc, sp, link
panic: boot process died: unknown
cpu0: exiting
reset!
same error, 2 different kirkwoods. Code just built from sources today.
Anyone ever seen anything like
this?
ron
next reply other threads:[~2010-09-27 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 0:25 ron minnich [this message]
2010-09-27 0:31 ` erik quanstrom
2010-09-27 0:52 ` ron minnich
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=AANLkTimbZYdhLNaFZee4pjtZa3hiaEqtXVB1yDpkg7L0@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).