From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm5: scheduler problem & apic
Date: Fri, 8 Aug 2003 20:30:19 +0000 (UTC) [thread overview]
Message-ID: <bh118r$6ch$1@news.cistron.nl> (raw)
In-Reply-To: 200308081932.56347.alistair@devzero.co.uk
Alistair J Strachan <alistair@devzero.co.uk> wrote:
>Andrew, I don't know if anybody's given you any feedback regarding the nForce
>2 APIC fix, but it appears to resolve the dead kernel problem, and I no
>longer have problems with IRQ fallouts when using acpi, and I've removed
>pci=noacpi from cmdline. ACPI and APIC now work together harmoniously.
I still occasionally see this behaviour:
New kernel install (booting from 2.6.0-test2 (vanilla)):
EXT3-fs: mounted filesystem with ordered data mode.
irq 19: nobody cared!
Call Trace:
[<c010be0a>] __report_bad_irq+0x32/0x90
[<c010bee0>] note_interrupt+0x50/0x78
[<c010c0e0>] do_IRQ+0xc0/0x124
[<c0108dd0>] default_idle+0x0/0x34
[<c0107000>] _stext+0x0/0x48
[<c02819ec>] common_interrupt+0x18/0x20
[<c0108dd0>] default_idle+0x0/0x34
[<c0107000>] _stext+0x0/0x48
[<c0108df9>] default_idle+0x29/0x34
[<c0108e83>] cpu_idle+0x37/0x48
[<c0107045>] _stext+0x45/0x48
[<c032276b>] start_kernel+0x147/0x150
handlers:
[<c01f3b34>] (ide_intr+0x0/0x160)
[<c01f3b34>] (ide_intr+0x0/0x160)
Disabling IRQ #19
hde: sata_error = 0x00400000, watchdog = 1, siimage_mmio_ide_dma_test_irq
hdg: sata_error = 0x00400000, watchdog = 1, siimage_mmio_ide_dma_test_irq
powercycling the machine let the kernel boot without this notice (and normal
working). This is a newsgate machine with HT and sata.
Sounds familiar ?
Danny
--
I think so Brain, but why does a forklift
have to be so big if all it does is lift forks?
prev parent reply other threads:[~2003-08-08 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 18:32 2.6.0-test2-mm5: scheduler problem & apic Alistair J Strachan
2003-08-08 20:30 ` Danny ter Haar [this message]
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='bh118r$6ch$1@news.cistron.nl' \
--to=dth@ncc1701.cistron.net \
--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