| To: | Chris Seufert <seufert@xxxxxxxxx> |
|---|---|
| Subject: | Re: Kernel Ooops |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 6 Sep 2006 08:30:28 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <2260b150609050427p3123cb85q5af484d8b907e6ac@xxxxxxxxxxxxxx>; from seufert@xxxxxxxxx on Tue, Sep 05, 2006 at 09:27:04PM +1000 |
| References: | <2260b150609050427p3123cb85q5af484d8b907e6ac@xxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Sep 05, 2006 at 09:27:04PM +1000, Chris Seufert wrote: > I have had this one before, and i had assumed it had been fixed. > > System seems very stable running ext3, so i dont 'think' its hardware > related, but i am begining to wonder. This is fixed, what kernel version are you using? (it was fixed in -rc5/6 IIRC). > RIP [<ffffffff8031dd16>] xfs_btree_init_cursor+0x48/0x1bd cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: review: propogate return codes from flush routines, Stewart Smith |
|---|---|
| Next by Date: | race in xfs_rename? (fwd), Nathan Scott |
| Previous by Thread: | TAKE 955939 - writing by splice() doesn't work in 2.6.17+, David Chinner |
| Next by Thread: | Re: Kernel Ooops, Chris Seufert |
| Indexes: | [Date] [Thread] [Top] [All Lists] |