conf/145311: loader.conf can cause boot hang
henrygrebler at optusnet.com.au
Sun Apr 4 08:28:03 UTC 2010
--> Try the following steps exhibit the same problem:
-->- Remove sem_load="YES". Execute `load sem' in the bootloader.
-->- Empty out loader.conf. Then boot up with the bootloader once again and do:
-->Please try all of the steps with boot -v to see what happens.
All of the following were performed with an empty loader.conf.
1. First try:
That seems a bit odd to me. I was given to understand that ukbd is
already in the kernel.
OK load snd_ich
loading required module 'sound'
OK boot -v
As far as I can tell, hangs in the same way (and the same as 3.2 of my
2. Second try (different order):
As far as I can tell, hangs as in 1 above.
3. Third try (omit sem):
6. Different order from 3 above.
It doesn't look like module sem is relevant.
So, both modules snd_ich and ukbd must be loaded to cause the hang.
Is it possible there is some sort of interaction between them?
7. I don't know how these things work. When there is no reponse after
"load sem", does that mean it did not do anything?
I tested this hypothesis: I did:
After the first command, I got the usual response
("/boot/kernel/ukbd.ko text=..."); but when I repeated it, nothing:
OK load ukbd
OK load ukbd
So, why is the first command loading a file when
/usr/src/sys/i386/conf/GENERIC has a line to load the driver?
Here it is:
device ukbd # Keyboard
The man page ukbd(1) says:
To compile this driver into the kernel, place the following line
kernel configuration file:
-->play OS'. If it's currently disabled, try enabling it. Also, try
-->disabling SMP to see if that has any affect:
Is this relevant for a machine with a single CPU?
More information about the freebsd-bugs