linux-kernel - Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Jul 2006 14:48:54 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Paul Fulghum <paulkf@...rogate.com>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <ak@....de>,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

On Fri, 28 Jul 2006 13:44:36 -0500
Paul Fulghum <paulkf@...rogate.com> wrote:

> 2.6.18-rc2-mm1 causes boot to fail early with:
> kernel panic: IO_APIC timer interrupt 0 doesn't work
> 
> 2.6.18-rc2 works.
> 
> 2.6.18-rc2-mm1 kernel config located at:
> http://www.microgate.com/ftp/linux/test/config
> 
> syslog from working 2.6.18-rc2 located at:
> http://www.microgate.com/ftp/linux/test/syslog
> 

I don't know what would have caused this.  Was 2.6.18-rc1-mm2 OK?

Patches which touch arch/i386/kernel/io_apic.c are:

x86_64-mm-i386-up-generic-arch.patch
x86_64-mm-i386-io-apic-access.patch
genirq-convert-the-i386-architecture-to-irq-chips.patch
initial-generic-hypertransport-interrupt-support.patch
genirq-i386-irq-remove-the-msi-assumption-that-irq-==-vector.patch
genirq-i386-irq-move-msi-message-composition-into-io_apicc.patch
genirq-i386-irq-dynamic-irq-support.patch

The developers of those patches are cc'ed.

A bisection search would be useful, if you have the time.  I'd zero in on
the x86_64 tree initially.  Perhaps x86_64-mm-i386-io-apic-access.patch.

Or it could be something else altogether.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/