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 -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
