Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Cc: manoj.ekbote@broadcom.com, mark.e.mason@broadcom.com
Subject: BigSur: garbled characters during boot
Date: Sun, 25 Nov 2007 13:48:42 +0100	[thread overview]
Message-ID: <20071125124842.GA32479@deprecation.cyrius.com> (raw)

When I boot a current kernel from git on a BigSur board I get some
garbled characters:

Synthesized TLB store handler fastpath (31 instructions).
Synthesized TLB modify handler fastpath (30 instructions).
��͡�х�������ɥ��遚����Bzɑ��遪b�������ѕͥ5R�Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 250436k/257568k available (2561k kernel code, 6940k reserved, 826k data, 132k init, 0k highmem)
Mount-cache hash table entries: 512

Any idea what this might be?
-- 
Martin Michlmayr
http://www.cyrius.com/

             reply	other threads:[~2007-11-25 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 12:48 Martin Michlmayr [this message]
2007-11-25 13:28 ` BigSur: garbled characters during boot Atsushi Nemoto
2007-11-25 13:43   ` Martin Michlmayr
2007-11-26 11:34     ` Maciej W. Rozycki
2007-11-25 22:17   ` Thomas Bogendoerfer

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=20071125124842.GA32479@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=linux-mips@linux-mips.org \
    --cc=manoj.ekbote@broadcom.com \
    --cc=mark.e.mason@broadcom.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