From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 66821] New: "BUG: soft lockup" in proc_fd_link, causing freeze
Date: Tue, 10 Dec 2013 17:01:34 +0000 [thread overview]
Message-ID: <bug-66821-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=66821
Bug ID: 66821
Summary: "BUG: soft lockup" in proc_fd_link, causing freeze
Product: File System
Version: 2.5
Kernel Version: 3.13.0-rc3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: andreas.reis@gmail.com
Regression: No
Created attachment 118011
--> https://bugzilla.kernel.org/attachment.cgi?id=118011&action=edit
dmesg output during progressing freeze
Getting this since a few days randomly either as immediate freeze or
progressing system freeze. I'm not sure if that's the same bug though (nor if I
put this report in the right product/component category, just guessing by the
trace).
It starts with
general protection fault: 0000 [#1] PREEMPT SMP
path_get+0x15/0x30
proc_fd_link+0x9e/0xf0
proc_pid_readlink+0x3f/0xe0
SyS_readlinkat+0xeb/0x130
system_call_fastpath+0x1a/0x1f
and becomes
BUG: soft lockup - CPU#5 stuck for 23s! [chrome-sandbox:11068]
proc_fd_link+0x69/0xf0
proc_pid_readlink+0x3f/0xe0
SyS_readlinkat+0xeb/0x130
system_call_fastpath+0x1a/0x1f
Notes:
* This is based only on one dmesg output; I haven't yet gotten around to
compare that of different freezes.
* Kernel is self-compiled via the current sources (17b2112f) in Torvald's git;
distro is Arch.
* Always appears to happen after the system has run for a while, ie. not right
after boot.
* root is btrfs, home is ext4, var is reiserfs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-12-10 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 17:01 bugzilla-daemon [this message]
2013-12-10 20:02 ` [Bug 66821] "BUG: soft lockup" in proc_fd_link, causing freeze bugzilla-daemon
2013-12-10 20:11 ` bugzilla-daemon
2013-12-10 21:20 ` bugzilla-daemon
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=bug-66821-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.