From: Soeren Sonnenburg <sonne@debian.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: gs_change ... kswapd0 exited with preempt_count 1
Date: Wed, 07 Mar 2012 23:50:05 +0100 [thread overview]
Message-ID: <1331160605.32484.24.camel@no> (raw)
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
Hi,
I am chasing a bug I cannot make any sense of: I have a i7 based server
on an intel board that runs just fine for days but then suddenly dies
with the backtraces below on git master but also any older kernel
version I tried. The system is running this config
http://7nn.de/debugging/config.gz
And no matter what I do I keep getting kernel panics after a couple of
days (or weeks) that all involve kswapd0 / gs_change:
http://7nn.de/debugging/panic-3.2.0.jpg
http://7nn.de/debugging/panic-3.3.0-rc5.jpg
Any ideas,
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-03-07 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1331160605.32484.24.camel@no \
--to=sonne@debian.org \
--cc=linux-kernel@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