linux-kernel - Re: [PATCH 8/8] x86: I/O APIC: Timer through 8259A second-chance

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]

Message-ID: <20080605150327.GA22128@elte.hu>
Date:	Thu, 5 Jun 2008 17:03:27 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 8/8] x86: I/O APIC: Timer through 8259A second-chance


* Maciej W. Rozycki <macro@...ux-mips.org> wrote:

>  It seems wrong to me to set timer_through_8259 in apic_{32,64}.c -- 
> can I get .config for this setup as well as the bootstrap log?  Why is 
> the 8259A needed here to supply the timer interrupt?  It shouldn't be 
> needed except as arranged in check_timer() -- elsewhere the 
> corresponding I/O APIC input is not set up correctly.
> 
>  Note I have chosen the default value of timer_through_8259 
> deliberately to trigger dodgy cases like this ;) so that they can be 
> investigated.

find them here:

 http://redhat.com/~mingo/misc/config-Thu_Jun__5_16_40_50_CEST_2008.bad
 http://redhat.com/~mingo/misc/log-Thu_Jun__5_16_40_50_CEST_2008.bad

NOTE: you need to copy out and use the boot parameters from the boot 
log:

 [ 0.000000] Command line: root=/dev/sda6 console=ttyS0,115200 
 earlyprintk=se rial,ttyS0,115200 debug initcall_debug apic=verbose 
 sysrq_always_enabled ignore _loglevel selinux=0 nmi_watchdog=1 
 profile=0 maxcpus=1 nosmp no_hz=off highres =0 noapic nolapic_timer 
 hpet=disable idle=mwait

as -tip testing occasionally randomizes boot parameters too. (to find 
regressions like this) Let me know if you cannot reproduce this.

	Ingo
--
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/