mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: enabling IOAPIC on C3 processor?
Date: Tue, 15 Mar 2005 13:34:55 +0100	[thread overview]
Message-ID: <16950.54895.527127.21123@alkaid.it.uu.se> (raw)
In-Reply-To: <5a2cf1f6050315040956a512a6@mail.gmail.com>

jerome lacoste writes:
 > I have a VIA Epia M10000 board that crashes very badly (and pretty
 > often, especially when using DMA). I want to fix that.
 > 
 > Serial console + magic SysRQ didn't help so I am going the nmi
 > watchdog way. But in order to have nmi watchdog I need APIC, right?
 > 
 > The C3 processor seems to support IOAPIC.
 > (http://www.via.com.tw/en/products/processors/c3/specs.jsp)
 > 
 > But:
 > - I don't see anything in the BIOS related to APIC. 
 > - grep APIC /lib/modules/`uname -r`/build/.config shows me that all
 > APIC options are 'y'.
 > - dmesg | grep APIC tells me "no local APIC present or hardware disabled".
 > - adding lapic kernel parameter doesn't change that. 
 > - and of course, nmi_watchdog=1 or 2 gives me NMI count 0 in /proc/interrupts.
 > 
 > Did I miss something when it comes to enabling IOAPIC support on C3 processor?

Unless you have a pre-release engineering part for a future product,
then your C3 has no local APIC, and hence no I/O APIC functionality.

I know some C3 specs pages list I/O APIC support, but if you look in
the datasheets for current products you find zero APIC support.

  reply	other threads:[~2005-03-15 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 12:09 jerome lacoste
2005-03-15 12:34 ` Mikael Pettersson [this message]
2005-03-15 12:52   ` enabling IOAPIC on C3 processor? (how to investigate hangs without nmi watchdog) jerome lacoste
2005-03-15 12:57     ` Mikael Pettersson
2005-03-15 14:40     ` Dave Jones
2005-03-15 20:22 ` enabling IOAPIC on C3 processor? Lee Revell
2005-03-16 15:11   ` jerome lacoste
2005-03-16 20:48     ` Lee Revell
2005-03-17 15:27       ` jerome lacoste

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=16950.54895.527127.21123@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=jerome.lacoste@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®