xfs
[Top] [All Lists]

Re: BUG: soft lockup detected on CPU#1!

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: BUG: soft lockup detected on CPU#1!
From: <raksac@xxxxxxxxx>
Date: Thu, 19 Feb 2009 00:04:49 -0800 (PST)
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1235030689; bh=pKX5jvCFYcfCRe9ewFHg/SS3UtLYGyu2KVUV3VlV2jQ=; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nUdErY+O9ZYi7jJ41phbSgV6I8xrBfeqXPmABizrv0ABlRXH2IYxf46GsYJ/+8W9mt05n6kOoaGFpZOQhklPI4OJC3qj/q286FyX0M0B6h5I2cQPoE4tN2vH7Cc+XdvcqFCQVJCgRH1+orxxksoYGRTtWuqpIpuO3UCWSpL2YCg=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Fu1ZHcBu/zSk5LVwdku8sIXShImCL6lFfvG39lr6bMmZUGrgJcDBlSBtqkFFoaJ1U3Gq4cN3Kol2ML6TChHvADkiFJw0qW7mGSi7MzqtMzSPUjuh9kZs4ae09+R9uAXSf4ePN08n9CGKx18osi+BH85tepE/auSz1NiSQGsZhLE=;
In-reply-to: <4994FD8C.5020303@xxxxxxxxxxx>
I think I am getting closer now. Can you suggest what
to look for from this oops -


Stack traceback for pid 192
0xad12f030      192       11  1    0   R  0xad12f1d0
*xfsdatad/0
esp        eip        Function (args)
0xaff37eec 0x7815007b map_vm_area+0xc3
0xaff37ef0 0x7814007b find_get_pages_contig+0x3d
0xaff37ef8 0x78156c04 free_block+0x41
0xaff37f20 0x78156d9b cache_flusharray+0x63
0xaff37f3c 0x78156b4e kmem_cache_free+0x52
0xaff37f4c 0x7814296f mempool_free_slab+0xb
0xaff37f50 0x78142954 mempool_free+0x60
0xaff37f60 0x781f429f xfs_destroy_ioend+0x4e
0xaff37f6c 0x781f43d0 xfs_end_bio_read+0x5
0xaff37f70 0x78128498 run_workqueue+0x71
0xaff37f74 0x781f43cb xfs_end_bio_read
0xaff37f8c 0x78128634 worker_thread+0xd9
0xaff37fac 0x781164c0 default_wake_function
0xaff37fc8 0x7812855b worker_thread
0xaff37fcc 0x7812ad7a kthread+0xc1
0xaff37fd8 0x7812acb9 kthread
0xaff37fe4 0x781036df kernel_thread_helper+0x7

Thanks,
Rakesh

--- Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:

> raksac@xxxxxxxxx wrote:
> > Guys,
> > 
> > Thank you for taking the time to write. Having
> said
> > where I stand and we are kind of on the same page.
> Is
> > there something I can expect which would put me on
> a
> > track of nailing down the problem. It maybe a wild
> > goose chase but something that I can start with
> would
> > be much appreciated.
> 
> Just random debugging thoughts...
> 
> Try stock 2.6.28.4, to see if you have the same
> problem.  If so, and
> esp. if you also see it on 2.6.29, then you'll get a
> lot more attention
> here.  :)
> 
> If not, then it's something with your backport most
> likely.  Figure out
> what you had to backport and see if it's possibly
> causing the error(s).
> 
> If it's locked up, try sysrq-w (echo w >
> /proc/sysrq-trigger) and look
> at dmesg to see if other threads are locked against
> it.  Figure out why.
> 
> On the oops try memory debugging etc, see if you're
> referencing freed
> memory, using corrupt lists, etc.
> 
> Look for other errors in the logs prior to this.
> 
> See if your filesystem is corrupted.
> 
> Bug Red Hat for XFS support, assuming you're
> actually buying RHEL5
> support from them.  :)
> 
> > Unfortunately there is no distro which gets closer
> to
> > where mainline lives today. Reading the changelog
> > there are several problems that I have already
> come
> > across and has convincingly driven me to take on
> this
> > task.
> 
> well certainly there are distros with kernels newer
> than 2.6.18, but it
> depends on your needs & goals I guess.
> 
> Good luck,
> -Eric
> 
> -Eric
> 



      

<Prev in Thread] Current Thread [Next in Thread>