public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] i2000 won't boot for me with current 2.5.69-bk
Date: Mon, 26 May 2003 21:21:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706035@msgid-missing> (raw)

I've tracked down the problem to something in mca.c:  the second call
to get SAL error logs causes a partial reboot instead of returning
error logs.  I instrumented bits of mca.c to see what was going on
(hope the printk output is self-explanatory). This is on a
uniprocessor i2000.

calling initcall 0xa00000010070fbe8  ( __initcall_ia64_mca_check_errors )
ia64_mca_log_sal_error_record
ia64_log_get()
ia64_log_get -- log_lock
ia64_log_get -- sal_get_state_info
SAL_CALL(isrv, SAL_GET_STATE_INFO, ...)
sal_get_state_info returned 0
log_get returned null
calling initcall 0xa00000010070fbf0 ( __initcall_ia64_mca_late_init )
init_timer(cmc_poll_timer)
init_tiemr(cpe_poll_timer)
acpi_request_vector(ACPI_INTERRUPT_CPE1) (obviously couldn't get it...)
ia64_mca_cpe_poll
set start_count
smp call ia64_mca_cpe_int_caller
local call ia64_mca_cpe_int_caller
ia64_mca_cpe_int_handler
ia64_mca_log_sal_error_record
ia64_log_get()
ia64_log_get -- log_lock
ia64_log_get -- sal_get_state_info
SAL_CALL(isrv, SAL_GET_STATE_INFO, ...)

(Monitor goes blank, I hear the floppy drive seek, and machine becomes
totally unresponsive and needs to be power cycled to continue)

Does anyone have any ideas?

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories,   all slightly different.


             reply	other threads:[~2003-05-26 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 21:21 Peter Chubb [this message]
2003-05-27  0:04 ` [Linux-ia64] i2000 won't boot for me with current 2.5.69-bk Peter Chubb
2003-05-27  0:44 ` Alex Williamson
2003-05-27  3:23 ` 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=marc-linux-ia64-105590723706035@msgid-missing \
    --to=peter@chubb.wattle.id.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox