From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263306AbVGOO0v (ORCPT ); Fri, 15 Jul 2005 10:26:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263309AbVGOO0v (ORCPT ); Fri, 15 Jul 2005 10:26:51 -0400 Received: from gate.crashing.org ([63.228.1.57]:15839 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S263306AbVGOO0s (ORCPT ); Fri, 15 Jul 2005 10:26:48 -0400 Subject: Re: console remains blanked From: Benjamin Herrenschmidt To: Albert Herranz Cc: Jan Engelhardt , linux-kernel@vger.kernel.org In-Reply-To: <20050714101807.74323.qmail@web25805.mail.ukl.yahoo.com> References: <20050714101807.74323.qmail@web25805.mail.ukl.yahoo.com> Content-Type: text/plain Date: Sat, 16 Jul 2005 00:26:46 +1000 Message-Id: <1121437606.5963.26.camel@gaston> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > I have this problem since 2.6.12-rc2. > If I add back the patch hunk specified in my original > message, the blanking behaviour changes to that > present in pre-2.6.12-rc2 kernels. And you'll have nice scheduling in atomic for any printk() done in atomic context that triggers the unblank() when using radeonfb on an LVDS LCD panel... > I just would like to know if this new behaviour is > just intentional and makes sense to everyone (except > me :-)