2.6.39-rc5-git2 boot crashs
Enclosed is still the /var/log/debug file. UNFORTUNATELY, IT DONT SHOWS THE KERNEL VERSION (THIS IS SOMETHING WHAT YOU COULD CORRECT !!!) The boots of today 14:17:43 and 21:00:01 are using 2.6.38.4 (during the 1st run, I compiled/packaged 2.6.39-rc5-git4 without problems, the 2nd is running actually), between them were runs with 2.6.39-rc5-git4 ON WHICH IS DEBUG (in the kernel hacker config) SWITCHED ON (on 2.6.38.4 it's NOT switched on).
Perhaps thats helpful anyhow.
wl
---
Professional hosting for everyone - http://www.host.ru
Quoted 2 lines · werner
Enclosed is still the
/var/log/debugfile.
Can you please just do what I asked to, namely do the minimal config.
That will also make it _much_ faster for you to compile the kernel (you can probably do it in 10 minutes or less if you just get a really nice config that only has the stuff you actually require - on my machine I compile my kernel in about 3 minutes from scratch).
And not only would it tell us something (namely whether the problem persists or not), but if it _does_ persist even with a minimal kernel that only has the drivers you need, it would make it much more feasible to do a bisect because now the compile/test cycle would be much shorter.
So please, just do it. Because quite frankly, by now you're mainly just wasting everybody's time.
Quoted 2 lines
UNFORTUNATELY, IT DONT SHOWS THE
KERNEL VERSION (THIS IS SOMETHING WHAT YOU COULD CORRECT !!!)
The kernel version shows up in dmesg as the very first thing. Something like
[ 0.000000] Linux version 2.6.39-rc5-00127-g1be6a1f89f13
([email protected]) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #9 SMP PREEMPT Fri Apr 29 16:28:05 PDT 2011
You've just lost it, possibly because your dmesg file ended up growing too large, or possibly because some tool just didn't bother to save it.
Linus