Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: "Michael S. Zick" <mszick@wolfbutter.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] BUG 2.6.11-rc4-pa1 XFS data page fault
Date: Thu, 17 Feb 2005 23:23:12 -0700	[thread overview]
Message-ID: <20050218062312.GA11968@colo.lackof.org> (raw)
In-Reply-To: <200502170653.52415.mszick@wolfbutter.com>

On Thu, Feb 17, 2005 at 06:53:52AM -0600, Michael S. Zick wrote:
> I am tracking a timing and/or race condition(s) with x86-udev.
> Debian doesn't use it yet, they still have a hard disk based /dev.
> But it is not a compile time option.
> If you have a 2.6.+ kernel, you have it.
> 
> Try turning it off with the command line option: 'noudev'

I thought this helped at first.  (2.6.11-rc4-pa1)
Could run spew+"make -j4" over xfs without crashing the box (panic).

Then I rebooted with a freshly built kernel (and "noudev")
and right away when I start spew on the XFS file system I get:

Kernel Fault: Code=26 regs=00000000fd0b0de0 (Addr=00000000000000c8)
...
 IAOQ[0]: xfs_btree_init_cursor+0x70/0x1b8 [xfs]
 IAOQ[1]: xfs_btree_init_cursor+0x8c/0x1b8 [xfs]
 RP(r2): xfs_btree_init_cursor+0x58/0x1b8 [xfs]

The system panics with and without the xfs patches Joel pointed me at.

The only difference in the .config was sym2 driver IOMAPPED.
I had it enabled (using IO Port space) and now disable it
since I really want MMIO space. I'm very skeptical this is
related to the problem.


> If your compile time options include devfs, try turning it 
> off also.  Use the command line option: 'nodevfs'

I don't use devfs. Willy won't let me. :^P

> In my case, for kernels 2.6.8, 2.6.9, 2.6.10 and 2.6.11 -
> If I boot from slow devices (cdrom, zip disk) everything is
> fine, If I boot from fast devices (hard disk) - something isn't
> getting setup the same.

Is there a difference in the how the devices are used?
ie. serialized vs. multiple IOs in flight at the same time?

I didn't start hitting problems until I lauched a second job
on the same file system.

thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-02-18  6:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42075CE800004656@mail-6-bnl.tiscali.it>
     [not found] ` <200502170653.52415.mszick@wolfbutter.com>
     [not found]   ` <20050217210915.GB1081@colo.lackof.org>
2005-02-18  1:00     ` [parisc-linux] BUG 2.6.11-rc4-pa1 XFS data page fault Michael S. Zick
2005-02-18  6:23   ` Grant Grundler [this message]
2005-02-18  9:28     ` Thibaut VARENE
2005-02-18 14:07       ` Michael S. Zick
     [not found]       ` <20050219022808.GA28925@colo.lackof.org>
2005-02-19 10:17         ` Michael S. Zick
2005-02-21 16:58           ` Matthew Wilcox
2005-02-18 17:35 Joel Soete
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16  6:55 Grant Grundler
     [not found] ` <4208D51500003293@mail-5-bnl.tiscali.it>
2005-02-16  7:45   ` Grant Grundler
2005-02-17  4:06 ` Carlos O'Donell
2005-02-19 22:27 ` Grant Grundler
2005-02-21  0:04   ` Grant Grundler

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=20050218062312.GA11968@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=mszick@wolfbutter.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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