From: Thomas Gleixner <tglx@linutronix.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.24-git: kmap_atomic() WARN_ON()
Date: Thu, 7 Feb 2008 00:58:42 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802070054220.9204@apollo.tec.linutronix.de> (raw)
current mainline triggers:
WARNING: at /home/tglx/work/kernel/x86/linux-2.6/arch/x86/mm/highmem_32.c:52 kmap_atomic_prot+0xe5/0x19b()
Modules linked in: ahci(+) sata_sil libata sd_mod scsi_mod raid1 ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 0, comm: swapper Not tainted 2.6.24 #173
[<c0126b60>] warn_on_slowpath+0x41/0x51
[<c011c5eb>] ? __enqueue_entity+0x9c/0xa4
[<c011c717>] ? enqueue_entity+0x124/0x13b
[<c011cedb>] ? enqueue_task_fair+0x41/0x4c
[<c032ce88>] ? _spin_lock_irqsave+0x14/0x2e
[<c012e885>] ? lock_timer_base+0x1f/0x3e
[<c011ad6d>] kmap_atomic_prot+0xe5/0x19b
[<c011ae37>] kmap_atomic+0x14/0x16
[<f88ea218>] ata_scsi_rbuf_get+0x1e/0x2c [libata]
[<f88ea821>] atapi_qc_complete+0x23f/0x289 [libata]
[<f88e3d00>] __ata_qc_complete+0x8e/0x93 [libata]
[<f88e3fc7>] ata_qc_complete+0x115/0x128 [libata]
[<f88e8d47>] ata_qc_complete_multiple+0x86/0xa0 [libata]
[<f8841a5d>] ahci_interrupt+0x370/0x40d [ahci]
[<c01512c6>] handle_IRQ_event+0x21/0x48
[<c01521ca>] handle_edge_irq+0xc9/0x10a
[<c0152101>] ? handle_edge_irq+0x0/0x10a
[<c0107518>] do_IRQ+0x8b/0xb7
[<c01055db>] common_interrupt+0x23/0x28
[<c032007b>] ? init_chipset_cmd64x+0xb/0x93
[<c010316e>] ? mwait_idle_with_hints+0x39/0x3d
[<c0103172>] ? mwait_idle+0x0/0xf
[<c010317f>] mwait_idle+0xd/0xf
[<c0103761>] cpu_idle+0xb0/0xe4
[<c031b509>] rest_init+0x5d/0x5f
This is not a new problem. It was pointed out some time ago already,
but now the WARN_ON() finally made it into mainline :)
The fix is not obvious, as this code seems to be called from various
call sites.
Thanks,
tglx
next reply other threads:[~2008-02-07 0:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:58 Thomas Gleixner [this message]
2008-02-13 22:39 ` Rafael J. Wysocki
2008-02-14 1:13 ` Thomas Gleixner
2008-02-25 19:59 ` Björn Steinbrink
2008-02-25 20:08 ` Jeff Garzik
2008-02-25 20:35 ` Björn Steinbrink
2008-02-25 20:40 ` Andrew Morton
2008-02-25 22:01 ` Thomas Gleixner
2008-02-25 22:17 ` Andrew Morton
2008-02-25 23:19 ` Jeff Garzik
2008-02-26 8:39 ` Ingo Molnar
2008-02-26 16:32 ` Jeff Garzik
2008-02-26 18:19 ` Andrew Morton
2008-02-26 20:49 ` Ingo Molnar
2008-02-26 21:37 ` Andrew Morton
2008-02-26 22:59 ` Jeff Garzik
2008-02-27 0:02 ` Alan Cox
2008-02-26 23:49 ` Nick Piggin
2008-02-26 8:50 ` Thomas Gleixner
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=alpine.LFD.1.00.0802070054220.9204@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jgarzik@pobox.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
all inboxes | Powered by JetHome®