From: Greg Edwards <edwardsg@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium
Date: Wed, 29 Mar 2006 19:01:30 +0000 [thread overview]
Message-ID: <20060329190130.GE12830@sgi.com> (raw)
In-Reply-To: <442AB6DD.4020800@sgi.com>
On Wed, Mar 29, 2006 at 01:55:26PM -0500, Prarit Bhargava wrote:
| But it looks like it is hanging on Altix's at
|
| Calling initcall 0xa0000001006ad230: bictcp_register+0x0/0x40()
| TCP bic registered
| Calling initcall 0xa0000001006b1160: xfrm_user_init+0x0/0xe0()
| Initializing IPsec netlink socket
| Calling initcall 0xa0000001006ade70: af_unix_init+0x0/0x120()
| NET: Registered protocol family 1
| Calling initcall 0xa0000001006adfc0: packet_init+0x0/0x100()
| NET: Registered protocol family 17
| Calling initcall 0xa0000001006a9670: acpi_poweroff_init+0x0/0x100()
| Calling initcall 0xa0000001006af2d0: seqgen_init+0x0/0x40()
| Calling initcall 0xa0000001006b18d0: early_uart_console_switch+0x0/0x120()
| Calling initcall 0xa0000001006a8e10: net_random_reseed+0x0/0x100()
| Freeing unused kernel memory: 400kB freed
Is it hung, or did it MCA? Check the leds (ctrl-t to L2 from console,
then 'leds'). If you repeat this procedure, you should see the LED
values changing.
Greg
next prev parent reply other threads:[~2006-03-29 19:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 16:33 [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium Prarit Bhargava
2006-03-29 16:34 ` Prarit Bhargava
2006-03-29 16:55 ` Chen, Kenneth W
2006-03-29 18:55 ` Prarit Bhargava
2006-03-29 19:01 ` Greg Edwards [this message]
2006-03-29 19:55 ` Chen, Kenneth W
2006-03-29 20:13 ` Luck, Tony
2006-03-29 20:51 ` Grant Grundler
2006-03-29 20:57 ` [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on James Bottomley
2006-03-29 20:58 ` [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium Luck, Tony
2006-03-29 21:36 ` Émeric Maschino
2006-03-29 22:04 ` Jack Steiner
2006-03-30 8:57 ` Jes Sorensen
2006-03-30 9:04 ` Jes Sorensen
2006-03-30 9:08 ` Jes Sorensen
2006-03-30 9:14 ` Keith Owens
2006-03-30 10:11 ` Jes Sorensen
2006-03-30 12:29 ` Jes Sorensen
2006-03-30 13:24 ` Jes Sorensen
2006-03-30 15:16 ` Jack Steiner
2006-03-30 15:42 ` Prarit Bhargava
2006-03-30 15:43 ` David Mosberger-Tang
2006-03-30 15:49 ` Jack Steiner
2006-03-30 15:53 ` David Mosberger-Tang
2006-03-30 16:34 ` H. J. Lu
2006-03-30 16:38 ` Prarit Bhargava
2006-03-30 16:45 ` H. J. Lu
2006-03-30 16:52 ` Prarit Bhargava
2006-03-30 16:53 ` Bjorn Helgaas
2006-03-30 17:10 ` Jack Steiner
2006-03-30 18:23 ` Luck, Tony
2006-03-30 18:23 ` Prarit Bhargava
2006-03-30 18:54 ` Grant Grundler
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=20060329190130.GE12830@sgi.com \
--to=edwardsg@sgi.com \
--cc=linux-ia64@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.