Hi Tom,
On 2020-07-29 11:29 a.m., Tom Lendacky wrote:
> On 7/29/20 4:50 AM, Thomas Gleixner wrote:
>> Scott,
>>
>> Scott Branden writes:
>>> On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
Scott Branden writes:
> Bios now updated to latest. Same kernel panic issue. Log below.
>
>>
On 7/29/20 4:50 AM, Thomas Gleixner wrote:
> Scott,
>
> Scott Branden writes:
>> On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
>>> Scott Branden writes:
Bios now updated to latest. Same kernel panic issue. Log below.
I think it is related to power cycling quickly.
Should
Scott,
Scott Branden writes:
> On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
>> Scott Branden writes:
>>> Bios now updated to latest. Same kernel panic issue. Log below.
>>>
>>> I think it is related to power cycling quickly.
>>> Should APIC work if PC power cycled in a few seconds or is tha
8254 timer not connected to IO-APIC
[0.009000] ...trying to set up timer (IRQ0) through the 8259A ...
[0.009000] . (found apic 0 pin 2) ...
[ 0.009000] ... failed.
[0.009000] ...trying to set up timer as Virtual Wire IRQ...
[0.009000] . failed.
[0.009000] ...tryi
Scott,
Scott Branden writes:
> Bios now updated to latest. Same kernel panic issue. Log below.
>
> I think it is related to power cycling quickly.
> Should APIC work if PC power cycled in a few seconds or is that the
> problem?
Yes, emphasis on should. Just to clarify, if you reboot it works a
gt; Occasionally I get the following Kernel panic on boot. This is
>> running on the latest kernel but have seen it previously as well.
>> "Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with
>> apic=debug and send a report."
>>
>> I do
Scott,
Scott Branden writes:
> Occasionally I get the following Kernel panic on boot. This is
> running on the latest kernel but have seen it previously as well.
> "Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with
> apic=debug and send a report."
On Mon, Jul 27, 2020 at 10:20 PM Scott Branden
wrote:
>
> Occasionally I get the following Kernel panic on boot. This is running on
> the latest kernel but have seen it previously as well.
> "Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with
> api
Occasionally I get the following Kernel panic on boot. This is running on the
latest kernel but have seen it previously as well.
"Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with
apic=debug and send a report."
I don't know who I am support to send a rep
done, bug number #7884
Cheers,
Eamonn
On Thu, 2007-01-25 at 09:17 +, Luming Yu wrote:
> > I didn't get a chance to try the -mm patch, but booting with acpi=off
> > works - other than no acpi, of course :)
> >
> > What now?
> Well, this should be ACPI interrupt configure issue.
> Please feel f
I didn't get a chance to try the -mm patch, but booting with acpi=off
works - other than no acpi, of course :)
What now?
Well, this should be ACPI interrupt configure issue.
Please feel free to enter a bug on bugzilla.kernel.org.
And, post acpidump output, /proc/interrupts ,lspci -vvx, dmesg for
Hi,
I didn't get a chance to try the -mm patch, but booting with acpi=off
works - other than no acpi, of course :)
What now?
Cheers,
Eamonn
On Thu, 2007-01-25 at 05:33 +, Luming Yu wrote:
> On 1/25/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
> > I've also just found bug #7820 on bugzilla
On 1/25/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
I've also just found bug #7820 on bugzilla which has a patch which may
address this issue from Ingo.
I'll give that a shot as well.
Yes, that patch workaround the problem. But it is just a workaround.
It would be much helpful to others by
I've also just found bug #7820 on bugzilla which has a patch which may
address this issue from Ingo.
I'll give that a shot as well.
Cheers,
Eamonn
On Wed, 2007-01-24 at 23:21 +0800, Luming Yu wrote:
> what about acpi=off?
>
> On 1/24/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
>
Hi,
I will give that a go tonight - it's my home system.
Cheers,
Eamonn
On Wed, 2007-01-24 at 23:21 +0800, Luming Yu wrote:
> what about acpi=off?
>
> On 1/24/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I can't get any kernel up to 2.6.20-rc5 to boot without using noapic on
>
what about acpi=off?
On 1/24/07, Eamonn Hamilton <[EMAIL PROTECTED]> wrote:
Hi,
I can't get any kernel up to 2.6.20-rc5 to boot without using noapic on
an ABIT KN9-Ultra with a dual-core Athlon.
I booted with apic=debug as suggested and got the following :
ENABLING IO-APIC IRQs
.. TIMER: vect
Hi,
I can't get any kernel up to 2.6.20-rc5 to boot without using noapic on
an ABIT KN9-Ultra with a dual-core Athlon.
I booted with apic=debug as suggested and got the following :
ENABLING IO-APIC IRQs
.. TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
.. MP-BIOS bug: 8254 timer not connecte
On Mon, 8 Jan 2007, Tobias Diedrich wrote:
>
> Yinghai Lu wrote:
> > Please check the latest version. ( 01/02/2007)
>
> Works for me, with both BIOS versions / routing variants.
Yinghai, Eric, can you please send me the latest version with
(a) explanations for the changelogs
(b) sign-off's (
Yinghai Lu wrote:
> Please check the latest version. ( 01/02/2007)
Works for me, with both BIOS versions / routing variants.
patches/series:
patch-2.6.20-rc4
patch-2.6.19-rc3-nokmem
myconfig
ccache
timer_01022007.diff
hpet-quirk
dmesg diff:
--- dmesg-20070108-2.6.20-rc4-bios-0402 2007-01-08 01:5
Please check the latest version. ( 01/02/2007)
YH
[PATCH] x86_64: check_timer with io apic setup before try_apic_pin
In the check_timer, it forget to set up the io apic before try_apic_pin for
timer. So add set_try_apic_pin to set up the io apic pin. otherwise the
try_apic_pin will not work.
a
Please check the revised patch
YH
[PATCH] x86_64: check_timer with io apic setup before try_apic_pin
add io apic setup before try_apic_pin for check_timer
also add remove_irq_to_pin call in io_apic.c
cc: Andi Kleen <[EMAIL PROTECTED]>
cc: Eric W. Biederman <[EMAIL PROTECTED]>
Signed-off-by: Yi
"Lu, Yinghai" <[EMAIL PROTECTED]> writes:
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 21, 2006 12:47 PM
> To: Lu, Yinghai
>>> +static int add_irq_entry(int type, int irqflag, int bus, int irq,
> int apic, int
>>> pin)
>
>>This is fai
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 12:47 PM
To: Lu, Yinghai
>> +static int add_irq_entry(int type, int irqflag, int bus, int irq,
int apic, int
>> pin)
>This is fairly sane but probably belongs in mptable.c as a helper.
"Yinghai Lu" <[EMAIL PROTECTED]> writes:
> On 12/19/06, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>> So the pin2 case should be tested right after the pin1 case as we do
>> currently. On most new boards that will be a complete noop.
>>
>> But it is better than our current blind guess at using
Yinghai Lu wrote:
> On 12/19/06, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> >So the pin2 case should be tested right after the pin1 case as we do
> >currently. On most new boards that will be a complete noop.
> >
> >But it is better than our current blind guess at using ExtINT mode.
> >
> >I f
On 12/19/06, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
So the pin2 case should be tested right after the pin1 case as we do
currently. On most new boards that will be a complete noop.
But it is better than our current blind guess at using ExtINT mode.
I figure after we try what the BIOS has
"Yinghai Lu" <[EMAIL PROTECTED]> writes:
> On 12/18/06, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>> Thanks. The bug is simply that the new code doesn't setup the
>> ioapic for the cases it intends to test. But it does clear out
>> the original programming. So if the normal good case doesn't
On 12/18/06, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
Thanks. The bug is simply that the new code doesn't setup the
ioapic for the cases it intends to test. But it does clear out
the original programming. So if the normal good case doesn't work the
code is going to have problems.
Please
Tobias Diedrich <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>> Could you try removing the clear_IO_APIC_pin from try_io_apic_pin.
>>
>> This isn't a complete fix but I believe for your hardware it will
>> fix the problem and it points at what the real fix is.
>>
>> Not properly progr
Tobias Diedrich wrote:
> I can also report, that updating the BIOS to version 0609 (released
> last week or so, also adds the long-missing HPET support) also makes
> the problem go away since the first testcase then already works.
> I'm currently running with the BIOS downgraded to version 0402.
Eric W. Biederman wrote:
> Tobias Diedrich <[EMAIL PROTECTED]> writes:
>
> > Linus Torvalds wrote:
> >
> >> Your dmesg is kind of interesting:
> >>
> >> ..TIMER: trying IO-APIC=0 PIN=0 with 8259 IRQ0 enabled(7)APIC error on
> >> CPU0:
> > 04(40)
> >> .. failed
> >>
> >> where that APIC error o
Tobias Diedrich <[EMAIL PROTECTED]> writes:
> Linus Torvalds wrote:
>
>> Your dmesg is kind of interesting:
>>
>> ..TIMER: trying IO-APIC=0 PIN=0 with 8259 IRQ0 enabled(7)APIC error on CPU0:
> 04(40)
>> .. failed
>>
>> where that APIC error on CPU0 seems to be a "Send accept error" and "Send
>
On Sunday 17 December 2006 00:22, Eric W. Biederman wrote:
> Actually can anyone tell me how try_apic_pin is supposed to work at
> all?
>
> It doesn't appear to be programming the io_apic.
magic:-)
ACPI can't even _describe_ the scenarios being tried by check_timer(),
which is trying to navigat
On Sun, 17 Dec 2006, Tobias Diedrich wrote:
>
> BTW, I'm also wondering if this secondary Oops is supposed to happen:
Well, if the timer doesn't work, then the NMI watchdog will trigger. So
it's "supposed" to happen in the sense that yeah, it's kind of expected,
but it's really bsically just
Linus Torvalds wrote:
> Your dmesg is kind of interesting:
>
> ..TIMER: trying IO-APIC=0 PIN=0 with 8259 IRQ0 enabled(7)APIC error on CPU0:
> 04(40)
> .. failed
>
> where that APIC error on CPU0 seems to be a "Send accept error" and "Send
> illegal vector" thing. I think we actually got the i
ndering if this secondary Oops is supposed to happen:
http://www.tdiedrich.de/~ranma/2.6.20-rc1-oops2.jpg
I guess the NMI watchdog is never disabled after the test failed?
|[68.908000] Kernel panic - not syncing: IO-APIC + timer doesn't work! Try
using the 'noapic' kernel
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Sun, 17 Dec 2006, Tobias Diedrich wrote:
>>
>> No such luck, it still panics and the APIC error is also unchanged.
>
> Ok. I don't see anything wrong off-hand, but I'll keep the patch in the
> tree in the hopes that Andi and/or Eric can see what's
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Sun, 17 Dec 2006, Tobias Diedrich wrote:
>>
>> No such luck, it still panics and the APIC error is also unchanged.
>
> Ok. I don't see anything wrong off-hand, but I'll keep the patch in the
> tree in the hopes that Andi and/or Eric can see what's
On Sun, 17 Dec 2006, Tobias Diedrich wrote:
>
> No such luck, it still panics and the APIC error is also unchanged.
Ok. I don't see anything wrong off-hand, but I'll keep the patch in the
tree in the hopes that Andi and/or Eric can see what's wrong and solve it.
If we don't find a solution, I
On Sun, 17 Dec 2006, Tobias Diedrich wrote:
>
> With commit b0268726 backed out, 2.6.20-rc1 boots fine.
Ok. It's sad, because that thing really did clean stuff up, and seemed
like a nice and robust approach.
Your dmesg is kind of interesting:
..TIMER: trying IO-APIC=0 PIN=0 with 8259 IRQ0 ena
On Sat, 16 Dec 2006, Tobias Diedrich wrote:
>
> 2.6.20-rc1 won't boot with the error message "IO-APIC + timer
> doesn't work! Try using the 'noapic' kernel parameter".
> However, IO-APIC seems to work just fine with 2.6.19-rc6 and I'd
> rath
On Tue, 15 Feb 2005, Joseph Cosby wrote:
> Hi,
> Using VMWare 4 with a 2.6.9 kernel I get "IO-APIC + timer doesn't work!" As
> suggested, the noapic option fixes the problem. This resulted after adding
> APIC support to my kernel. My problem is, I need APIC support t
ubject: Re: 2.6.9 IO-APIC + timer doesn't work! with VMWare 4
Date: Tue, 15 Feb 2005 15:58:59 -0500
On Tue, 2005-02-15 at 13:29 -0700, Joseph Cosby wrote:
> Hi,
> Using VMWare 4 with a 2.6.9 kernel I get "IO-APIC + timer doesn't
work!"
> As suggested, the noapic
On Tue, 2005-02-15 at 13:29 -0700, Joseph Cosby wrote:
> Hi,
> Using VMWare 4 with a 2.6.9 kernel I get "IO-APIC + timer doesn't work!"
> As suggested, the noapic option fixes the problem. This resulted after
> adding APIC support to my kernel. My problem is, I need
Hi,
Using VMWare 4 with a 2.6.9 kernel I get "IO-APIC + timer doesn't work!"
As suggested, the noapic option fixes the problem. This resulted after
adding APIC support to my kernel. My problem is, I need APIC support to boot
on a separate, non-VMWare machine, and I need to keep
45 matches
Mail list logo
