mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: Nathan Straz <nstraz@sgi.com>, Paul Jackson <pj@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Stock IA64 kernel on SGI Altix 350
Date: Thu, 3 Jun 2004 13:19:06 -0700	[thread overview]
Message-ID: <200406031319.06466.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040603200905.GA27701@fi.muni.cz>

On Thursday, June 3, 2004 1:09 pm, Jan Kasprzak wrote:
> 	Wow, mail to lkml is way faster than asking local SGI support :-).
> Thank you all for fast reply and sorry for posting to the wrong list.

Cool, but keep in mind that this is totally unsupported.  If this kernel 
breaks, you get to keep both pieces (though I'll try to help glue it back 
together!) :)

> 	Thanks, I did not know about sn2_defconfig nor compressed
> (I was trying to boot gzip-9'ed vmlinux, which was probably the reason
> of why I failed). Is make sn2_defconfig and make compressed documented
> anywhere in the kernel sources? I think short
> Documentation/ia64/README.Altix or README.sn2 would be helpful.

I think 'make help' documents most of it.

> 	However - it still does not work, altough I got at least some
> console messages. I have tried both stock 2.6.6 and 2.6.7-rc2-mm2
> (make sn2_defconfig, make -j compressed).
>
> Uncompressing Linux... done
> Memory: 11803200k/11929104k available (7422k code, 137904k reserved, 4016k
> data, 336k init) McKinley Errata 9 workaround not needed; disabling it
> Calibrating delay loop... 2077.40 BogoMIPS
> Dentry cache hash table entries: 2097152 (order: 10, 16777216 bytes)
> Inode-cache hash table entries: 1048576 (order: 9, 8388608 bytes)
> Mount-cache hash table entries: 1024 (order: 0, 16384 bytes)
> Boot processor id 0x0/0x0
> task migration cache decay timeout: 10 msecs.
> Mount-cache hash table entries: 1024 (order: 0, 16384 bytes)
> Boot processor id 0x0/0x0
> task migration cache decay timeout: 10 msecs.
> CPU 1: base freq=200.000MHz, ITC ratio=14/2, ITC freq=1400.000MHz+/--1ppm
> Calibrating delay loop... 16.44 BogoMIPS
>
> ... both kernel versions (2.6.6 and 2.6.7-rc2-mm2) hang there. Also note
> the strange bogomips value for CPU 1. The system has three bricks
> (6 CPUs, 1400MHz/3MB cache). Firmware is pretty recent (the newest
> we could find at www.sgi.com):
>
> 002c06#0a: SGI SAL Version 3.25 rel040225 IP41 built 12:01:43 PM Feb 25,
> 2004

These messages are consistent with having a PROM that's too old; you need at 
least 3.32.  You'll have to dig around the support site some more or talk to 
your support person for that though.  Booting with 'nohalt' should work 
around this particular issue though.

Jesse


  reply	other threads:[~2004-06-03 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 17:01 Jan Kasprzak
2004-06-03 17:30 ` Jesse Barnes
2004-06-03 20:09   ` Jan Kasprzak
2004-06-03 20:19     ` Jesse Barnes [this message]
2004-06-03 20:41       ` Jan Kasprzak
2004-06-04 12:09     ` Jan-Benedict Glaw
2004-06-04 15:03       ` Linus Torvalds
2004-06-03 17:34 ` Paul Jackson
     [not found] <962201031@toto.iv>
2004-06-04  3:59 ` Peter Chubb

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=200406031319.06466.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=kas@informatics.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nstraz@sgi.com \
    --cc=pj@sgi.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

all inboxes | Powered by JetHome®