From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 93491] Kernel crashes every 10 minutes. Computer stalls
Date: Thu, 19 Feb 2015 16:45:56 +0000 [thread overview]
Message-ID: <bug-93491-13602-XizmbkLUZD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-93491-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=93491
--- Comment #3 from Eric Sandeen <sandeen@redhat.com> ---
dmesg after reboot won't be helpful, I'm afraid.
If the fs was corrupt and fixed, but output not saved, and no further
information is available from the crash, this will be very hard to resolve.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-02-19 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 10:03 [Bug 93491] New: Kernel crashes every 10 minutes. Computer stalls bugzilla-daemon
2015-02-19 16:13 ` [Bug 93491] " bugzilla-daemon
2015-02-19 16:36 ` bugzilla-daemon
2015-02-19 16:45 ` bugzilla-daemon [this message]
2015-02-20 9:10 ` bugzilla-daemon
2015-02-20 15:16 ` bugzilla-daemon
2015-02-20 15:25 ` bugzilla-daemon
2015-02-20 15:56 ` bugzilla-daemon
2015-02-20 16:09 ` bugzilla-daemon
2015-03-03 18:38 ` bugzilla-daemon
2015-03-03 19:55 ` 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-93491-13602-XizmbkLUZD@https.bugzilla.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 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).