From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 13536] crash while copying atime with touch
Date: Tue, 11 Aug 2009 14:33:00 GMT [thread overview]
Message-ID: <200908111433.n7BEX04Z027790@demeter.kernel.org> (raw)
In-Reply-To: <bug-13536-695@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13536
Roland Kletzing <devzero@web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |devzero@web.de
--- Comment #11 from Roland Kletzing <devzero@web.de> 2009-08-11 14:33:00 ---
>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
so, for each iteration you will need a reboot before, right ?
but, what`s the problem with that ? ;)
i`d go this way:
1. make a list of all modules you want to unload.
2. name that file however you want
3. do "cat file.list |while read module;do modprobe -r $module;done"
4. test
5. after the next crash, cut that file into 2 parts and repeat 3+4
6. in theory, one of the file should contain the "bad" module. name that file
appropriately (.good / .bad)
7. take the .bad file and repeat the steps until bisection results with a file
containing a single module
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2009-08-11 14:33 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
2009-06-18 13:54 ` bugzilla-daemon
2009-06-18 13:56 ` bugzilla-daemon
2009-08-11 14:33 ` bugzilla-daemon [this message]
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=200908111433.n7BEX04Z027790@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).