Hi, i've just installed kernel 2.4.18-18.7.x (from RPM) and now it
seems there are problems with my scsi devices.
I have attached an adaptec scsi AIC7XXX adapter, the system detects the
device, but in the logs appears messages: "blk: queue c24afa18, I/0
limit 4095Mb (mask0xfffffff)", these messages didn't appear before with
my old kernel.
Also, there are another messages in the dmesg results:
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errno = 2
When i try to list or do something with my tape the message: st0 block
limits 1 - 16777215 bytes appears...
Sorry i'm new in this ?
Is this a bug ? a big one ? should i use instead my old kernel ?
Thanks in advance,
Karina.
On Tue, 2002-12-10 at 19:33, Karina wrote:
> Hi, i've just installed kernel 2.4.18-18.7.x (from RPM) and now it
> seems there are problems with my scsi devices.
> I have attached an adaptec scsi AIC7XXX adapter, the system detects the
> device, but in the logs appears messages: "blk: queue c24afa18, I/0
> limit 4095Mb (mask0xfffffff)", these messages didn't appear before with
> my old kernel.
Thats a perfectly normal message. Its giving parameters for your scsi
> Also, there are another messages in the dmesg results:
>
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errno = 2
That one is a bit stranger. I'd have expected it to put the scsi adapter
in the initrd which apparently it hasnt
> When i try to list or do something with my tape the message: st0 block
> limits 1 - 16777215 bytes appears...
Quite normal.
So it looks like its ok. Do file the kmod: failed to exec report in
https://bugzilla.redhat.com/bugzilla however. Regardless of it not being
a problem in your case it does want fixing
On 10 Dec 2002, Alan Cox wrote:
> On Tue, 2002-12-10 at 19:33, Karina wrote:
> > Hi, i've just installed kernel 2.4.18-18.7.x (from RPM) and now it
> > seems there are problems with my scsi devices.
> > I have attached an adaptec scsi AIC7XXX adapter, the system detects the
> > device, but in the logs appears messages: "blk: queue c24afa18, I/0
> > limit 4095Mb (mask0xfffffff)", these messages didn't appear before with
> > my old kernel.
>
> Thats a perfectly normal message. Its giving parameters for your scsi
>
> > Also, there are another messages in the dmesg results:
> >
> > kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errno = 2
>
> That one is a bit stranger. I'd have expected it to put the scsi adapter
> in the initrd which apparently it hasnt
I get the exact same message on an intel L440GX (VA Linux) machine. I
attributed it to the routing problem this board has. Looks like I was
wrong or was I? FWIW I do not have any SCSI devices attached.
> So it looks like its ok. Do file the kmod: failed to exec report in
> https://bugzilla.redhat.com/bugzilla however. Regardless of it not being
> a problem in your case it does want fixing
Assuming that you still want it in bugzilla if Karina does not do it I will.
Karina if you do bugzilla this please let me know the number.
Enjoy,
--
.............Tom "Nothing would please me more than being able to
[email protected] hire ten programmers and deluge the hobby market
with good software." -- Bill Gates 1976
We are still waiting ....
On 10 Dec 2002, Alan Cox wrote:
> > kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errno = 2
>
> That one is a bit stranger. I'd have expected it to put the scsi adapter
> in the initrd which apparently it hasnt
Possibly not bugzilla worthy - it's /sbin/modprobe that's ENOENT, not the
scsi adapter module itself.
This message is generated when the initrd loads scsi_mod.o and then
sd_mod.o without loading any hostadapters first. init_sd does a
scsi_register_module(MODULE_SCSI_DEV, &sd_template) which causes a
request_module("scsi_hostadapter") in scsi_mod.o as the initrd hasn't yet
loaded any hostadapters. The initrd then proceeds to load some the
hostadapter drivers explicitly via insmod and everything proceeds fine.
Presumably if mkinitrd was reordered to load scsi_mod, first hostadapter,
then sd_mod, etc, the message would go away but as it stands it is purely
cosmetic.
Chris
On 10 Dec 2002, Alan Cox wrote:
> So it looks like its ok. Do file the kmod: failed to exec report in
> https://bugzilla.redhat.com/bugzilla however. Regardless of it not being
> a problem in your case it does want fixing
It appears that recent RH build initrd files w/o all of the stuff in
modules.conf. Perhaps only the first SCSI adaptor, perhaps just ignoring
the ones which don't match the build hardware. I suspect the latter, since
even using --with= in a manual mkinitrd failed (silently) to include the
modules. I can't tell you how much that sucks if you build kernels for
multiple machines on a compile server.
Also, I installed 2.4.18-18.8.0 and it put a bunch of overlong label=
statements in lilo.conf, then ran lilo and didn't check the status. Since
it had deleted the old kernel that left a totally unbootable system. Guess
RH really likes grub and only tests upgrades and such with that.
I will report this later tonight when I'm willing to take the time to
prepare a proper bug report.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.