public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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 02:00:12 +0100	[thread overview]
Message-ID: <200911210200.13438.JuergenUrban@gmx.de> (raw)
In-Reply-To: <4B06CCFC.8030309@sandeen.net>

On Friday 20 November 2009 18:08:12 Eric Sandeen wrote:
> Eric Sandeen wrote:
> > Juergen Urban wrote:
> >> On Thursday 19 November 2009 19:00:16 Eric Sandeen wrote:
> >>> Juergen Urban wrote:
> >>>> Hello,
> >>>>
> >>>> my machine is running very unstable since I use XFS on an external USB
> >>>> harddisc (855 GByte XFS partition on 1TByte). One problem was the
> >>>> stack overflows caused by the large stack use of XFS, USB, SCSI and
> >>>> VFS in Linux 2.6.23.13. NFS on XFS caused much more stack overflows. I
> >>>> think I got around the stack overflows by disabling preemption, SMP
> >>>> and NFS in Linux, but I am not sure about it. I think that I didn't
> >>>> got a message from the stack overflow detection after this.
> >>>
> >>> Are you on 4k stacks?  To be honest I'd still expect things to be
> >>> mostly ok stack-wise even if so.
> >>
> >> No, I am using 8k stacks.
> >
> > Hmm.
>
> BTW if you are still seeing stack overflows when testing w/ the newer
> kernel, we can use some tracing to see what the stack backtrace is:
>
> sysctl -w kernel.stack_tracer_enabled=1
> mount -t debugfs none /sys/kernel/debug/
>
> and then look in:
>
> /sys/kernel/debug/tracing/stack_trace
> /sys/kernel/debug/tracing/stack_max_size
>

I don't think that I still get stack overflows in Linux 2.6.23.13.

Now I downloaded the new KNOPPIX with Linux 2.6.31.6. I've got also crashes 
with it, but this also could be a stack overflow, because the kernel 
configuration includes SMP and preemption. The problem here is that I don't see 
any kernel message. I just see the blinking keyboard or sometimes even 
nothing. To get the error I just need to play video with mplayer and don't 
need to write to the file system at all. I need to wait until I've got a good 
backtrace, but this will be with Linux 2.6.23.13.
The console tools of my installed Debian can't configure or use /dev/tty[0-9]* 
of Linux 2.6.31.6. The ioctls are not supported. I installed a newer version 
of the package, but this doesn't help. I copied the ".config" from Linux 
2.6.23.13 to 2.6.31.6. Maybe this is not compatible.


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-11-21  1:00 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 [this message]
2009-11-21 10:51           ` Michael Monnerie
2009-11-21 17:33             ` Juergen Urban
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=200911210200.13438.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