linux-mips
[Top] [All Lists]

blast_dcache32 problem with PREEMPT kernel

To: <linux-mips@linux-mips.org>
Subject: blast_dcache32 problem with PREEMPT kernel
From: "Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Date: Fri, 26 Feb 2010 03:41:34 -0800
In-reply-to: <6ec4247d1002251934h2168a03fqdcb8e6f0132aa547@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4B861890.6090002@gmail.com> <201002250852.09638.florian@openwrt.org> <6ec4247d1002251312h37f409bdp2384d7fcbddbb321@mail.gmail.com> <4B872904.6070208@metafoo.de> <6ec4247d1002251934h2168a03fqdcb8e6f0132aa547@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
Thread-index: Acq2lLkpzdnh1eOFT7Gknz8fsHfT3gAQu6Eg
Thread-topic: blast_dcache32 problem with PREEMPT kernel
Hi list,

I am hitting following bug with CONFIG_PREEMP enabled VSMP kernel (
2.6.24) compiled for mips34K core.


BUG: using smp_processor_id() in preemptible [00000001] code:
usb-storage/190
caller is blast_dcache32+0x30/0x25c
Call Trace:
[<8012f338>] vprintk+0x2e8/0x584
[<8012f354>] vprintk+0x304/0x584
[<801111a0>] blast_dcache32+0x30/0x25c
[<80387d5c>] debug_smp_processor_id+0xcc/0xe0
[<801111a0>] blast_dcache32+0x30/0x25c
[<80387d5c>] debug_smp_processor_id+0xcc/0xe0
[<801111a0>] blast_dcache32+0x30/0x25c
[<8010d9e4>] dma_map_sg+0x128/0x144
[<80410a84>] urb_destroy+0x0/0x38
[<801827b0>] kfree+0x8c/0x20c
[<80411944>] usb_sg_init+0x310/0x324
[<8042a708>] usb_stor_bulk_transfer_sg+0xd0/0x174
[<8042a914>] usb_stor_Bulk_transport+0x168/0x324
[<80121a94>] enqueue_entity+0xcc/0x130
[<8042a3f4>] usb_stor_invoke_transport+0x38/0x27c
[<80149ee8>] remove_wait_queue+0x1c/0x60
[<8054568c>] _spin_unlock_irqrestore+0x24/0x44
[<805425fc>] __down_interruptible+0x144/0x1e4
[<801239f0>] default_wake_function+0x0/0x8
[<8042bd58>] usb_stor_control_thread+0x268/0x320
[<801497c0>] kthread+0x0/0xa4
[<80149800>] kthread+0x40/0xa4
[<801241d8>] complete+0x4c/0x6c
[<8042baf0>] usb_stor_control_thread+0x0/0x320
[<80149818>] kthread+0x58/0xa4
[<8010476c>] kernel_thread_helper+0x10/0x18

Any pointers to debug this / fix this will be greatly appreciated.

Thanking you,

Anoop

<Prev in Thread] Current Thread [Next in Thread>