From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: jfs problem
Date: Mon, 17 Nov 2008 23:47:47 -0600 [thread overview]
Message-ID: <49225703.7060905@shaw.ca> (raw)
In-Reply-To: <e38d12ff0811171408k2e77cf9bt6f89e448194ebe32@mail.gmail.com>
Andrey Vul wrote:
> I have a JFS problem occuring randomly. The hardware that this happens
> on is an Asus M50VM laptop.
>
> /dev/sda5 is mounted on /
>
> Kernel version is 2.6.27.4 with dm-bbr (device mapper - bad block
> relocation), fbcondecor, and squashfs patches.
>
> dmesg:
> [ 130.405776] DMAR:[DMA Write] Request device [00:1f.2] fault addr fff9f000
> [ 130.405780] DMAR:[fault reason 05] PTE Write access is not set
> [ 130.405828] ERROR: (device sda5): diRead: i_ino != di_number
> [ 130.406133] ERROR: (device sda5): remounting filesystem as read-only
> [ 130.406136]
> [ 130.406146] jfs_lookup: iget failed on inum 188808
> [ 131.212899] DMAR:[DMA Write] Request device [00:1f.2] fault addr fff9f000
> [ 131.212903] DMAR:[fault reason 05] PTE Write access is not set
> [ 131.212962] ERROR: (device sda5): stack overrun in dtSearch!
> [ 131.212968] btstack dump:
> [ 131.212972] bn = 0, index = 0
> [ 131.212975] bn = 5402c5, index = 0
> [ 131.212979] bn = 0, index = 0
> [ 131.212982] bn = 5402c5, index = 0
> [ 131.212985] bn = 0, index = 0
> [ 131.212988] bn = 5402c5, index = 0
> [ 131.212991] bn = 0, index = 0
> [ 131.212995] bn = fffffffffffffff4, index = 7336
> [ 131.213015] jfs_lookup: dtSearch returned -5
This doesn't look like any JFS problem, more like DMAR is blocking a
write request from a controller to an area that it doesn't think should
be writable. Can you post dmesg and lspci -vv from bootup?
next prev parent reply other threads:[~2008-11-18 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 22:08 jfs problem Andrey Vul
2008-11-17 23:58 ` Steven Noonan
2008-11-18 3:13 ` Dave Kleikamp
2008-11-18 5:47 ` Robert Hancock [this message]
[not found] ` <e38d12ff0811172259s7e75ec68u2a57d3a7ec6ec848@mail.gmail.com>
2008-11-18 16:20 ` Robert Hancock
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=49225703.7060905@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.