From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261185AbVFSArh (ORCPT ); Sat, 18 Jun 2005 20:47:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261452AbVFSArh (ORCPT ); Sat, 18 Jun 2005 20:47:37 -0400 Received: from mustang.oldcity.dca.net ([216.158.38.3]:55718 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S261185AbVFSArf (ORCPT ); Sat, 18 Jun 2005 20:47:35 -0400 Subject: Re: bad: scheduling while atomic!: how bad? From: Lee Revell To: David L Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Date: Sat, 18 Jun 2005 20:50:33 -0400 Message-Id: <1119142233.4560.45.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2005-06-18 at 15:33 -0700, David L wrote: > [snip] > >On Sat, 2005-06-18 at 14:59 -0700, David L wrote: > > > I'm seeing the message: > > > > > > bad: scheduling while atomic! > > > >It indicates a kernel bug, which could range from harmless to very bad. > > > >Usually that message is accompanied by a stack trace, can you provide a > >real log excerpt? > Is this what you need? > > bad: scheduling while atomic! No, I missed the part about a vendor provided driver. You need to report the problem to the vendor or provide the driver source. Lee