Philip Bliss wrote:
> I am developing a serial driver for linux using coLinux 0.7.4 on a
> Windows 2000 machine, and I get this error message seemingly at random:
>
> BUG: scheduling while atomic: events/0/0x00010000/4
> [<c0103b7a>] show_trace_log_lvl+0x1a/0x30
> [<c0103cb2>] show_trace+0x12/0x20
> [<c0104ae5>] dump_stack+0x15/0x20
> [<c02e61e1>] schedule+0x4d1/0x670
> [<c02e7e63>] __down+0xa3/0x140
> [<c02e7d4a>] __down_failed+0xa/0x10
> [<c025612a>] cocd_interrupt+0x8a/0x100
> [<c013ab91>] handle_IRQ_event+0x31/0x60
> [<c013aeb9>] __do_IRQ+0x79/0x100
> [<c013d0ba>] co_callback+0x16a/0x390
> [<c010a593>] proxy_interrupt_handler+0x43/0x60
> [<c0103873>] common_interrupt+0x23/0x30
> [<c025631d>] cocd_unit_task+0xfd/0x1b0
> [<c0120be4>] run_workqueue+0x84/0x170
> [<c012141c>] worker_thread+0x6c/0xa0
> [<c01241b2>] kthread+0x42/0x70
> [<c0103997>] kernel_thread_helper+0x7/0x10
> =======================
>
> It does not totally bring the system down, but it does end my debugging
> session. Does this make sense to anyone?
Yes, of curse. Please create a Bug entry for this.
Please add your "cat /proc/cmdline" into the report.
Please add the config line for this device also.
I think, there is a coding error in the interrupt handler.
--
Henry N.
|
