All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] "BUG: soft lockup detected on CPU#0" on recent 64bit 	k-2.6.16 (up or smp)
Date: Sun, 02 Apr 2006 11:23:17 +0000	[thread overview]
Message-ID: <442FB425.6000308@tiscali.be> (raw)
In-Reply-To: <IX00XW$54609265F67FD22980DB5BAA9486A0DB@scarlet.be>



Joel Soete wrote:
> Hello pa*,
> 
> [snip]
> 
>>also noticed on n4k runing k-2.6.16-pa0 64bit smp kernel:
>>BUG: soft lockup detected on CPU#0!
>>
> 
> [...]
> 
>> IAOQ[0]: _read_lock+0x18/0x30
>> IAOQ[1]: _read_lock+0x8/0x30
>> RP(r2): send_group_sig_info+0x3c/0xb0
>>
> 
> This kind of hung re-occured on this n4k (64bit smp kernel 2.6.16-pa8);
> 
> I just grab the piminfo but useless:
> [...]
> Parse IAOQ = 0x000000ffff80ff3c for CPU[1]
> 
> Func: _end, Off: 0xffef1f1244, Addr: 0xffff80ff3c
> [...]
> 
> Parse IAOQ = 0x00000000000006c4 for CPU[3]
> 
> [...]
> 
> Sorry,
>     Joel
> 
> PS: I just start the same test but without CONFIG_DETECT_SOFTLOCKUP :<?
> 
well never the less system still hanging after only:
top - 09:04:58 up 1 day, 16:26,  3 users,  load average: 2.40, 2.26, 2.20

training the same test (kernel build in loop)
(just this time without "BUG: soft lockup detected on CPU#0!" msg?)

Thanks,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-04-02 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 15:41 Re:[parisc-linux] "BUG: soft lockup detected on CPU#0" on recent 64bit k-2.6.16 (up or smp) Joel Soete
2006-04-02 11:23 ` Joel Soete [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13  6:45 Joel Soete
2006-04-16 20:04 ` [parisc-linux] " Joel Soete
2006-03-24 11:30 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=442FB425.6000308@tiscali.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.