On Thu, 2006-05-18 at 15:55 +0200, Andi Kleen wrote: > Michael Ellerman <[email protected]> writes: > > > Currently printk is no use for early debugging because it refuses to actually > > print anything to the console unless cpu_online(smp_processor_id()) is true. > > On x86-64 this is simply solved by setting the boot processor online very early. Yeah, someone suggested that. Unfortunately it doesn't work, we actually want to call printk before we even know which cpu we're on :D cheers -- Michael Ellerman IBM OzLabs wwweb: http://michael.ellerman.id.au phone: +61 2 6212 1183 (tie line 70 21183) We do not inherit the earth from our ancestors, we borrow it from our children. - S.M.A.R.T Person
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Andi Kleen <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- References:
- [RFC/PATCH] Make printk work for really early debugging
- From: Michael Ellerman <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Andi Kleen <[email protected]>
- [RFC/PATCH] Make printk work for really early debugging
- Prev by Date: Re: support for sata7 Streaming Feature Set?
- Next by Date: Re: replacing X Window System !
- Previous by thread: Re: [RFC/PATCH] Make printk work for really early debugging
- Next by thread: Re: [RFC/PATCH] Make printk work for really early debugging
- Index(es):
 |