[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
2.4.2: killing interrupt handler was: Re: ignoring boot on 2.4.2 ?
- From: Helge Kreutzmann <kreutzm itp uni-hannover de>
- To: AXP-Liste <axp-list redhat com>
- Cc: Carsten Luckmann <luckmann itp uni-hannover de>,Martin Mueller <mmueller itp uni-hannover de>
- Subject: 2.4.2: killing interrupt handler was: Re: ignoring boot on 2.4.2 ?
- Date: Thu, 1 Mar 2001 12:45:44 +0100
Hello !
On Wed, Feb 28, 2001 at 09:07:52AM -0500, Phillip Ezolt wrote:
> This non-intuitive error happens when:
>
> Legacy kernel start address is NOT turned on and you are using an old
> (pre v0.7) version of aboot.
>
> Try turning it on, and things should work fine. (In the Kernel
> hacking section.)
Thanks, this got the boot past this point. Now we get a panic a little
later:
...
/proc/sys/net/piv4/ip_always_defrag is missing -- cannot contract IP
defragmentation
lo OK
eht0 failed
portmap failed
NFS lockd: lockdsvc: Invalid arg
Starting NFS statd: Kernel panic: Aiee, killing interrupt handler !
In interrupt handerl - not syncing
I am not worried about the defrag message (we havn't edited the RH 6.1
startup-scripts) but how can we keep the interrupt handler from beeing
killed ?
Thanks
Helge
--
Helge Kreutzmann, Dipl.-Phys. kreutzm@itp.uni-hannover.de
For gpg-key: finger kreutzm@rigel.itp.uni-hannover.de
64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm
Help keep free software "libre": http://www.freepatents.org/
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]