From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13876] [x86_32, 2.6.30, reiserfs, reiser3, bug, regression] kernel oopsed while Sarg was running
Date: Mon, 23 Nov 2009 09:45:03 GMT [thread overview]
Message-ID: <200911230945.nAN9j38j026832@demeter.kernel.org> (raw)
In-Reply-To: <bug-13876-695@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13876
Igor M Podlesny <for.poige+bugzilla.kernel.org@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |CODE_FIX
--- Comment #9 from Igor M Podlesny <for.poige+bugzilla.kernel.org@gmail.com> 2009-11-23 09:44:59 ---
> Igor, can you try latest kernel
Roland, that comp. isn't mine; it has been running 2.6.27.something happily for
quite a long time now and its users are careless. I don't think it'd be a good
idea to tell'em "guys, kernel devs would like to give your box another crash
test, wouldn't ya mind, ugh?". :-)
P. S. I tried reproducing this problem inside VirtualBox but failed -- 2.6.30
inside it runs just ok. In case I'll have a chance to meet that bug I'll do my
best reporting it. Let me mark this ticket as resolved.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2009-11-23 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 11:36 [Bug 13876] New: [x86_32, 2.6.30, reiserfs, reiser3, bug, regression] kernel oopsed while Sarg was running bugzilla-daemon
2009-07-30 12:23 ` [Bug 13876] " 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 [this message]
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=200911230945.nAN9j38j026832@demeter.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).