From: Roger Luethi <rl@hellgate.ch>
To: linux-kernel@vger.kernel.org
Subject: [2.6] kernel BUG at arch/i386/mm/highmem.c:14!
Date: Tue, 26 Aug 2003 19:33:37 +0200 [thread overview]
Message-ID: <20030826173337.GA3993@k3.hellgate.ch> (raw)
This BUG immediately followed my turning off DMA on hda (with a mounted
partition and dirty buffers). Register and stack info are available upon
request (screenshot). 2.6.0-test4.
Roger
kernel BUG at arch/i386/mm/highmem.c:14!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c011bc36>] Not tainted
EFLAGS: 00010206
EIP is at kunmap+0x16/0x30
[...]
Process pdflush [...]
[<c0158f69>] __blk_queue_bounce+0x1e9/0x230
[<c0158fe7>] blk_queue_bounce+0x37/0x60
[<c022be20>] __make_request+0x50/0x670
[<c023ccb0>] task_mulout_intr+0x0/0x290
[<c022c584>] generic_make_request+0x144/0x1e0
[<c0176fec>] bio_alloc+0xcc/0x1a0
[<c022c65d>] submit_bio+0x3d/0x70
[<c01c80e0>] reiserfs_write_full_page+0x210/0x350
[<c01c8265>] reiserfs_writepage+0x25/0x40
[<c019ed3f>] mpage_writepages+0x38f/0x4d0
[<c01c8240>] reiserfs_writepage+0x0/0x40
[<c014e375>] do_writepages+0x35/0x40
[<c019c644>] __sync_single_inode+0x194/0x470
[<c010a10c>] common_interrupt+0x18/0x20
[<c019cce1>] sync_sb_inodes+0x1d1/0x3d0
[<c019d041>] writeback_inodes+0x161/0x420
[<c014d0a9>] get_page_state+0x19/0x20
[<c014e1bc>] wb_kupdate+0xdc/0x160
[<c014eb0c>] __pdflush+0x21c/0x5f0
[<c014eee0>] pdflush+0x0/0x20
[<c014eef1>] pdflush+0x11/0x20
[<c014e0e0>] wb_kupdate+0x0/0x160
[<c0107259>] kernel_thread_helper+0x5/0xc
next reply other threads:[~2003-08-26 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 17:33 Roger Luethi [this message]
2003-08-26 18:01 ` [2.6] kernel BUG at arch/i386/mm/highmem.c:14! Jens Axboe
2003-08-26 19:02 ` Roger Luethi
2003-08-29 8:35 ` Jens Axboe
2003-08-29 16:07 ` Andrew Morton
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=20030826173337.GA3993@k3.hellgate.ch \
--to=rl@hellgate.ch \
--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