| To: | Marc Lehmann <schmorp@xxxxxxxxxx> |
|---|---|
| Subject: | Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 9 Aug 2011 21:35:36 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20110809091643.GA26036@xxxxxxxxxx> |
| References: | <20110806122556.GB20341@xxxxxxxxxx> <20110806142005.GG3162@dastard> <20110807014237.GA18909@xxxxxxxxxx> <20110807102625.GJ3162@dastard> <20110809091643.GA26036@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Aug 09, 2011 at 11:16:43AM +0200, Marc Lehmann wrote: > This just in, this was on screen, xfs_fsr was active at the time, kernel > is tainted: > > [248359.646330] CPU 1 > [248359.646326] last sysfs file: /sys/devices/virtual/net/lo/operstate > [248359.646323] Oops: 0000 [#1] SMP > [248359.646319] PGD 8b43067 PUD 1bc63067 PMD 0 > [248359.646292] IP: [<ffffffffa13371ab>] xfs_trans_log_inode+0xb/0x2f [xfs] > [248359.646285] BUG: unable to handle kernel NULL pointer dereference at > 0000000000000018 And the event trace to go along with the xfs-fsr run? I don't need to know the dmesg output - I need the information in the event trace from the xfs-fsr run when the problem occurs.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr, Marc Lehmann |
|---|---|
| Next by Date: | Re: [PATCH 1/2] vfs: split generic splice code from i_mutex locking, Jan Kara |
| Previous by Thread: | Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr, Marc Lehmann |
| Next by Thread: | Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr, Marc Lehmann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |