From: "Joel Soete" <soete.joel@tiscali.be>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] N Class SMP pb ? (follow up)
Date: Thu, 25 Sep 2003 16:56:26 +0200 [thread overview]
Message-ID: <3F5CC41F00008D27@ocpmta3.freegates.net> (raw)
Hi all,
Trying to continue investigation, I puted a printk at the begining of handle_interruption()
to get just the interruption's 'code' managed.
As already mentionned in previous mail that I could read many 6, 15 (but
it seems to be normal: e
en in UP kernel those interruption occurs) but
(most interesting) it is the very first time that I got the message making
failled the kernel:
[...]
handle_interruption(26, ...).
SMP CALL FUNCTION TIMED OUT (CPU=1)
handle_interruption(26, ...).
Stack dump:
[...]
(unfortunately I couldn't grab this dump :( )
Could this be a pb with sync between cpu time ref? (because timeout = jiffies
+ HZ)
I have also a look for where this function is called but never see its return
code tested to launch a 'stack dump' and a stop of system?
Thanks in advance for help,
Joel
PS: I don't know if it is important but the two cpus on this server are located
in slot 1 and 3 (not in slot 1 and 2 as we would logicaly expect)
-------------------------------------------------------------------------
L'Internet rapide, c'est pour tout le monde. Tiscali ADSL, 19,50 Euro
pendant 3 mois! http://reg.tiscali.be/default.asp?lg=fr
next reply other threads:[~2003-09-25 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 14:56 Joel Soete [this message]
2003-09-25 15:41 ` [parisc-linux] N Class SMP pb ? (follow up) Derek Engelhaupt
2003-09-25 23:35 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2003-09-26 15:46 Joel Soete
2003-09-26 16:08 ` Joel Soete
2003-09-26 16:50 ` Grant Grundler
2003-09-27 18:16 ` Joel Soete
2003-09-30 16:31 Joel Soete
2003-09-30 18:50 ` Grant Grundler
2003-10-01 6:48 Joel Soete
2003-10-01 17:20 ` Joel Soete
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=3F5CC41F00008D27@ocpmta3.freegates.net \
--to=soete.joel@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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