From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] test11, test12 kernel vs. big sur: Unexpected irq vector
Date: Fri, 15 Dec 2000 17:07:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205851@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205850@msgid-missing>
John-
Two questions:
1) What version of the firmware are you running?
2) Are you including ACPI support? I found that most IRQ problems
go away when you do this.
On Fri, Dec 15, 2000 at 11:32:48AM -0500, John Kohl wrote:
> I tried booting a kernel built from the latest test12 patch kit on one
> of our development systems (big sur, A stepping). It
> starts up, prints out a few messages, then loops forever printing
> Unexpected irq vector 0x0 on CPU 0!
> This comes from arch/ia64/kernel/irq.c.
>
> We had the same problems with the test11 kernels. Any suggestions on
> how to debug and/or remedy this?
>
> --
> =John Kohl <jtk@rational.com>, Software Engineer
> Rational Software, Configuration Management Business Unit
> Mark your calendars! Rational User Conference 2001, July 22-26, 2001
> in beautiful Denver, Colorado
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
next prev parent reply other threads:[~2000-12-15 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 16:32 [Linux-ia64] test11, test12 kernel vs. big sur: Unexpected irq vector John Kohl
2000-12-15 17:07 ` Don Dugger [this message]
2000-12-15 17:11 ` John Kohl
2000-12-15 17:41 ` Don Dugger
2000-12-15 17:52 ` [Linux-ia64] test11, test12 kernel vs. big sur: Unexpected ir Hall, Jenna S
2000-12-15 17:57 ` Cook, Steven C
2000-12-15 18:05 ` Jonathan_Kwahk
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-105590678205851@msgid-missing \
--to=n0ano@valinux.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.