Comment 1 for bug 94095

I do not see this problem if fsck runs at boot time. This leads me to believe that this is a timing problem at boot time. I'm aware that changes were made to improve boot times in feisty. Since I never saw this problem in edgy, suspect the boot optimization(s) in feisty is causing the problem.

I think the automatic fsck after 30 boots, gives the ethernet setup enough time to complete before other network steps are done.

Others feisty users may not see this, because they are running on newer/faster hardware.

Portion of /proc/cpuinfo
cpu MHz : 746.793
cache size : 256 KB
bogomips : 1494.79