All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13536] crash while copying atime with touch
Date: Thu, 18 Jun 2009 13:53:03 GMT	[thread overview]
Message-ID: <200906181353.n5IDr365014325@demeter.kernel.org> (raw)
In-Reply-To: <bug-13536-695@http.bugzilla.kernel.org/>

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





--- Comment #8 from Elmar Stellnberger <estellnb@gmail.com>  2009-06-18 13:53:02 ---
  Lately I tried to infringe the problem by unloading all possibly unloadable
kernel modules (up to 9) and see it suddenly worked without any problem.
Unexpectedly the vmware&virualbox modules did not harm. However finding the
kernel module that causes the crash by binary search is almost impossible since
there is no crash as soon as all requests can be satisfied from the cache
memory. Nonetheless I can provide a minimal module list the script has been
working with and a maximal module list that is sure to cause a crash.
  I wonder if there is any way to forge ahead to a backtrace/core file. At
FreeBSD there is always a core-dump hanging around after a crash.

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

  parent reply	other threads:[~2009-06-18 13:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 11:33 [Bug 13536] New: crash while copying atime with touch bugzilla-daemon
2009-06-14 11:34 ` [Bug 13536] " bugzilla-daemon
2009-06-14 11:36 ` bugzilla-daemon
2009-06-14 11:37 ` bugzilla-daemon
2009-06-14 11:54 ` bugzilla-daemon
2009-06-14 22:45 ` bugzilla-daemon
2009-06-15 16:29 ` bugzilla-daemon
2009-06-15 16:33 ` bugzilla-daemon
2009-06-15 17:36 ` bugzilla-daemon
2009-06-18 13:53 ` bugzilla-daemon [this message]
2009-06-18 13:54 ` bugzilla-daemon
2009-06-18 13:56 ` bugzilla-daemon
2009-08-11 14:33 ` bugzilla-daemon
2009-08-12  9:10 ` bugzilla-daemon
2009-08-15 16:19 ` bugzilla-daemon
2009-08-15 18:50 ` bugzilla-daemon
2009-08-18  7:32 ` bugzilla-daemon
2009-08-18  7:56 ` bugzilla-daemon
2009-08-18  9:07 ` bugzilla-daemon
2009-08-18  9:21 ` bugzilla-daemon
2009-08-20 10:27 ` bugzilla-daemon
2009-08-22  8:53 ` bugzilla-daemon
2009-08-23 20:44 ` bugzilla-daemon
2009-08-23 20:48 ` bugzilla-daemon
2009-08-23 21:00 ` bugzilla-daemon
2009-08-23 21:00 ` bugzilla-daemon
2009-08-23 22:29 ` bugzilla-daemon
2009-08-25 20:07 ` bugzilla-daemon
2009-08-25 21:01 ` bugzilla-daemon
2009-08-28 12:19 ` bugzilla-daemon
2009-10-21 11:00 ` bugzilla-daemon
     [not found] <bug-13536-695@https.bugzilla.kernel.org/>
2012-06-08 11:57 ` bugzilla-daemon
2012-06-08 11:57 ` 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=200906181353.n5IDr365014325@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 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.