Antwort: Re: Antwort: Re: Oops in Kernel 2.4.21-rc1

[Werner . Beck (Werner.Beck@Lidl.de)]

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@xxxxxxxxxx|
|         |           >                |
|         |                            |
|         |           27.05.2003 16:07 |
|         |                            |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       An:       Werner.Beck@xxxxxxx                                                                                          |
  |       Kopie:    linux-kernel@xxxxxxxxxxxxxxx                                                                                 |
  |       Thema:    Re: Antwort: Re: Oops in Kernel 2.4.21-rc1                                                                   |
  >------------------------------------------------------------------------------------------------------------------------------|




On Tue, 27 May 2003 15:54:40 +0200
Werner.Beck@xxxxxxx 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





-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/