From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, rl@hellgate.ch,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [2.6] kernel BUG at arch/i386/mm/highmem.c:14!
Date: Fri, 29 Aug 2003 09:07:27 -0700 [thread overview]
Message-ID: <20030829090727.10ea0099.akpm@osdl.org> (raw)
In-Reply-To: <20030829083556.GB28216@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> > ----------------------------------------------------------------------------
> > hda: DMA disabled
> > bad: scheduling while atomic!
> > Call Trace:
> > [<c011ce00>] schedule+0x510/0x520
> > [<c022a820>] blk_run_queues+0x120/0x300
> > [<c0147e50>] find_get_page+0x70/0x140
> > [<c011ed6e>] io_schedule+0xe/0x20
> > [<c0171f7f>] __wait_on_buffer+0xcf/0xe0
> > [<c011fa80>] autoremove_wake_function+0x0/0x50
> > [<c011fa80>] autoremove_wake_function+0x0/0x50
> > [<c01de17a>] flush_commit_list+0x31a/0x440
> > [<c01e28fb>] do_journal_end+0x5fb/0xc00
> > [<c01e1b79>] flush_old_commits+0x139/0x1d0
> > [<c01cf940>] reiserfs_write_super+0x30/0x40
> > [<c01791bf>] sync_supers+0x1ef/0x280
> > [<c014e143>] wb_kupdate+0x63/0x160
> > [<c011cae2>] schedule+0x1f2/0x520
> > [<c014eb0c>] __pdflush+0x21c/0x5f0
> > [<c014eee0>] pdflush+0x0/0x20
> > [<c014eef1>] pdflush+0x11/0x20
> > [<c014e0e0>] wb_kupdate+0x0/0x160
> > [<c0107259>] kernel_thread_helper+0x5/0xc
>
> These traces look suspicious. Are you using a standard kernel? What
> options?
This trace has been reported several times, and it always correlates with
an IDE error message of some form.
I'm suspecting that something in the IDE error handling path either forgets
to undo a spinlock or leaves interrupts disabled.
prev parent reply other threads:[~2003-08-29 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 17:33 [2.6] kernel BUG at arch/i386/mm/highmem.c:14! Roger Luethi
2003-08-26 18:01 ` Jens Axboe
2003-08-26 19:02 ` Roger Luethi
2003-08-29 8:35 ` Jens Axboe
2003-08-29 16:07 ` 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=20030829090727.10ea0099.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=axboe@suse.de \
--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