All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: raksac@yahoo.com
Cc: xfs@oss.sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!
Date: Wed, 11 Feb 2009 04:21:21 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0902110420520.13264@p34.internal.lan> (raw)
In-Reply-To: <407126.80177.qm@web30205.mail.mud.yahoo.com>


On Tue, 10 Feb 2009, raksac@yahoo.com wrote:

>
> Hello,
>
> I am running the 2.6.28 based xfs kernel driver on a
> custom kernel with following kernel config enabled.
>
> CONFIG_PREEMPT
> CONFIG_DETECT_SOFTLOCKUP
>
> Running the following xfsqa causes a soft lockup. The
> configuration is a x86 with Hyperthreading, 4GB RAM
> and a AHCI connected JBOD. Its 100% reproducible.
>
> Any suggestions/inputs on where to start debugging the
> problem would be much appreciated.
>
> #! /bin/sh
> # FS QA Test No. 008
> #
> # randholes test
> #
>
> BUG: soft lockup detected on CPU#1!
> [<4013d525>] softlockup_tick+0x9c/0xaf
> [<40123246>] update_process_times+0x3d/0x60
> [<401100ab>] smp_apic_timer_interrupt+0x52/0x58
> [<40103633>] apic_timer_interrupt+0x1f/0x24
> [<402a1557>] _spin_lock_irqsave+0x48/0x61
> [<f8b8fe30>] xfs_iflush_cluster+0x16d/0x31c [xfs]
> [<f8b9018b>] xfs_iflush+0x1ac/0x271 [xfs]
> [<f8ba49a1>] xfs_inode_flush+0xd6/0xfa [xfs]
> [<f8bb13c8>] xfs_fs_write_inode+0x27/0x40 [xfs]
> [<401789d9>] __writeback_single_inode+0x1b0/0x2ff
> [<40101ad5>] __switch_to+0x23/0x1f9
> [<40178f87>] sync_sb_inodes+0x196/0x261
> [<4017920a>] writeback_inodes+0x67/0xb1
> [<401465df>] wb_kupdate+0x7b/0xe0
> [<40146bc3>] pdflush+0x0/0x1b5
> [<40146ce1>] pdflush+0x11e/0x1b5
> [<40146564>] wb_kupdate+0x0/0xe0
> [<4012be6d>] kthread+0xc1/0xec
> [<4012bdac>] kthread+0x0/0xec
> [<401038b3>] kernel_thread_helper+0x7/0x10
> =======================
>
> Thanks,
> Rakesh
>
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>

There were some pretty nasty bugs in 2.6.28 for XFS, can you reproduce it on 
2.6.28.4?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-02-11  9:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  7:16 BUG: soft lockup detected on CPU#1! raksac
2009-02-11  9:21 ` Justin Piszcz [this message]
2009-02-11 23:33   ` raksac
2009-02-11 23:36     ` Justin Piszcz
2009-02-12  9:22       ` raksac
2009-02-12 21:55         ` Dave Chinner
2009-02-12 21:59           ` raksac
2009-02-12 22:10             ` Eric Sandeen
2009-02-12 22:16               ` raksac
2009-02-13  4:56                 ` Eric Sandeen
2009-02-19  8:04                   ` raksac
2009-02-13  9:32                 ` Michael Monnerie
2009-02-11 23:34   ` raksac
2009-02-12 21:49 ` Dave Chinner
2009-02-12 21:55   ` raksac
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11  7:57 Rakesh
2007-05-02 16:17 brendan powers
2006-07-17 12:52 Jochen Heuer
2006-07-17 14:30 ` Steven Rostedt
2006-07-17 14:48   ` Jochen Heuer
2006-07-21 22:53     ` Jochen Heuer
2006-07-24 13:20       ` Steven Rostedt
2006-07-21 22:58   ` Jochen Heuer

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=alpine.DEB.1.10.0902110420520.13264@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=raksac@yahoo.com \
    --cc=xfs@oss.sgi.com \
    /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.