linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13369] New: kernel BUG at fs/ext4/inode.c:3123
Date: Sat, 23 May 2009 12:04:52 GMT	[thread overview]
Message-ID: <bug-13369-13602@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=13369

           Summary: kernel BUG at fs/ext4/inode.c:3123
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.30-rc6
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: ckom26@gmail.com
        Regression: No


Being haunted by a consistent bug in 2.6.29.[234] that kept pdflush stuck at
100% cpu, I fetched and compiled 2.6.30-rc6. Now, I keep getting "kernel BUG at
fs/ext4/inode.c:3123!" (usually when I fire up ktorrent). In the attached
kernel logs you can see 2 different occurences of the bug.

A nearby single core cpu, low end box has not exhibited a single bug or
corruption for 3 months now, since I've converted to ext4, so I tried the
"nosmp" kernel boot parameter on the dual core laptop in question. Lo and
behold, the bug didn't rear its ugly head.

All partitions are mounted with "nodelalloc".

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2009-05-23 12:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 12:04 bugzilla-daemon [this message]
2009-05-23 12:07 ` [Bug 13369] kernel BUG at fs/ext4/inode.c:3123 bugzilla-daemon
2009-05-23 15:06 ` bugzilla-daemon
2009-05-23 21:40 ` bugzilla-daemon
2009-05-24 18:27   ` Aneesh Kumar K.V
2009-05-23 21:46 ` bugzilla-daemon
2009-05-24  2:52 ` bugzilla-daemon
2009-05-24 18:28   ` Aneesh Kumar K.V
2009-05-24  5:08 ` bugzilla-daemon
2009-05-24 12:02 ` bugzilla-daemon
2009-05-24 12:03 ` bugzilla-daemon
2009-05-24 16:32 ` bugzilla-daemon
2009-05-24 18:27 ` bugzilla-daemon
2009-05-24 18:28 ` bugzilla-daemon
2009-05-24 19:20   ` Aneesh Kumar K.V
2009-05-24 19:20 ` bugzilla-daemon
2009-05-26 13:16   ` Aneesh Kumar K.V
2009-05-24 20:43 ` bugzilla-daemon
2009-05-24 20:44 ` bugzilla-daemon
2009-05-26 13:16 ` bugzilla-daemon
2009-05-27 21:32 ` bugzilla-daemon
2009-08-18 17:38 ` 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-13369-13602@http.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).