Re: [PATCH v3] printk: Have printk() never buffer its data

[Greg Kroah-Hartman]

On Tue, Jun 26, 2012 at 11:38:28AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Jun 26, 2012 at 11:34:05AM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Jun 26, 2012 at 07:00:38PM +0200, Kay Sievers wrote:
> > > > Hm, this doesn't boot for me, just hangs at startup :(
> > 
> > Booting in a qemu image I get the following, it just hangs here:
> > 
> > [    2.683675] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
> > Started File System Check on Root Device                                [  OK  ]
> > Starting LSB: setup hostname and yp...
> > [    2.732973] systemd-fsck[108]: root: clean, 244481/1313280 files, 2189115/5242880 blocks
> > Starting Remount Root FS...
> > systemd-fsck[107]: root: clean, 244481/1313280 files, 2189115/5242880 blocks
> > [    2.746312] EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr
> > Started Remount Root FS                                                 [  OK  ]
> > Starting Load Random Seed...
> > Started Load Random Seed                                                [  OK  ]
> > [    2.797945] boot.localnet[133]: Using boot-specified hostname 'pistachio.kroah.org'
> > boot.localnet[133]: Using boot-specified hostname 'pistachio.kroah.org'
> > [    2.898718] boot.localnet[133]: Setting up hostname 'pistachio'..done
> > boot.localnet[133]: Setting up hostname 'pistachio'..done
> > boot.localnet[    2.973681] boot.localnet[133]: Setting up loopback interface RTNETLINK answers: File exists
> > [133]: Setting up loopback interface RTNETLINK answers: File exists
> > boot.localnet[133]: ..done
> > [    2.979959] boot.localnet[108]: ..done
> > Started LSB: setup hostname and yp                                      [  OK  ]
> > Started Setup Virtual Console                                           [  OK  ]
> > [    3.056710] input: PC Speaker as /devices/platform/pcspkr/input/input3
> 
> Ok, without your patch I get the same hang within qemu, so odds are it's
> not your fault here, but booting still fails.  I wonder if it's due to
> whatever oddness suse does with it's initrd, let me go try to get a
> initrd-free boot and see if that works...

Doh, stupid 'quiet' boot mode, it was hiding where things were hanging.

I get the following as the last line on the terminal before it locks up
(I sent you the full image off-list):
	Booting Node   0, Processors  #1 #2 #3

And I have 4 processors in this laptop, so odds are that's the first
time the continuation printk logic kicks in.

Any ideas?

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/