From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13876] New: [x86_32, 2.6.30, reiserfs, reiser3, bug, regression] kernel oopsed while Sarg was running
Date: Thu, 30 Jul 2009 11:36:32 GMT [thread overview]
Message-ID: <bug-13876-695@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=13876
Summary: [x86_32, 2.6.30, reiserfs, reiser3, bug, regression]
kernel oopsed while Sarg was running
Product: File System
Version: 2.5
Kernel Version: 2.6.30
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ReiserFS
AssignedTo: reiserfs-devel@vger.kernel.org
ReportedBy: for.poige+bugzilla.kernel.org@gmail.com
Regression: Yes
Created an attachment (id=22537)
--> (http://bugzilla.kernel.org/attachment.cgi?id=22537)
partial dmesg output
(Sarg is Squid statistic analyzer, giving quite valuable both disk and CPU
load.)
dmesg is in the attachment. Unfortunately, it's not complete cause the kernel's
failure made it impossible to log in to the comp where it occurred. Possibly,
it completely remains in the system log files, and I hope since the comp will
get rebooted (it's a remote one for me), I'll be able to find the logs and rest
of the filesystem... ergh... intact.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-07-30 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 11:36 bugzilla-daemon [this message]
2009-07-30 12:23 ` [Bug 13876] [x86_32, 2.6.30, reiserfs, reiser3, bug, regression] kernel oopsed while Sarg was running bugzilla-daemon
2009-08-20 14:31 ` bugzilla-daemon
2009-08-20 14:51 ` bugzilla-daemon
2009-08-20 15:30 ` bugzilla-daemon
2009-08-20 15:36 ` bugzilla-daemon
2009-08-21 19:56 ` bugzilla-daemon
2009-08-22 8:56 ` bugzilla-daemon
2009-11-21 0:06 ` bugzilla-daemon
2009-11-23 9:45 ` 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-13876-695@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@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).