Re: 2.4.2: killing interrupt handler was: Re: ignoring boot on 2.4.2 ?

[Michal Jaegermann <michal ellpspace math ualberta ca>]

On Thu, Mar 01, 2001 at 12:45:44PM +0100, Helge Kreutzmann wrote:
> 
> 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

Can you start in a single user mode?  If yes, then starting services
one by one, with a full controll from user space, will make much easier
to pinpoint your problem.  If not, then you will eliminate from your
investigations spurious stuff.

> I am not worried about the defrag message (we havn't edited the RH 6.1
> startup-scripts)

Why it shows up at all?

If you will look at 'Changes' file in 'Documentation' subdirectory of
your kernel sources then you will find there a section entitled
"Current Minimal Requirements" which specifies exactly that for a user
space.  If these are not met then your bug hunting will be at least
greatly impeded (and your chances for attracting a serious attention
are rather slim).

There is also another file in that directory named BUG-HUNTING and
another one in the top one named REPORTING-BUGS.  All of this pretty
essential reading material if you have troubles.

  Michal