All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Gilmore <dennis@ausil.us>
To: sparclinux@vger.kernel.org
Subject: Re: Unknown CPU in 2.6.29-rc1
Date: Fri, 16 Jan 2009 16:11:49 +0000	[thread overview]
Message-ID: <200901161011.57560.dennis@ausil.us> (raw)
In-Reply-To: <Pine.SOC.4.64.0901161249030.2120@math.ut.ee>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Friday 16 January 2009 08:32:17 am you wrote:
> On Fri, Jan 16, 2009 at 12:58:32PM +0200, Meelis Roos wrote:
> > After Sam's insw/... fix, todays 2.6.29-rc1+git boots up and seems fo
> > work on E3500 with 2 USII-400's. However, the CPU has suddenly became
> > unknown (it was known in 2.6.27):
> >
> > [  136.434591] CPU: Unknown chip, impl[0x17] vers[0x11]
> > [  136.434649] FPU: Unknown chip, impl[0x17] vers[0x11]
>
> Did you expect:
> CPU: TI UltraSparc II  (BlackBird)
> FPU: UltraSparc II integrated FPU
>
> Ohh, I see why.
> The sucker that updated kernel/cpu.c did a poor job doing so.
> (For reference: it was me)
>
> I assume manufacturer_info can be indexed but it needs to be searched.
> Will likely fix tonight if you do not beat me.
>
> I think I know why I did this mistake, as I really did not make up
> my mind what approach to use and ended up mixing it.
>
> [For the record I do not have a sparc to test it on.
> My SUN Blade 100 are cauing me troubles..]
if its locking up regularly try appending ide=nodma to the kernel line.

Dennis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-01-16 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 10:58 Unknown CPU in 2.6.29-rc1 Meelis Roos
2009-01-16 11:08 ` Meelis Roos
2009-01-16 14:32 ` Sam Ravnborg
2009-01-16 16:11 ` Dennis Gilmore [this message]
2009-01-16 17:18 ` Sam Ravnborg
2009-01-16 18:08 ` Sam Ravnborg
2009-01-16 20:09 ` Meelis Roos
2009-01-16 20:36 ` Sam Ravnborg
2009-01-16 23:39 ` Julian Calaby
2009-01-17  6:28 ` Sam Ravnborg

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=200901161011.57560.dennis@ausil.us \
    --to=dennis@ausil.us \
    --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.