From: Alexey Vlasov <renton@renton.name>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup on all kernels after 2.6.3x
Date: Thu, 7 Mar 2013 17:34:14 +0400 [thread overview]
Message-ID: <20130307133414.GA6115@beaver> (raw)
In-Reply-To: <1360422473.6696.28.camel@edumazet-glaptop>
Hi,
On Sat, Feb 09, 2013 at 07:07:53AM -0800, Eric Dumazet wrote:
> >
> > I used 2.6.2x kernel for a long time on my shared hosting and I
> > didn't
> > have any problems. Kernels worked well and server uptime was about
> > 2-3
> > years.
> >
> > ...
> >
> > it doesn't happen on an empty server, only on loaded ones.
> > Unfortunately
> > I don't know how to provoke such hanging artificially.
> >
> Your traces dont contain symbols, its quite hard to guess the issue.
Well the server got high loaded and began to crash almost once a day.
=====
BUG: soft lockup - CPU#1 stuck for 23s! [httpd:21686]
Call Trace:
[<ffffffff8110bba5>] ? mntput_no_expire+0x25/0x170
[<ffffffff810f9389>] ? path_lookupat+0x189/0x890
[<ffffffff810f9b67>] ? filename_lookup.clone.39+0xd7/0xe0
[<ffffffff810fc85c>] ? user_path_at_empty+0x5c/0xb0
[<ffffffff8102b5f9>] ? __do_page_fault+0x1b9/0x480
[<ffffffff810f146e>] ? vfs_fstatat+0x3e/0x90
[<ffffffff810c54bf>] ? remove_vma+0x5f/0x70
[<ffffffff810f168f>] ? sys_newstat+0x1f/0x50
[<ffffffff814b09c2>] ? page_fault+0x22/0x30
[<ffffffff814b0f49>] ? system_call_fastpath+0x18/0x1d
=====
There's a full trace in attachment.
--
BRGDS. Alexey Vlasov.
next prev parent reply other threads:[~2013-03-07 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 14:10 BUG: soft lockup on all kernels after 2.6.3x Alexey Vlasov
2013-02-09 15:07 ` Eric Dumazet
2013-02-09 15:30 ` Alexey Vlasov
2013-03-07 12:54 ` Alexey Vlasov
2013-03-07 16:20 ` Eric Dumazet
2013-03-07 16:37 ` Alexey Vlasov
2013-03-07 16:44 ` richard -rw- weinberger
2013-03-07 16:57 ` Eric Dumazet
2013-03-09 19:11 ` Alexey Vlasov
2013-03-07 13:34 ` Alexey Vlasov [this message]
2013-03-07 13:41 ` BUG: soft lockup on all kernels after 2.6.3x (include full log) Alexey Vlasov
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=20130307133414.GA6115@beaver \
--to=renton@renton.name \
--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.