From: Blaisorblade <bla...@ya...> - 2005-12-30 11:09:37
|
On Monday 26 December 2005 20:51, Juraj Holtak wrote: > Am Montag, den 26.12.2005, 20:15 +0100 schrieb Blaisorblade: > > > Same problem? Guess not, post the failures. > > > > Ok, correction - I see the same result - disable CONFIG_DEBUG_SPINLOCK > > probably. > > > > It's a debug option anyway - did I already said "your config is crazy?" > > disabling this was my first step. disable all what wasnt enabled before. > it didn`t help. it has nothing to do with it. i disabled all kernel > debugging? > > what do you mean by: > Ok, correction - I see the same result > can you reproduce the bug? No; I thought so but after seeing the complete description I saw you mentioned another bug. Just got this couple of mail (blocked by my spam filters - ) - when you said "I had to start it up 20x to get it running", I got a similar result with CONFIG_DEBUG_SPINLOCK - once out of 10 it started, the other ones it gave immediate "segmentation fault" at startup. Instead, you said in the other mail you got: > busy wait hang right after root partition is mounted read only and init > should start that's another thing, but the areas I'd check are: 1) if my binaries don't run there some host problems (some Fedora kernels or things like Exec Shield have given us problems in the past) 2) if they run, the problem is either with the .config or with GCC. -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |