From: Robert Love <rml@tech9.net>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings
Date: 29 Mar 2003 17:11:47 -0500 [thread overview]
Message-ID: <1048975906.13757.7.camel@localhost> (raw)
In-Reply-To: <004201c2f63c$25d4aa00$030aa8c0@unknown>
On Sat, 2003-03-29 at 16:42, Shawn Starr wrote:
> How can I go about debugging this? How can I find the path causing
> the problem?
Begin by finding out where the EIP is. It should be a spin_lock(). The
oops says it is kernel/timer.c:258.
This line is a double locking of an already-locked lock. So find where
the initial lock was. The oops said that is kernel/timer.c:398.
Look at the call chain (from the oops) from the first to the second
lock. Someone assumed it could not happen. Obviously they were wrong.
Robert Love
next prev parent reply other threads:[~2003-03-29 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 20:45 [PANIC][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings Shawn Starr
2003-03-29 21:15 ` Robert Love
2003-03-29 21:42 ` [OOPS][2.5.66bk3+] " Shawn Starr
2003-03-29 22:11 ` Robert Love [this message]
2003-03-29 22:28 ` Andrew Morton
2003-03-29 22:33 ` Shawn Starr
2003-03-29 22:34 ` Shawn Starr
2003-03-31 2:52 ` [PANIC][2.5.66bk3+] " Zwane Mwaikambo
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=1048975906.13757.7.camel@localhost \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.net \
/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