mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Werner.Beck@Lidl.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Antwort: Re: Antwort: Re: Oops in Kernel 2.4.21-rc1
Date: Tue, 27 May 2003 17:26:31 +0200	[thread overview]
Message-ID: <20030527172631.56af611b.skraw@ithnet.com> (raw)
In-Reply-To: <OFBC4DE14D.84808A7E-ONC1256D33.005135A5-C1256D33.00523E77@lidl.de>

On Tue, 27 May 2003 16:58:19 +0200
Werner.Beck@Lidl.de wrote:

> we just did an update from 2.4.10-SuSE because of some problems with the
> hardware (module for NIC and HDD). In this constellation we also had a
> kernel oops with the ISDN ("killing interrupt handler") which unfortunately
> didn't give us any hints in the logs.

Take my advice: Don't waste time with 7.3 based setup. Simply take a 8.2. It is
way better. Applications should not have problems with such an upgrade. 

> The systems are a field test and running an application that's why it is a
> problem to access them. I think a cause has an effect. The ISDN was not
> active at that time but probably a job of the SuSE distri, but I can't
> imagine that this causes kernel problems.
>  I will run a test in our lab and hope to get the error, then I can do some
> changes with the system.
> Thanks for your hints...

Your problem is this: even your old 7.3 should not crash no matter what cron
does around midnight. It makes no sense to find out _what_ crashes the box, you
won't probably find the real cause, so in the end you are only taking a
work-around instead of a real solution.

On the other hand: if you take a state-of-the-art distro chances are you won't
see your problem any more, have spent about the same time, but come out with a
new and fine solution.

Regards,
Stephan




       reply	other threads:[~2003-05-27 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFBC4DE14D.84808A7E-ONC1256D33.005135A5-C1256D33.00523E77@lidl.de>
2003-05-27 15:26 ` Stephan von Krawczynski [this message]
2003-05-27 14:58 Werner.Beck

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=20030527172631.56af611b.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=Werner.Beck@Lidl.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

all inboxes | Powered by JetHome®