All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Hacking SuperDome
Date: Wed, 11 Feb 2009 00:23:12 -0700	[thread overview]
Message-ID: <20090211072312.GA19531@colo.lackof.org> (raw)
In-Reply-To: <20090207142906.GA8553@alpha.franken.de>

On Sat, Feb 07, 2009 at 03:29:06PM +0100, Thomas Bogendoerfer wrote:
> Hi,
> 
> thanks to Madze, I've now access to a HP Superdome;-)

Wow...that's so cool...I didn't this would happen. :)

> The bigger partition produces following boot log:
...

> The smaller partion hangs even earlier:
> 
> HARD Booted.
> palo ipl 1.14 root@duet Sat Apr  8 16:08:16 EDT 2006
> 
> Boot image contains:
>     0/vmlinux64 6484269 bytes @ 0xa000
...
> SBA found REO rev 2 at 0xfffffff888000000
> Elroy version TR4.0 (0x5) found at 0xfffffff884000000
> 
> 
> First guess would be some PCI setup issues... Any hints ?

Look for HPMC's. The console can't keep up with the kernel in general.
When an HPMC occurs, some of the output can get stranded.

I would add "initcall_debug=1" to boot parameters. See kernel/main.c.
Possible add a mdelay(100) after each initcall.

Since Tulip configured properly, I'm going to assume PCI resources
were properly assigned and all PCI Busses enumerated. PCI support
shouldn't be any different than for other PAT PDC machines.

hth,
grant

  parent reply	other threads:[~2009-02-11  7:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 14:29 Hacking SuperDome Thomas Bogendoerfer
2009-02-08  4:30 ` Kyle McMartin
2009-02-08 17:05   ` Kyle McMartin
2009-02-08 23:15     ` Matthew Wilcox
2009-02-08 11:33 ` Matthew Wilcox
2009-02-11  7:23 ` Grant Grundler [this message]
2009-02-11 10:00   ` Thomas Bogendoerfer
2009-02-11 16:26     ` Matthew Wilcox
2009-02-11 17:02     ` Grant Grundler
2009-02-11 18:14   ` Kyle McMartin
2009-02-11 18:28     ` Kyle McMartin
2009-02-11 19:29     ` Grant Grundler
2009-02-12  0:36 ` Kyle McMartin
2009-02-13 20:46   ` Thomas Bogendoerfer
2009-02-15 15:33 ` Jan-Benedict Glaw

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=20090211072312.GA19531@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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.