From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 71301] New: CPU soft lockup
Date: Fri, 28 Feb 2014 16:28:30 +0000 [thread overview]
Message-ID: <bug-71301-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=71301
Bug ID: 71301
Summary: CPU soft lockup
Product: File System
Version: 2.5
Kernel Version: 3.13.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: cyril.adrian@gmail.com
Regression: No
Created attachment 127701
--> https://bugzilla.kernel.org/attachment.cgi?id=127701&action=edit
.config and syslog
During a simple and innocent "du" :-)
The process locked in the kernel, I could not kill it, machine froze at
shutdown (I had to turn it off the hard way).
I join the syslog (only starting from the first bug).
Home-compiled kernel, .config joined too.
For more info please ask.
Best regards,
Cyril
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-02-28 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:28 bugzilla-daemon [this message]
2014-02-28 20:42 ` [Bug 71301] CPU soft lockup bugzilla-daemon
2014-03-01 6:53 ` bugzilla-daemon
2014-03-02 13:55 ` 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-71301-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.