Re: bug in sym53c8xx? [Was: RAID1 + LVM not detected during boot on 2.6.9]
From: Alexander E. Patrakov
Date: Thu Dec 16 2004 - 00:11:51 EST
Aleksandar Milivojevic wrote:
> The timeline (during normal boot) looks something like this:
> - sym53c8xx is loaded and starts detecting disks
> - raid1 and dm-* modules are loaded
> - raidautorun and lvm vgscan are executed
> raid1 module doesn't find anything since sym53c8xx hasn't yet reported
> any disk drives.
> If I insert sleep 30 (shorter value would probably work too) after
> "insmod sym53c8xx" line in init script, and than reboot, everything
> works. sym53c8xx has enough time to find the disk drives, so when next
> steps are taken (loading of raid1 and dm-* modules, and execution of
> raidautorun and lvm vgscan) they are there.
> I'm not sure if insmod was supposed to wait until driver initializes?
> In the 2.4.x kernel days, I remember there was different driver used for
> this SCSI card (Symbios Logic 53c1010 Ultra3 SCSI Adapter). It hasn't
> suffered from this problem (it detects disks fast enough so that
> subsequent loading/initialization of raid1 works).
> The question is if this is:
> - bug in sym53c8xx driver?
> - bug in insmod?
> - bug in init script built by mkinitrd (missing sleep)?
> - bug in design of initrd?
> If this might be a bug in sym53c8xx, let me know, and I'll file the bug
> into bugzilla.
I am not sure how to classify this bug properly.
First, the driver correctly follows the behaviour described by Greg KH: it
should load successfully even if there is no corresonding hardware. Then
(in already-loaded state) it should generate hotplug events when the
hardware says it's present (and that's slow). Greg KH says that in hotplug
world (i.e., in reality) nothing else is possible. From this viewpoint, the
bug is in the linuxrc script provided by RedHat. It should really either
poll and sleep and wait or use udev to get notification when the disk is
Second, a similar problem has been discussed on LKML in September, under the
title "udev is too slow creating devices". While originally concerned with
asynchronicity due to udev itself, this therad also touches the idea that
udev doesn't really add asynchronicity, since PCI devices are really
hot-pluggable and the bus is already asynchronous. The thread starts here:
and continues here:
In this thread, there were the following words by Benjamin Herrenschmidt:
> Nope, Greg is right. Drivers themselves won't necessarily provide
> you with the device interface in a synchronous way after they are
> loaded, and some will certainly never. It is all an asynchronous process
> and there is simply no way to ask for any kind of enforced synchronicity
> here without major bloatage.
However, we _do_ need this synchronicity, and therefore _have_ to live with
major bloatage either in the kernel (currently that's not there) or in the
userspace (your "sleep for a magic number of seconds" here and there in
linuxrc and bootscripts). My opinion is that the needed userspace bloatage
is not centralized, also it's hard to audit, and therefore the issue of
supporting the statement "This piece of hardware must be there, it's not
really hotpluggable" must be dealt with.
P.S.: FreeBSD explicitly sleeps 15 seconds for SCSI devices to settle.
Alexander E. Patrakov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/