public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Harald Dunkel" <harald.dunkel@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.9-rc4: Kernel BUG at timer:414
Date: Thu, 14 Oct 2004 18:36:37 +0200	[thread overview]
Message-ID: <416EAB15.6030304@t-online.de> (raw)

Hi folks,

I got a kernel panic on amd64:


Kernel BUG at timer:414
invalid operand: 0000 [1] PREEMPT
CPU 0
Modules linked in: ...
Pid: 3711, comm: mktemp Not tainted 2.6.9-rc4
RIP: 0010: ...{cascade+46}
:
:
Process mktemp (pid 3711, ...)
Stack: ...
Call Trace: <IRQ>
             <...>{run_timer_softirq}
             <...>{__do_softirq+83}
             <...>{do_softirq+53}
             <...>{do_IRQ+383}
             <...>{ret_from_intr+0}
             <EOI>
Code 0f 0b 66 b1 2f 80 ff ff ff ff9e 01 66 66 90 66 66 90 48 8b
RIP <...>{cascade+46}
  <0> Kernel panic - not syncing: Aiee, killing interrupt handler!


Please excuse that I did not write down every hex code
of the error message.


Regards

Harri

             reply	other threads:[~2004-10-14 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 16:36 Harald Dunkel [this message]
2004-10-15 11:44 ` 2.6.9-rc4: Kernel BUG at timer:414 Harald Dunkel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=416EAB15.6030304@t-online.de \
    --to=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox