From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
David Howells <dhowells@redhat.com>,
Neil Brown <neilb@cse.unsw.edu.au>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-kernel@vger.kernel.org, alex@hausnet.ru, mingo@redhat.com
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.
Date: Sun, 12 Nov 2006 21:32:36 +0100 [thread overview]
Message-ID: <1163363556.15249.27.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200611122019.09851.ioe-lkml@rameria.de>
On Sun, 2006-11-12 at 20:18 +0100, Ingo Oeser wrote:
> Hi there,
>
> On Sunday, 12. November 2006 14:16, Arjan van de Ven wrote:
> > If this isn't UP this could be the first real case of "noapic" in your
> > entire list...... which isn't too useful.
> > Maybe we need to get more/any people who see "need noapic on SMP" to
> > file a bug (and provide a reasonable amount of info)
>
> I need noapic since ever (5 years!) to get my USB controller running.
> Without noapic it doesn't get any interrupts for some reason.
so it never worked? (that's important to know versus regression)
Also does this machine use ACPI for interrupt routing?
That's also important, because if you're NOT using ACPI, "noapic" means
that you're using the PIRQ for irq routing and not MPS, so you're not
"just" changing apic behavior, you're actually using a different BIOS
table. (and to be honest, a buggy bios table is more likely the
cause ... ;)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-12 20:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611111129.kABBTWgp014081@fire-2.osdl.org>
2006-11-11 18:00 ` Andrew Morton
2006-11-11 18:10 ` Arjan van de Ven
2006-11-11 18:19 ` Andrew Morton
2006-11-12 11:50 ` Arjan van de Ven
2006-11-12 12:53 ` Adrian Bunk
2006-11-12 13:16 ` Arjan van de Ven
2006-11-12 13:37 ` Adrian Bunk
2006-11-12 13:57 ` Arjan van de Ven
2006-11-12 14:10 ` Adrian Bunk
2006-11-12 14:16 ` Arjan van de Ven
2006-11-12 15:21 ` Adrian Bunk
2006-11-12 15:50 ` Arjan van de Ven
2006-11-12 15:59 ` Patrick McFarland
2006-11-12 16:07 ` Arjan van de Ven
2006-11-12 16:47 ` Adrian Bunk
2006-11-12 21:45 ` Dave Jones
2006-11-13 2:07 ` Andi Kleen
2006-11-12 19:18 ` Ingo Oeser
2006-11-12 19:34 ` Andrew Morton
2006-11-12 20:32 ` Arjan van de Ven [this message]
2006-11-13 6:42 ` Neil Brown
2006-11-13 11:22 ` David Howells
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=1163363556.15249.27.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=alex@hausnet.ru \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bunk@stusta.de \
--cc=dhowells@redhat.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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®