From: daniel+devel-linux-sparclinux@flexserv.de
To: sparclinux@vger.kernel.org
Subject: Re: oops on e4k5
Date: Sat, 22 Jul 2006 08:45:54 +0000 [thread overview]
Message-ID: <873bcum3i5.fsf@xserver.flexserv.de> (raw)
In-Reply-To: <877j26m8kl.fsf@xserver.flexserv.de>
Hello David,
thanks for your response
David Miller <davem@davemloft.net> writes:
> The OOPS is severely truncated where the most important
> information would normally appear. Please reproduce with
> the following patch applied.
okay i will do so.
>
> It might also help if you turn off CONFIG_PROM_CONSOLE.
> The zilog serial driver should drive your console just fine,
> and your logs show it does register properly.
>
> Also, what kind of cpus are in this machine? (/proc/cpuinfo
> output is sufficient)
>
> Thanks.
cpu : TI UltraSparc II (BlackBird)
fpu : UltraSparc II integrated FPU
prom : OBP 3.2.26 2000/05/09 19:07
type : sun4u
ncpus probed : 10
ncpus active : 10
D$ parity tl1 : 0
I$ parity tl1 : 0
Cpu0Bogo : 800.48
Cpu0ClkTck : 0000000017d78400
Cpu1Bogo : 800.05
Cpu1ClkTck : 0000000017d78400
Cpu4Bogo : 800.05
Cpu4ClkTck : 0000000017d78400
Cpu5Bogo : 800.05
Cpu5ClkTck : 0000000017d78400
Cpu8Bogo : 800.05
Cpu8ClkTck : 0000000017d78400
Cpu9Bogo : 800.05
Cpu9ClkTck : 0000000017d78400
Cpu10Bogo : 800.05
Cpu10ClkTck : 0000000017d78400
Cpu11Bogo : 800.05
Cpu11ClkTck : 0000000017d78400
Cpu12Bogo : 800.05
Cpu12ClkTck : 0000000017d78400
Cpu13Bogo : 800.05
Cpu13ClkTck : 0000000017d78400
MMU Type : Spitfire
State:
CPU0: online
CPU1: online
CPU4: online
CPU5: online
CPU8: online
CPU9: online
CPU10: online
CPU11: online
CPU12: online
CPU13: online
next prev parent reply other threads:[~2006-07-22 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 6:56 oops on e4k5 Daniel J. Priem
2006-07-22 8:10 ` David Miller
2006-07-22 8:45 ` daniel+devel-linux-sparclinux [this message]
2006-07-23 6:07 ` daniel+devel.linux.sparclinux
-- strict thread matches above, loose matches on Subject: below --
2006-07-21 20:18 daniel+devel.linux.lkml
2006-07-21 21:06 ` David 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=873bcum3i5.fsf@xserver.flexserv.de \
--to=daniel+devel-linux-sparclinux@flexserv.de \
--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.