From: Andrew Morton <akpm@osdl.org>
To: Roger Luethi <rl@hellgate.ch>
Cc: linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [2.5.74] bad: scheduling while atomic!
Date: Fri, 4 Jul 2003 19:28:06 -0700 [thread overview]
Message-ID: <20030704192806.76f07845.akpm@osdl.org> (raw)
In-Reply-To: <20030704153407.GA3540@k3.hellgate.ch>
Roger Luethi <rl@hellgate.ch> wrote:
>
> I haven't had the time to investigate this, so I don't have much
> information to share beyond the trace below. I think I have seen this at
> least with 2.5.73, too. The system looks okay, then, usually hours later
> (if at all, it's a rare event), something triggers a flood of those call
> traces (many of them per second).
>
> The syslog seems to suggest it might be related to IDE DMA:
>
> Jul 4 17:17:28 [kernel] hda: dma_timer_expiry: dma status == 0x61
> Jul 4 17:17:44 [kernel] hda: timeout waiting for DMA
> Jul 4 17:17:44 [kernel] [<c0107000>] default_idle+0x0/0x40
> Jul 4 17:17:44 [kernel] bad: scheduling while atomic!
>
> Compiler is gcc 3.2.3.
>
> bad: scheduling while atomic!
> Call Trace:
> [<c0107000>] default_idle+0x0/0x40
> [<c011f110>] schedule+0x500/0x510
> [<c0107063>] poll_idle+0x23/0x40
> [<c0118073>] apm_cpu_idle+0xa3/0x140
> [<c0117fd0>] apm_cpu_idle+0x0/0x140
> [<c0107000>] default_idle+0x0/0x40
> [<c01070b8>] cpu_idle+0x38/0x40
> [<c0105000>] rest_init+0x0/0x30
> [<c037c738>] start_kernel+0x138/0x140
> [<c037c4c0>] unknown_bootoption+0x0/0x100
Possibly the IDE error handler has a locking imbalance. It returned from
the interrupt handler without having unlocked a lock which it should have
unlocked, and that left the currently-running process (the idle task in
this case) with an incorrect preempt count.
prev parent reply other threads:[~2003-07-05 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 15:34 [2.5.74] bad: scheduling while atomic! Roger Luethi
2003-07-05 2:28 ` Andrew Morton [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=20030704192806.76f07845.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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