Re: Kernel Panic installing on SGI Indy
* Jacob Richard Beauregard <jrbeaure@uvm.edu> [2009-02-24 22:12]:
> Well, this email regards one of the SGI Indys. With the first SGI Indy,
> now named Bell, I successfully installed Debian via netboot, though the
> partitioning step of the installation was a bit tricky. However, when
> netbooting the other SGI Indy, which will hopefully be named Whistle upon
> successful installation, experienced a kernel panic very shortly after
> downloading the netboot file (though it's much less frustrating having
> something like this occur early in the installation process).
>
> The output was something along the lines of:
>
> Checking for multiply shift/bug? bug present? yes. workaround present? no.
> There might have been a line here but I forget what it was.
> Kernel Panic!
> Enable CPU_R4000_WORKAROUNDS to rectify.
>
> A Google search of "CPU_R4000_WORKAROUNDS debian" (not in quotes) returns
> one page of results referring to mostly if not all debian kernel image
> configuration files.
>
> It was suggested to me on the Debian support IRC channel that I might
> email debian-kernel-list to notify of the problem and to seek feedback.
>
> In any case, the CPU_R4000_WORKAROUNDS flag is referred to in two
> sections of all of the Google search results (which are pretty much all
> some file called Kconfig):
> "config MACH_DECSTATION" and "config CPU_R4000_WORKAROUNDS"
>
> However, it isn't referred to in the "config SGI_IP22" section. This
> machine, meanwhile, is detected as SGI_IP22 by the bootloader.
Ralf, Thomas, any comments?
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: