Brain storm: how do I debug this?

[Omer Zak]

Then the next step is to eliminate bugs in modular drivers (unless in
"same kernel" you mean that also the kernel modules are the same) and in
user space programs/configuration files.

Time to do a "Lion in the desert":
1. Uninstall as many packages as possible from the Debian installation,
yet exhibiting the bug.  This will also reduce the number of files to be
dealt with in the next steps.
2. If the filesystem in the system supports access timestamps, determine
which files are being accessed by the boot process.
I don't know if it needs to be enabled specifically - I know that in
regular Linux systems I'd like this to be disabled to conserve boot
times and reduce chances of filesystem corruption.
3. Make hybrid Debian-Ubuntu installations, by copying over groups of
files (among those which are being touched by the boot process) from
Ubuntu when they differ from their Debian counterparts.

On Sat, 2011-03-19 at 15:26 +0200, Shachar Shemesh wrote:
> On 19/03/11 15:14, Omer Zak wrote:
> > Did you verify that all hardware works properly, especially all physical
> > memory?
> > Can you run a memory test on the device?
> >    
> I don't think there is memcheck for arm (am I wrong?), but the symptoms 
> don't feel like corrupt memory. There is no panic, and Ubuntu worked 
> just fine with precisely the same kernel.

-- 
PHP - the language of the Vogons.
My own blog is at http://www.zak.co.il/tddpirate/

My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which
I may be affiliated in any way.
WARNING TO SPAMMERS:  at http://www.zak.co.il/spamwarning.html