Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

[Rafael J. Wysocki]

On 6/2/2013 6:20 AM, Fengguang Wu wrote:
> Greetings,
>
> FYI, I got this occasionally in some of my machines when testing the
> pm/bleeding-edge branch:
>
> [    0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> [    0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> [    0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
> [    0.044000] ..... (found apic 0 pin 2) ...
> [    0.048000] ....... failed.
> [    0.048000] ...trying to set up timer as Virtual Wire IRQ...
> [    0.048000] ..... failed.
> [    0.048000] ...trying to set up timer as ExtINT IRQ...
> [    0.052000] ..... failed :(.
> [    0.052000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the
> +'noapic' option.
>
> Bisect result is unfortunately not reliable..

Can you please check if this is reproducible with the acpi-hotplug 
branch alone?

Rafael

---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk

Sad Rejonowy Gdansk Polnoc w Gdansku, 
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego, 
numer KRS 101882

NIP 957-07-52-316
Kapital zakladowy 200.000 zl

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

[Fengguang Wu]

On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote:
> On 6/2/2013 6:20 AM, Fengguang Wu wrote:
> >Greetings,
> >
> >FYI, I got this occasionally in some of my machines when testing the
> >pm/bleeding-edge branch:
> >
> >[    0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> >[    0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> >[    0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
> >[    0.044000] ..... (found apic 0 pin 2) ...
> >[    0.048000] ....... failed.
> >[    0.048000] ...trying to set up timer as Virtual Wire IRQ...
> >[    0.048000] ..... failed.
> >[    0.048000] ...trying to set up timer as ExtINT IRQ...
> >[    0.052000] ..... failed :(.
> >[    0.052000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the
> >+'noapic' option.
> >
> >Bisect result is unfortunately not reliable..
> 
> Can you please check if this is reproducible with the acpi-hotplug
> branch alone?

Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect.

Thanks,
Fengguang

Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

[Fengguang Wu]

On Mon, Jun 03, 2013 at 07:26:24PM +0800, Fengguang Wu wrote:
> On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote:
> > On 6/2/2013 6:20 AM, Fengguang Wu wrote:
> > >Greetings,
> > >
> > >FYI, I got this occasionally in some of my machines when testing the
> > >pm/bleeding-edge branch:
> > >
> > >[    0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> > >[    0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > >[    0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
> > >[    0.044000] ..... (found apic 0 pin 2) ...
> > >[    0.048000] ....... failed.
> > >[    0.048000] ...trying to set up timer as Virtual Wire IRQ...
> > >[    0.048000] ..... failed.
> > >[    0.048000] ...trying to set up timer as ExtINT IRQ...
> > >[    0.052000] ..... failed :(.
> > >[    0.052000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the
> > >+'noapic' option.
> > >
> > >Bisect result is unfortunately not reliable..
> > 
> > Can you please check if this is reproducible with the acpi-hotplug
> > branch alone?
> 
> Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect.

FYI, linux-next boots fine, so it should have been fixed somewhere.
Sorry for the noises!

Thanks,
Fengguang

Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

[Rafael J. Wysocki]

On 6/4/2013 2:43 AM, Fengguang Wu wrote:
> On Mon, Jun 03, 2013 at 07:26:24PM +0800, Fengguang Wu wrote:
>> On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote:
>>> On 6/2/2013 6:20 AM, Fengguang Wu wrote:
>>>> Greetings,
>>>>
>>>> FYI, I got this occasionally in some of my machines when testing the
>>>> pm/bleeding-edge branch:
>>>>
>>>> [    0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
>>>> [    0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>>>> [    0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
>>>> [    0.044000] ..... (found apic 0 pin 2) ...
>>>> [    0.048000] ....... failed.
>>>> [    0.048000] ...trying to set up timer as Virtual Wire IRQ...
>>>> [    0.048000] ..... failed.
>>>> [    0.048000] ...trying to set up timer as ExtINT IRQ...
>>>> [    0.052000] ..... failed :(.
>>>> [    0.052000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the
>>>> +'noapic' option.
>>>>
>>>> Bisect result is unfortunately not reliable..
>>> Can you please check if this is reproducible with the acpi-hotplug
>>> branch alone?
>> Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect.
> FYI, linux-next boots fine, so it should have been fixed somewhere.
> Sorry for the noises!

No problem, I'm glad it's been fixed.

Thanks,
Rafael

---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk

Sad Rejonowy Gdansk Polnoc w Gdansku, 
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego, 
numer KRS 101882

NIP 957-07-52-316
Kapital zakladowy 200.000 zl

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Re: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.

[Martin Mokrejs]

Fengguang Wu wrote:
> On Mon, Jun 03, 2013 at 07:26:24PM +0800, Fengguang Wu wrote:
>> On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote:
>>> On 6/2/2013 6:20 AM, Fengguang Wu wrote:
>>>> Greetings,
>>>>
>>>> FYI, I got this occasionally in some of my machines when testing the
>>>> pm/bleeding-edge branch:
>>>>
>>>> [    0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
>>>> [    0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>>>> [    0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
>>>> [    0.044000] ..... (found apic 0 pin 2) ...
>>>> [    0.048000] ....... failed.
>>>> [    0.048000] ...trying to set up timer as Virtual Wire IRQ...
>>>> [    0.048000] ..... failed.
>>>> [    0.048000] ...trying to set up timer as ExtINT IRQ...
>>>> [    0.052000] ..... failed :(.
>>>> [    0.052000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the
>>>> +'noapic' option.
>>>>
>>>> Bisect result is unfortunately not reliable..
>>>
>>> Can you please check if this is reproducible with the acpi-hotplug
>>> branch alone?
>>
>> Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect.
> 
> FYI, linux-next boots fine, so it should have been fixed somewhere.
> Sorry for the noises!

Can you please check it is not present in stable 3.9 and 3.10-rc4?
We might still need to backport the deemed patch. Thank you,
Martin