From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 34302] Errors from kjournald
Date: Tue, 3 May 2011 15:02:15 GMT [thread overview]
Message-ID: <201105031502.p43F2Fo5030112@demeter2.kernel.org> (raw)
In-Reply-To: <bug-34302-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=34302
--- Comment #1 from Theodore Tso <tytso@mit.edu> 2011-05-03 15:02:14 ---
You've given us a bunch of stack dumps, but not the explanation of why
kernel dumped them. There should have been a few more informative
messages before the stack dumps in your syslog. I'm going to guess it
was a soft lockup warning message, perhaps?
- Ted
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-05-03 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 13:30 [Bug 34302] New: Errors from kjournald bugzilla-daemon
2011-05-03 15:01 ` Ted Ts'o
2011-05-03 15:02 ` bugzilla-daemon [this message]
2011-05-03 16:27 ` [Bug 34302] " bugzilla-daemon
2011-05-03 16:59 ` Andreas Dilger
2011-05-03 17:54 ` bugzilla-daemon
2011-05-03 18:48 ` bugzilla-daemon
2012-08-23 13:51 ` 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=201105031502.p43F2Fo5030112@demeter2.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.