All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Gilmore <dennis@ausil.us>
To: sparclinux@vger.kernel.org
Subject: Re: T1000 CPU lockups
Date: Thu, 02 Nov 2006 19:26:40 +0000	[thread overview]
Message-ID: <200611021326.41605.dennis@ausil.us> (raw)
In-Reply-To: <200611011449.37829.dennis@ausil.us>

On Wednesday 01 November 2006 18:12, David Miller wrote:
> From: Dennis Gilmore <dennis@ausil.us>
> Date: Wed, 1 Nov 2006 14:49:37 -0600
>
> > I have had  my T1000 lockup intermittently.  I'm running a vanilla 2.6.18
> > kernel.   I get in the system logs for quite a few of the cpu's
> >
> > Oct 31 20:58:19 daedalus kernel: BUG: soft lockup detected on CPU#21!
> > Oct 31 20:58:19 daedalus kernel: Call Trace:
> > Oct 31 20:58:20 daedalus kernel:  [00000000004319f4]
> > smp_percpu_timer_interrupt+0xd4/0x144
> > Oct 31 20:58:20 daedalus kernel:  [00000000004109d4] tl0_irq14+0x1c/0x20
> > Oct 31 20:58:20 daedalus kernel:  [0000000000468f28]
> > futex_lock_pi+0x130/0x7cc Oct 31 20:58:20 daedalus kernel: 
> > [000000000046a154] do_futex+0xb90/0xbbc Oct 31 20:58:20 daedalus kernel: 
> > [000000000046a6f4]
> > compat_sys_futex+0x11c/0x130
> > Oct 31 20:58:20 daedalus kernel:  [0000000000406c94]
> > linux_sparc_syscall32+0x3c/0x40
> > Oct 31 20:58:20 daedalus kernel:  [00000000701004b0] 0x701004b8
> >
> > after these. while the system stays alive  I cant actually do anything
>
> I think Fabbione was seeing this one too, CC:'d for more testing.
>
> This patch below should fix it, thanks for the most excellent bug
> report.
Thanks for the patch,  its Applied and built,  it has usually taken a few days 
to manifest.  so ill watch it and report back  later. 

-- 
Dennis Gilmore, RHCE
Proud Australian

  parent reply	other threads:[~2006-11-02 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 20:49 T1000 CPU lockups Dennis Gilmore
2006-11-02  0:12 ` David Miller
2006-11-02 17:05 ` Fabio Massimo Di Nitto
2006-11-02 19:26 ` Dennis Gilmore [this message]
2006-11-03  0:03 ` David Miller

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=200611021326.41605.dennis@ausil.us \
    --to=dennis@ausil.us \
    --cc=sparclinux@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 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.