Chapter 30. Network Troubles
For this example, we’ve got a system that panic’ed several times with essentially the same error: a bad pointer. The trace information indicated that it was a problem in the networking code in the kernel. It’s an easy one to solve (or at least fix), because in this case a patch for the problem was readily available.
We’ll go through the analysis procedures, take a short detour to verify that the problem was real, and look for a solution in the SunSolve bug and patch databases.
Initial analysis
This system was a fairly new SPARCstation 5, running SunOS 4.1.3_U1. (We’ll verify that, leaving nothing to chance.) This means we need to analyze the crash on a comparable system: a sun4m architecture, running the same version ...
Get Panic! UNIX® System Crash Dump Analysis now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
