From: Lee Revell <rlrevell@joe-job.com>
To: David L <idht4n@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad: scheduling while atomic!: how bad?
Date: Sat, 18 Jun 2005 20:50:33 -0400 [thread overview]
Message-ID: <1119142233.4560.45.camel@mindpipe> (raw)
In-Reply-To: <BAY104-F33EC080F521153F56952B884F70@phx.gbl>
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
prev parent reply other threads:[~2005-06-19 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 21:59 bad: scheduling while atomic!: how bad? David L
2005-06-18 22:10 ` Arjan van de Ven
2005-06-18 22:49 ` David L
2005-06-18 22:52 ` Arjan van de Ven
2005-06-18 23:19 ` David L
2005-06-18 23:46 ` Arjan van de Ven
2005-06-18 22:18 ` Lee Revell
2005-06-18 22:33 ` David L
2005-06-19 0:50 ` Lee Revell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1119142233.4560.45.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=idht4n@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox