linux-kernel - Re: Ask help about pre_init_apic

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: <1410509968.7023.33.camel@linux.intel.com>
Date:	Fri, 12 Sep 2014 11:19:28 +0300
From:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	x86@...nel.org
Subject: Re: Ask help about pre_init_apic_IRQ0()

On Thu, 2014-09-11 at 23:59 +0200, Thomas Gleixner wrote:
[]

> > With patch nothing happened indeed.
> > 
> > 
> > >      x86_intel_mid_timer=apbt_only
> > 
> > [    0.116839] BUG: unable to handle kernel NULL pointer dereference at
> > 0000003a
> > [    0.123803] IP: [<c1071c0e>] setup_irq+0xf/0x4d
> > ...
> > 

w/o patch

[    0.000000] Early APIC setup for system timer0
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: CPU: 0 PID: 0 at
arch/x86/kernel/apic/apic.c:1393 setup_local_APIC+0x20c/0x2d9()

...and stuck a bit later

> > > or
> > >      x86_intel_mid_timer=lapic_and_apbt
> > 
> > [    0.116858] BUG: unable to handle kernel NULL pointer dereference at
> > 0000003a
> > [    0.123820] IP: [<c1071c0e>] setup_irq+0xf/0x4d
> > ...
> > 

w/o patch

[    0.000000] Early APIC setup for system timer0
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: CPU: 0 PID: 0 at
arch/x86/kernel/apic/apic.c:1393 setup_local_APIC+0x20c/0x2d9()

...and boots normally


> > > 
> > > on the kernel commandline. But even w/o that patch I doubt that
> > > anything post moorestown even has that apbt trainwreck implemented. If
> > > I'm right then the commandline option will prevent the thing to boot
> > > at all, which is an even better reason to remove that crap
> > > alltogether.
> > 
> > See above.
> 
> That was with the patch applied, right? 

Correct.

> What happens if you undo the
> patch and add the command line options?

See above.

-- 
Andy Shevchenko <andriy.shevchenko@...el.com>
Intel Finland Oy

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