From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: Kernel crash in interrupt handler: nested interrupt breaks saved %eip?
Date: Fri, 9 Jul 2004 15:34:31 +0400 [thread overview]
Message-ID: <200407091534.35944@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <200407090031.09750.vda@port.imtp.ilyichevsk.odessa.ua>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > EIP: 0060:[<c02262a2>] Tainted: P
> ^^^^^^^^^^
> What was that? Your lsmod please?
That's caused by vmware bodules; I don't think they affect the situation.
> > So I think that an interrupt happened at that time, and %eip was
> > broken inside the handler.
>
> You can istrument your kernel to check for that on every interrupt
> and printk a KERN_NOTICE message if eip was changed.
What's the correct place for those? do_IRQ()? Or probably some other places
also (APIC timer interrupt handler? exception handler?)
Unpleasant situation is that the problem is on a production server, which
should be operational 24/7 ... However, probably I'll try to install an
instrumented kernel in the next kernel upgrade.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA7oLLsTbPknTfAB4RAhGvAJ9n9246V7cMntgPnwmKBI/pcR0XGACeMnSY
fuIaVh1yCssaJC0PWdHd7sE=
=/8fI
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-07-09 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 19:51 Nikita V. Youshchenko
[not found] ` <200407090031.09750.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-09 11:34 ` Nikita V. Youshchenko [this message]
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=200407091534.35944@zigzag.lvk.cs.msu.su \
--to=yoush@cs.msu.su \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
Powered by JetHome