OOPS FAQ (was: OOPS (may be an attack))

Ion Badulescu (ionut@moisil.cs.columbia.edu)
Thu, 25 Mar 1999 15:00:09 +0200


On Wed, 24 Mar 1999 11:00:53 EST, Catalin BOIE wrote:

> Today I got an oops:
>
> Call trace: [<c010addd>] [<c0118ea1>] [<c01091a7>] [<c01103c6>] [<c0108d4d>] [<c0183698>] [<c010b15f>] [<c0108cd0>]
>
> Trace: c010addd <synchronize_bh+39/4c>
> Trace: c0118ea1 <do_exit+65/2ac>
> Trace: c01091a7 <die+53/54>
> Trace: c01103c6 <do_page_fault+2d2/324>
> Trace: c0108d4d <error_code+2d/40>
> Trace: c0183698 <scrup+74/10c>
> Trace: c010b15f <do_IRQ+1b/54>
> Trace: c0108cd0 <ret_from_intr+0/20>

Don't try to filter what you don't understand.

Despite what some people might think, the kernel does _not_ log 10+ lines
for one OOPS just for the hell of it. They are necessary for understanding
the state of the CPU at the time of the event.

As presented above, the report is 99% useless.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/