linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: Antwort: Re: Antwort: Re: Oops in Kernel 2.4.21-rc1
       [not found] <OFBC4DE14D.84808A7E-ONC1256D33.005135A5-C1256D33.00523E77@lidl.de>
@ 2003-05-27 15:26 ` Stephan von Krawczynski
  0 siblings, 0 replies; 2+ messages in thread
From: Stephan von Krawczynski @ 2003-05-27 15:26 UTC (permalink / raw)
  To: Werner.Beck; +Cc: linux-kernel

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Antwort: Re: Antwort: Re: Oops in Kernel 2.4.21-rc1
@ 2003-05-27 14:58 Werner.Beck
  0 siblings, 0 replies; 2+ messages in thread
From: Werner.Beck @ 2003-05-27 14:58 UTC (permalink / raw)
  To: skraw; +Cc: linux-kernel


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.
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...



|---------+---------------------------->
|         |           Stephan von      |
|         |           Krawczynski      |
|         |           <skraw@ithnet.com|
|         |           >                |
|         |                            |
|         |           27.05.2003 16:07 |
|         |                            |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       An:       Werner.Beck@Lidl.de                                                                                          |
  |       Kopie:    linux-kernel@vger.kernel.org                                                                                 |
  |       Thema:    Re: Antwort: Re: Oops in Kernel 2.4.21-rc1                                                                   |
  >------------------------------------------------------------------------------------------------------------------------------|




On Tue, 27 May 2003 15:54:40 +0200
Werner.Beck@Lidl.de wrote:

> unfortunately that is not possible at the moment...
>

>> Exchange the USB/ISDN part with a pci card and re-try with kernel -rc4.
>
>> Tell us if that works.
>
>> Regards,
>> Stephan

Well, what exactly do you expect to hear? There are about a million and one
possibilities about your problem. Most of them are hardware-related. Hoping
that you have already made sure that you have no defective RAM, controller,
mainboard or the like (unlikely since you mention two hosts) I would
eliminate
additional risk factors like USB (always gives fun) and use the latest
kernel.

Regards,
Stephan






^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-05-27 15:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <OFBC4DE14D.84808A7E-ONC1256D33.005135A5-C1256D33.00523E77@lidl.de>
2003-05-27 15:26 ` Antwort: Re: Antwort: Re: Oops in Kernel 2.4.21-rc1 Stephan von Krawczynski
2003-05-27 14:58 Werner.Beck

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).