| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB |
| From: | Juergen Urban <JuergenUrban@xxxxxx> |
| Date: | Sat, 21 Nov 2009 18:33:20 +0100 |
| In-reply-to: | <200911211151.23764@xxxxxx> |
| References: | <200911190957.45957.JuergenUrban@xxxxxx> <200911210200.13438.JuergenUrban@xxxxxx> <200911211151.23764@xxxxxx> |
| User-agent: | KMail/1.10.3 (Linux/2.6.27-7-generic; KDE/4.1.3; i686; ; ) |
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? |
| Previous by Date: | Re: Bug#557262: 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) - root cause found = asterisk, Roger Heflin |
|---|---|
| Next by Date: | Re: XFS, NFS and inode64 on 2.6.27, Michael Monnerie |
| Previous by Thread: | Re: BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB, Michael Monnerie |
| Next by Thread: | Re: BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |