| 1 |
On 08/01/08 15:46, Åsmund Grammeltvedt wrote: |
| 2 |
> On Tuesday 08 January 2008 15:34:09 lurker wrote: |
| 3 |
>> Greetings, |
| 4 |
>> |
| 5 |
>> Often when I build systems with catalyst I encounter the following |
| 6 |
>> |
| 7 |
>> kernel freeze after the boot loader has completed: |
| 8 |
>>> [ ... lots of kernel loading stuff which seems ok ... ] |
| 9 |
>>> Freeing unused kernel memory: 172k freed |
| 10 |
>>> request_module: runaway loop modprobe binfmt-0000 |
| 11 |
>>> request_module: runaway loop modprobe binfmt-0000 |
| 12 |
>>> request_module: runaway loop modprobe binfmt-0000 |
| 13 |
>>> request_module: runaway loop modprobe binfmt-0000 |
| 14 |
>>> request_module: runaway loop modprobe binfmt-0000 |
| 15 |
> |
| 16 |
> I had an issue with the same symptoms. It turned out that after some builds, |
| 17 |
> the initramfs would contain empty files instead of links to busybox. |
| 18 |
> |
| 19 |
> In my case, the only way I could get it to work consistently was to patch |
| 20 |
> genkernel to use symbolic links instead, when setting up the initramfs. |
| 21 |
|
| 22 |
After upgrading to busybox-1.8.2 I've not experienced this any more. |
| 23 |
Perhaps it's just a coincidence due to the random nature of this problem. |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-catalyst@l.g.o mailing list |
Archives