From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well
Date: Mon, 17 Dec 2007 20:44:51 +0100 [thread overview]
Message-ID: <200712172044.51629.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0712171540040.6503@blonde.wat.veritas.com>
On Montag, 17. Dezember 2007, you wrote:
> On Mon, 17 Dec 2007, Hemmann, Volker Armin wrote:
> > I got another crash, now with 2.6.23.11 on logout from KDE (two
> > differences, new kernel, 4gb ram instead of 2gb):
> > also I got some strange message yesterday before increasing ramsize:
> > [19546.639528] swap_free: Bad swap offset entry 04000000
> > [27999.370777] swap_free: Bad swap offset entry 04000000
> > [27999.434282] swap_free: Bad swap offset entry 04000000
> > [27999.466035] swap_free: Bad swap offset entry 04000000
> > [27999.521132] swap_free: Bad swap offset entry 04000000
> > [27999.561621] VM: killing process ld-linux-x86-64
> > [27999.561719] swap_free: Bad swap offset entry 04000000
>
> You're seeing a single bit set where it shouldn't be: please give
> memtest86+ a good try; if it's not actually your memory that's bad,
> then I'd guess it's something like overheating (please correct me,
> ye who know better).
>
> Hugh
first of all, the 2 with which I was seeing that have had their memtest run
for some hours some weeks ago, without problems. I can compile stuff - like
the latest kde4 rc without segfaults or problems (except when the oops is
happening), and this mess only started recently. To be more correct:
the swap-mess only started with 2.6.23.11. With 2.6.23.9 I get the kio_http...
rip's, but no swap related messages.
Overheating is very unlikely. I made sure that my computer is very well
cooled. Even under high load I get something like 50°C from lmsensors and
bios - and the errors are completly unrelated to load. Or temperature.
Without load my cpu idles at ~30°C. Again, lmsensors and bios are very close
about that.
Glück Auf,
Volker
next prev parent reply other threads:[~2007-12-17 20:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 0:06 almost daily Kernel oops with 2.6.23.9 Hemmann, Volker Armin
2007-12-17 14:59 ` almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well Hemmann, Volker Armin
2007-12-17 15:47 ` Hugh Dickins
2007-12-17 19:44 ` Hemmann, Volker Armin [this message]
2007-12-20 2:13 ` Hemmann, Volker Armin
2007-12-20 3:50 ` Scott
2007-12-20 5:53 ` Hemmann, Volker Armin
2007-12-20 14:38 ` David Newall
2007-12-20 18:37 ` Hemmann, Volker Armin
2007-12-20 21:48 ` Pekka Enberg
2007-12-20 22:13 ` Ingo Molnar
[not found] ` <1198134579.4429.10.camel@homer.simson.net>
2007-12-20 18:14 ` Hemmann, Volker Armin
2007-12-21 7:47 ` Mike Galbraith
2007-12-21 12:54 ` Hemmann, Volker Armin
2007-12-20 15:25 ` Stefan Richter
2007-12-20 18:12 ` Hemmann, Volker Armin
2007-12-20 19:04 ` Ingo Molnar
2007-12-20 20:29 ` Hemmann, Volker Armin
2007-12-21 2:09 ` Hemmann, Volker Armin
2007-12-21 11:19 ` Ingo Molnar
2007-12-29 23:03 ` Hemmann, Volker Armin
2007-12-20 19:06 ` Stefan Richter
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=200712172044.51629.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=hugh@veritas.com \
--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