From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12679] New: 2.6.28.4 ext4 fs hang, load 22 and up, may be firefox/apps stuck on sync_page
Date: Mon, 9 Feb 2009 07:52:43 -0800 (PST) [thread overview]
Message-ID: <bug-12679-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12679
Summary: 2.6.28.4 ext4 fs hang, load 22 and up, may be
firefox/apps stuck on sync_page
Product: File System
Version: 2.5
KernelVersion: 2.6.28.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: sec@dschroeder.info
Latest working kernel version: ?
Earliest failing kernel version: ?
Distribution: Gentoo
Hardware Environment: Desktop, Athlon X2 5050e, 4GB Ram, mcp55, hd103ui
Software Environment: amd64 gentoo linux,kernel.org 2.6.28.4, e2fsprogs 1.41.4
Problem Description: using the system, applications accessing the "faulty"
filesystem hang, load increases to 23.00, dmesg is nothing special, top shows
two cores in nearly 100% wait
Steps to reproduce: dont know yet
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-09 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 15:52 bugme-daemon [this message]
2009-02-09 15:59 ` [Bug 12679] 2.6.28.4 ext4 fs hang, load 22 and up, may be firefox/apps stuck on sync_page bugme-daemon
2009-02-09 16:07 ` bugme-daemon
2009-02-10 19:43 ` bugme-daemon
2009-02-23 22:09 ` bugme-daemon
2009-02-23 22:10 ` bugme-daemon
2009-02-26 11:09 ` bugme-daemon
2009-02-26 11:10 ` bugme-daemon
2009-03-04 5:33 ` bugme-daemon
2009-04-09 15:09 ` 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-12679-13602@http.bugzilla.kernel.org/ \
--to=bugme-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.