From: Juergen Urban <JuergenUrban@gmx.de>
To: xfs@oss.sgi.com
Subject: Re: BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB
Date: Sat, 21 Nov 2009 18:33:20 +0100 [thread overview]
Message-ID: <200911211833.20691.JuergenUrban@gmx.de> (raw)
In-Reply-To: <200911211151.23764@zmi.at>
On Saturday 21 November 2009 11:51:23 Michael Monnerie wrote:
> On Samstag, 21. November 2009 Juergen Urban wrote:
> > To get the error I just need to play video with mplayer and don't
> > need to write to the file system at all.
>
> This really sounds like a broken hardware. Have you tried running
> MEMTEST?
>
> mfg zmi
At the first moment I also thought that it is a hardware bug. I already ran
MEMTEST for some hours, but it doesn't find anything. I replaced the main
board, the CPU and the power supply. I also tried to replace/remove RAM. But
I've done this while chasing for the stack overflow. But maybe this a problem
which I introduced by replacing the hardware. So I will try to change all the
hardware back.
Can someone explain the purpose of the BUG() in end_page_writeback()? Can I
remove the line?
Will XFS also work if I disable all address operations? What is the purpose of
the address operations?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-21 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 8:57 BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB Juergen Urban
2009-11-19 18:00 ` Eric Sandeen
2009-11-20 16:23 ` Juergen Urban
2009-11-20 16:36 ` Eric Sandeen
2009-11-20 17:08 ` Eric Sandeen
2009-11-21 1:00 ` Juergen Urban
2009-11-21 10:51 ` Michael Monnerie
2009-11-21 17:33 ` Juergen Urban [this message]
2009-11-21 22:04 ` Dave Chinner
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=200911211833.20691.JuergenUrban@gmx.de \
--to=juergenurban@gmx.de \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox