From: Joel Soete <soete.joel@tiscali.be>
To: Helge Deller <deller@gmx.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Strange newest LAB msg?
Date: Sun, 02 Apr 2006 14:29:23 +0000 [thread overview]
Message-ID: <442FDFC3.8070408@tiscali.be> (raw)
In-Reply-To: <200604021515.04424.deller@gmx.de>
Helge Deller wrote:
> On Sunday 02 April 2006 13:18, Joel Soete wrote:
>
[snip]
>
>>EXT3-fs: mounted filesystem with ordered data mode.
>>VFS: Mounted root (ext3 filesystem) readonly.
>>Freeing unused kernel memory: Badness in smp_call_function at /usr/src/linux-2.6.16.1-pa10/arch/parisc/kernel/smp.c:348
>>Backtrace:
>> [<0000000010112900>] dump_stack+0x18/0x28
>> [<000000001011d9b4>] smp_call_function+0x37c/0x3c0
>> [<0000000010111c5c>] flush_data_cache+0x2c/0x48
>> [<00000000101109a8>] free_initmem+0x68/0x2f8
>> [<000000001010fb20>] init+0x858/0x8c8
>> [<000000001010347c>] ret_from_kernel_
>>(this latest 'Badness in smp_call_function ...' was there but seems to be harmless and the boot continue without showing any more
>>IOREMAP info ;-) )
>
>
> WHAT'S THAT ?
> Do we have some __init too much ?
337 smp_call_function (void (*func) (void *info), void *info, int retry, int wait)
338 {
339 struct smp_call_struct data;
340 unsigned long timeout;
341 static DEFINE_SPINLOCK(lock);
342 int retries = 0;
343
344 if (num_online_cpus() < 2)
345 return 0;
346
347 /* Can deadlock when called with interrupts disabled */
348 WARN_ON(irqs_disabled());
349
> I never tested SMP.
>
No pb ;-)
>
>
>>PS: btw, rm CONFIG_DETECT_SOFTLOCKUP in the config doesn't help on this system ;<(:
>>still hanging (this time without Softlockup msg) after only:
>>top - 09:04:58 up 1 day, 16:26, 3 users, load average: 2.40, 2.26, 2.20
>
>
> I think the softlockups don't really matter.
> Does your box hangs without SMP as well ?
>
well it did with b2k and n4k runing 64bit kernel with CONFIG_DETECT_SOFTLOCKUP=y && # CONFIG_SMP is not set
but I need to verify now without CONFIG_DETECT_SOFTLOCKUP.
(sorry I couldn't do it now but tomorrow morming; ok?
Thanks,
Joel
next prev parent reply other threads:[~2006-04-02 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 15:26 [parisc-linux] Strange newest LAB msg? Joel Soete
2006-03-31 15:54 ` Matthew Wilcox
2006-04-01 7:02 ` Grant Grundler
2006-04-01 7:35 ` Helge Deller
2006-04-01 14:30 ` James Bottomley
2006-04-02 9:29 ` Helge Deller
2006-04-02 11:18 ` Joel Soete
2006-04-02 13:15 ` Helge Deller
2006-04-02 14:29 ` Joel Soete [this message]
2006-04-03 1:28 ` Grant Grundler
2006-04-03 2:02 ` Matthew Wilcox
2006-04-04 12:05 ` James Bottomley
2006-04-05 6:50 ` Helge Deller
2006-04-06 0:02 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 13:20 Joel Soete
2006-04-05 16:43 Joel Soete
2006-04-05 17:02 ` Helge Deller
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=442FDFC3.8070408@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=deller@gmx.de \
--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