Messages in this thread | | | Date | Wed, 25 May 2005 22:52:04 -0700 | From | Andrew Morton <> | Subject | Re: Hotplug CPU printk issue |
| |
Shaohua Li <shaohua.li@intel.com> wrote: > > > Please confirm that we in fact do not want to allow downed CPUs to > > print things, then send a patch. > Yep. In the cpu hotplug case, per-cpu data possibly isn't initialized > even the system state is 'running'. As the comments say in the original > code, some console drivers assume per-cpu resources have been allocated. > radeon fb is one such driver, which uses kmalloc. After a CPU is down, > the per-cpu data of slab is freed, so the system crashed when printing > some info.
hm, that certainly sounds sane, but I do recall there were reasonable-sounding reasons why the ia64 guys wanted printk-on-a-down-CPU to work. Hopefully David can remember what the problem was so we can find a more thorough fix.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |