Hi Tony, It's similar to an Oops output, but not equal, probably it's different for different architecture. So, if i'm right, you can find some explaination in the file: Documentation/oops-tracing.txt and in a many other internet page (searching something related to "oops") In short, it tell the status just before the illegal istruction. i could Just guess some things: > PC: [<c00102bc>] tasklet_action+0xbe/0xd2 I think that's where the program counter is at that moment. Looking at it you could imagine what's the problem, or at least where it happens. 0xbe word after tasklet_action starts. > SR: 2010 SP: c0733ae0 a2: c2dd92c0 > d0: 00000024 d1: 00000074 d2: c01f4c60 d3: 00000009 > d4: c30f230c d5: c30b6ca0 a0: c2dd9486 a1: c01b37e8 and theese are the other register (so, you should know how your architecture use stack and registers). Here you can see if there's some completely wrong parameters, or pointer, or whatever... The rest seem quite intelligible. > Kernel panic - not syncing: Aiee, killing interrupt handler! Aieee?? LOL !!! Hope this helps, and i hope i didn't tell anything wrong. Bye! -- -gaspa- ----------------------------------------------- --------- Powered by Debian GNU/Linux --------- ------ HomePage: iogaspa.altervista.org ------- -Il lunedi'dell'arrampicatore: www.lunedi.org - -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
