Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750902AbWBTVSg (ORCPT ); Mon, 20 Feb 2006 16:18:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750896AbWBTVSg (ORCPT ); Mon, 20 Feb 2006 16:18:36 -0500 Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:61065 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1750808AbWBTVSg (ORCPT ); Mon, 20 Feb 2006 16:18:36 -0500 Date: Mon, 20 Feb 2006 13:18:47 -0800 (PST) Message-Id: <20060220.131847.25386315.davem@davemloft.net> To: mingo@redhat.com CC: linux-kernel@vger.kernel.org Subject: softlockup interaction with slow consoles From: "David S. Miller" X-Mailer: Mew version 4.2.53 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 773 Lines: 20 When register_console() runs, it dumps the entire log buffer to the console device with interrupts off. If you're going over a slow console, this can easily take more than 10 seconds especially on SMP with many cpus brought up. This makes the softlock fire, which is terribly annoying :-) I think the bug is in the console registry code, I think it should capture chunks of the existing console buffer into some local memory and push things piece by piece with interrupts enabled to the console driver(s). Any better ideas? - 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/