From: Andreas Schmidt <andy@space.wh1.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Frequent system freezes after kernel bug
Date: Sun, 13 Jun 2004 19:51:34 +0200 [thread overview]
Message-ID: <20040613175134.GO1733@rocket> (raw)
In-Reply-To: <40CB9B84.4030502@g-house.de> (from evil@g-house.de on Sun, Jun 13, 2004 at 02:10:44 +0200)
On 2004.06.13 02:10, Christian Kujau wrote:
> Andreas Schmidt wrote:
> |> On Sat, Jun 12, 2004 at 08:37:42PM +0200, Andreas Schmidt wrote:
> |>
> |> > > kernel: EIP: 0010:[iput+44/592] Tainted: P
> |>
> | fcdsl 862816 2
>
> could be totally unrelated, but please try to reproduce without this
> (tainted) fcdsl module. it is often known for weird lockups. i'm not
> able to tell from the oops message, so i have to ask: is this an SMP
> box?
The box has just one processor (Duron, in case it's relevant). BTW, I'm
a bit at a loss how to reproduce the problem. Trouble is, it appears
quite arbitrarily. The box has been running about 26hrs now without a
reboot. (OK, there wasn't much activity today except handling mails.) I
could unload the fcdsl module, which would cut me off the net. If
necessary, I could even do this for a day or two -- but what if that
error didn't occur during that time? As I'm not sure what triggered it
in the first place, IMHO nothing could be deduced with certainty from
the error not occuring. There'd only be definite information if it
_did_ happen again. So, what do you suggest? (Sorry if that sounds
obnoxious, but I'm really a bit confused about this stuff...)
Best regards,
Andreas
next prev parent reply other threads:[~2004-06-13 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 18:37 Frequent system freezes after kernel bug Andreas Schmidt
2004-06-12 20:20 ` Chris Wedgwood
2004-06-12 21:49 ` Andreas Schmidt
2004-06-13 0:10 ` Christian Kujau
2004-06-13 17:51 ` Andreas Schmidt [this message]
2004-06-13 22:14 ` Christian Kujau
2004-06-14 3:51 ` Andreas Schmidt
2004-06-16 7:23 ` Andreas Schmidt
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=20040613175134.GO1733@rocket \
--to=andy@space.wh1.tu-dresden.de \
--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