From: Rabeeh Khoury <rabeeh@il.marvell.com>
To: linux-scsi@vger.kernel.org
Subject: NMI Watchdog timeout problem
Date: Wed, 20 Aug 2003 14:53:17 +0300 [thread overview]
Message-ID: <3F43612D.5060909@il.marvell.com> (raw)
Hi All,
I'm having a problem with my SCSI detect function.
I have a dual CPU machine running kernel 2.4.19-SMP and I have two cards
in the system (our own cards that we do internal development on).
The detect function (as pointed to by the host template data structure)
takes long time for initializing 8 drives connected to both cards (~8
seconds) ; this is part of the initialization sequence and a must to do
path.
During this time the detect function goes to first card, ioremaps the
PCI BAR spaces and initilzlies 4 drives (~4 seconds) then goes to the
other card and ioremaps the PCI BAR space and then initializes the other
4 drives (another ~4 seconds).
What I'm seeing is that in random places within the detect function I
get an NMI watchdog timer and the system crashes.
Notes -
1.. The detect function doesn't disable interrupts on local CPU or any
other CPU.
2.. The driver works perfectly on a single CPU machine.
Can any one please explain to me why the watchog timer expires, even
though interrupts are enabled ?
Do you have any suggestion how to workaround this ?
Thank you,
Rabeeh
reply other threads:[~2003-08-20 11:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F43612D.5060909@il.marvell.com \
--to=rabeeh@il.marvell.com \
--cc=linux-scsi@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