On Tue, Jul 06, 2010 at 04:23:48PM +0200, Arnd Bergmann wrote: > > 2. A more serious problem is that printing kernel message no more works > > after running into userspace. > > .... > > Freeing init memory: 100K > > 3sy||_|_| > > phyCORE login: > > .... > > The boot message between init and login sheel is printed only > > partly. The cursor jumps back and forward. It seems that part the > > special characters like new line etc. are cutted away so that the > > printout is shown in such a funny manner. After a tty is spawned, every > > thing works just well. I can log in onto the system and it seems to work > > so far. I bisected the kernel and identified eventually > > fb11bee14186af87ee6abb833cf1a2a6be59c65b as the > > first bad commit. The actual problem should be, however, > > 36c621d82b956ff6ff72273f848af53e6c581aba, where tty_port_block_til_ready() > > is introduced. Seems to me that there are locking problems. I > > unfortunately don't have any insights of tty layer to tell where the > > exact problem is. > > I'm sorry you had to bisect this. I did the same bisect and already > submitted a patch for this, which probably got stuck in Greg's inbox > while he was preparing the stable releases. I can't find the patch > in the archives now, which could also mean that it never left my local > machine. > > I have the patch on a different machine, but will resend it to Greg > when I get there to make sure it doesn't get lost. It's in my todo queue, sorry, I spent last week on the 5 stable kernel releases, I should get to this today and push it into the next linux-next release. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
