On Wed, Aug 31, 2011 at 09:01:40AM +0100, Ian Campbell wrote: > On Tue, 2011-08-30 at 10:22 -0400, Konrad Rzeszutek Wilk wrote: > > > It might make sense to also use 'xen_raw_printk' as sometimes you don't > > get to see the panic - you end up with this unhelpfull message: > > > > (XEN) domain_crash_sync called from entry.S > > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > > .. snip.. > > > > so something like this: > > Fine by me, although I do wonder if maybe we shouldn't be fixing panic() > itself or our console driver or something, this isn't the first such > patch I've noticed which doubles up on the panic message. Is the > underlying issue just that earlyprintk isn't on by default?
Yup. earlyprintk=xen would do the same thing. Added this patch on the 3.1-rcX train with your Acked-by. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110901135334.gc23...@dumpdata.com
