Thorsten,
> >Does the other kernel show any boot progress on the screen at all, after the
> >bootstrap has finished loading and passed control to the kernel?
>
> Coloured pixels.
If the other kernel (nonet) shows a proper boot screen, that's a kernel size
issue.
On the other hand:
>
> >Can you send me the contents of arch/m68k/atari/config.c and
> >arch/m68k/atari/atariints.c from the patched source tree you used for these
> >kernels?
>
> Sure:
That does not include my more recent patches to the interrupt code. I
suspect you may be using the atari_ethernec driver instead of the generic ne
one as well. I'll check your kernel image to see what it does use.
The ne.c network driver does not appear to tolerate interrupts arriving before
the device has been configured, at least in the early boot phases. I'm uncertain
whether it would work even with my latest patches applied - maybe I can find
some time on the weekend to test that.
Geert: is there some way for kernel network drivers to figure out whether the
network subsystem has been initialized, and hold off interrupt processing
before that time? I'm using 'if (netif_running(dev))' in atari_ethernec but
that does not appear to prevent the lockup.
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20130124202050.ga28...@mail.biophys.uni-duesseldorf.de
