From: Jeff Mahoney <jeffm@suse.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: reiserfs-dev@namesys.com, reiserfs-list@namesys.com
Subject: Re: kernel BUG() hit during PCI testing
Date: Tue, 10 May 2005 14:25:47 -0400 [thread overview]
Message-ID: <4280FCAB.1020600@suse.com> (raw)
In-Reply-To: <20050510173448.GQ11745@austin.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linas Vepstas wrote:
> HI,
>
> On Tue, May 10, 2005 at 12:25:01PM -0400, Jeff Mahoney was heard to remark:
>>This one is on my radar among several others of the same type. What's
>>happening is that somehow buffers are getting dirtied despite not being
>>uptodate. They're getting allowed to be put back into the write cycle
>>which is totally invalid, so they're getting caught rather than being
>>written to disk. ext3 has similar problems, but tends to handle them as
>>buffer errors rather than BUGs. I'm investigating whether or not these
>>errors could occur outside individual filesystems.
>
> OK, if I don't get busy with other things, I'll look more closely at
> this as well. Maybe :-/ Meanwhile here's the dmesg output between
> the pci outage and the crash. Don't know if this will be useful.
> If you want any kind of tracing turned on, let me know.
It should be just a matter of performing an audit of where these buffers
are getting re-introduced into the write cycle. I don't really need any
more data points, I've got quite a bit already from various reports.
Thanks though.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCgPyrLPWxlyuTD7IRAmeEAJ9coIRFqDgtcR6/HM2W3Ub6cDCnPQCdEfDD
n98S1iOxoEdrFwASM8FRohE=
=/v+v
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-05-10 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 22:23 kernel BUG() hit during PCI testing Linas Vepstas
2005-05-10 16:25 ` Jeff Mahoney
2005-05-10 17:34 ` Linas Vepstas
2005-05-10 18:25 ` Jeff Mahoney [this message]
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=4280FCAB.1020600@suse.com \
--to=jeffm@suse.com \
--cc=linas@austin.ibm.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
/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.