public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: <raksac@yahoo.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!
Date: Thu, 12 Feb 2009 01:22:16 -0800 (PST)	[thread overview]
Message-ID: <235313.30733.qm@web30205.mail.mud.yahoo.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0902111835420.27406@p34.internal.lan>


Hi Justin,

Yes it is a 2.6.18 rhel5 based custom kernel but the
XFS driver is a back port from the 2.6.28.4

Thanks,
Rakesh

--- Justin Piszcz <jpiszcz@lucidpixels.com> wrote:

> 
> On Wed, 11 Feb 2009, raksac@yahoo.com wrote:
> 
> >
> > Hi Justin,
> >
> > Thank you for the pointer. Well as suggested I did
> and
> > now the xfsqa goes upto test 011
> >
> > #! /bin/sh
> > # FS QA Test No. 011
> > #
> > # dirstress
> >
> > but dies with a oops. Any suggestions?
> >
> > Here is the oops trace -
> >
> > BUG: unable to handle kernel NULL pointer
> dereference
> > at virtual address 00000000
> > printing eip:
> > f8bd02c2
> > *pde = e7167067
> > Oops: 0000 [#1]
> > PREEMPT SMP
> > last sysfs file:
> >
>
/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002e/temp1_input
> > Modules linked in: xfs sg sunrpc m24c02 pca9554
> > pca9555 mcp23016 lm85 hwmon_vid i2c_i801 i2c_core
> > midplane uhci_hcd sk98lin tg3 e1000 mv_sata sd_mod
> > ahci libata
> > CPU:    1
> > EIP:    0060:[<f8bd02c2>]    Not tainted VLI
> > EFLAGS: 00010286   (2.6.18.rhel5 #2)
> > EIP is at xfs_iget_core+0x4d6/0x5e9 [xfs]
> 
> Can you show uname -a output?
> 
> EFLAGS: 00010286   (2.6.18.rhel5 #2)
>                      ^^^^^^^^^^^^
> 



      

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

  reply	other threads:[~2009-02-12 16:29 UTC|newest]

Thread overview: 19+ 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
2009-02-11 23:33   ` raksac
2009-02-11 23:36     ` Justin Piszcz
2009-02-12  9:22       ` raksac [this message]
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
     [not found] <20060717125216.GA15481@planetzork.ping.de>
     [not found] ` <1153146608.1218.9.camel@localhost.localdomain>
2006-07-17 14:48   ` Jochen Heuer
2006-07-21 22:53     ` Jochen Heuer
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=235313.30733.qm@web30205.mail.mud.yahoo.com \
    --to=raksac@yahoo.com \
    --cc=jpiszcz@lucidpixels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox