public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Boszormenyi <zboszor@dunaweb.hu>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: Bad page state in process 'nfsd' with xfs
Date: Mon, 01 May 2006 10:07:44 +0200	[thread overview]
Message-ID: <4455C1D0.5060104@dunaweb.hu> (raw)
In-Reply-To: <20060501102440.A1864834@wobbly.melbourne.sgi.com>

Hi,

Nathan Scott írta:
> On Sun, Apr 30, 2006 at 05:19:56PM +0200, Zoltan Boszormenyi wrote:
>   
>> ...
>> Or not. I had an FC3/x86-64 system until two days ago, now I have FC5/86-64.
>>
>> When FC3 was installed I chose to format the partitions to XFS and since 
>> then
>> I had Oopses regularly with or without VMWare modules.
>>     
>
> What was the stack trace for your oops...?
>
> cheers.
>   

I reported some Oopses for earlier kernels, they are here:

http://marc.theaimsgroup.com/?t=113649735300003&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=113166035904096&w=2
http://marc.theaimsgroup.com/?l=fedora-list&m=113611408900505&w=2

With FC3, the last kernel I used was vanilla 2.6.15.
It may be that those above were fixed since.

Best regards,
Zoltán Böszörményi


  reply	other threads:[~2006-05-01  8:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 15:19 Bad page state in process 'nfsd' with xfs Zoltan Boszormenyi
2006-05-01  0:24 ` Nathan Scott
2006-05-01  8:07   ` Zoltan Boszormenyi [this message]
2006-05-01 21:33     ` Nathan Scott
2006-05-01 22:08       ` Zoltan Boszormenyi
  -- strict thread matches above, loose matches on Subject: below --
2006-04-28 20:22 David Greaves
2006-04-30  2:06 ` Nick Piggin
2006-04-30 22:04 ` Nathan Scott
2006-05-01  9:41   ` David Greaves
2006-05-01 15:21     ` Chris Wedgwood

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=4455C1D0.5060104@dunaweb.hu \
    --to=zboszor@dunaweb.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=nickpiggin@yahoo.com.au \
    /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