Keith Owens wrote:
>
> On Thu, 14 Jun 2001 03:08:28 -0600,
> "D. Stimits" <stimits@xxxxxxxxxx> wrote:
> >Now I am however getting what is probably a scsi error, and less likely
> >XFS...I'm not sure though. What I see is that it starts to load fine,
> >then gets to:
> >SCSI subsystem driver Revision: 1.00
> >kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> >spurious 8259A interrupt: IRQ7.
>
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> is no such file or directory. Your initrd does not contain
> /sbin/modprobe, initrd normally only contains insmod to save space.
> You compiled the kernel for automatic loading (kmod) which expects
> modprobe. As long as you load a SCSI host adaptor yourself during
> initrd startup, you can ignore this message.
Interesting that it is not there. Wouldn't modprobe be normal on
mkinitrd? Since I can do this to view an initial ramdisk on loopback:
gzip -dc your.img > somefile
mount -o loop somefile somedir
I wonder if there is a way I can do a reverse of this...mount it, copy
modprobe (statically linked) to it, and rewrite it with dd?
>
> spurious 8259A interrupt: IRQ7. is a little more puzzling. The system
> got an interrupt on irq 7 but nothing was assigned to that irq. 7 is
> usually line printer, although it could have been assigned to another
> device. In any cause it is definitely nothing to do with XFS, it might
> not even be SCSI related. Ask on linux-kernel and include the chipset
> data and PCI routing information from the start of the boot log.
I do have a printer that isn't normally on. I wonder if this is possibly
related to having had it on and used it, then turning it off? But then
again, it occurred during bootup, and it wasn't on at all that whole
time. Also, I have seen it quite sparsely in the logs, it has shown up
before, but is rare. It looks like maybe it is related to the ethernet
adapter, at as far as what it shows up next to. I'll probably
investigate it a bit then ask the kernel list if there is no answer.
D. Stimits, stimits@xxxxxxxxxx
|