From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Thu, 30 Dec 2004 10:21:54 +0000 [thread overview]
Message-ID: <200412301021.54043.nick@linicks.net> (raw)
> All of them have in common the notice of some process having
>
> "exited with preempt_count 1"
>
> and all of them happened within three hours -- this is the first time
> that a mainline kernel has been behaving so consistently unstable for
> me, in fact.
Yes, I got exactly the same - hard locked, nothing in logs.
I got this from screen:
kswapd exited with prempt-count 1
Kernel Panic - not syncing: fatal exception in interrupt.
My box has one IDE drive... and is gateway for my LAN using IPTABLES/NAT/MASQ.
The crash happened everytime I finished playing quake2 and quit the client.
I have gone back to 2.6.4 at the moment - the only kernel I can get to run
24/7/365 without a kswapd oops.
I am still sussing why/wtf.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2004-12-30 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 10:21 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-31 11:46 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Manfred Spraul
2004-12-30 0:31 Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King
2004-12-31 9:58 ` Georg C. F. Greve
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones
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=200412301021.54043.nick@linicks.net \
--to=nick@linicks.net \
--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