lkml.org 
[lkml]   [2014]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Ask help about pre_init_apic_IRQ0()
From
Date
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@intel.com>
Intel Finland Oy



\
 
 \ /
  Last update: 2014-09-12 11:01    [W:0.068 / U:0.792 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site