[ale] Kernel problem

[David Corbin]

Dow Hurst wrote:

>You could try enabling verbose mode on the daemons that are started. 
>You could put a sync at the end of each init script.  And you could not
>load modules automatically but do it by hand to see if a particular
>module is fouling up your boot.  At least that would be a start.
>Dow
>
>David Corbin wrote:
>
>>I have a 2.4.17 kernel that works well for me.   I download and build
>>2.4.18.  I copy the .config file from 2.4.17, do a "make oldconfig", and
>>build that kernel.  The -18 kernel will not boot for me.  It hangs up a
>>short way into the init.d scripts.
>>
>>What is the correct thing to do to isolate the problem?  (Each failed
>>boot with 2.4.18 causes fsck to repair the filesystem, too, btw).
>>
>>David
>>
>>P.S. There is one problem with 2.4.17 - I hae an application that will
>>lock it up after 2-3 days, but I think that's related to a specific USB
>>device/driver.
>>
>>---
>>This message has been sent through the ALE general discussion list.
>>See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
>>sent to listmaster at ale dot org.
>>
>
Without having proof, I don't *think* it's the init scripts causing the 
lockup.  The lockup simply occurs *while* they're running....



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.