Schduling while atomic

[hllywood@nmt.edu (Scott Miller)]

On Mon, 13 Jan 2003, Russell King - ARM Linux wrote:

> You need to give us a little more than just that.  You should have a
> stack trace, which you should be able to decode into symbols via the
> corresponding System.map.

bad: scheduling while atomic!
Function entered at [<c0020810>] from [<c0031820>]
Function entered at [<c00317d4>] from [<c001ca2c>]
r7 = C01A15CC  r6 = C01A15D8  r5 = C0190000  r4 = C001C978
Function entered at [<c001c9cc>] from [<c0017070>]
r5 = C0190000  r4 = C01A8294
Function entered at [<c0017000>] from [<c00086a4>]
Function entered at [<c0008574>] from [<c0008080>]
r5 = C01B9794  r4 = C01B9794

The functions decode to be:
c0020810 T dump_stack
c00317d4 T schedule
c001c9cc T cpu_idle
c0017000 ? __init_end
c0017000 t rest_init
c0017000 T _text
c0008574 ? start_kernel

Does this help?

- Sincerely,
Scott A. Miller
+-------------------------------------------------------+
| I'm seated in the arm-chair of animosity, next to the |
| throne of denial, across from the sofa of sloth.      |
|      - Hector on the living room furniture            |
+-------------------------------------------------------+