Further Oops Insights

"'[The] text below is mostly for the benefit of newbies--it's more along the lines of 'how to get from [a] bug report to the source of [the] bug', with more details than normal,' began Al Viro, offering a full review of another Linux kernel oops in an effort to educate more people on how this is done. Al's walk through included a patch to fix the bug that caused the oops. He noted:

"'This might be worth doing on [a] more or less regular basis, especially if more people join the fun; everyone [has] their own set of tricks in [this] area and making it easier to gather might help a lot of people. It's not just about oops-tracing per se, of course--Arjan's site gives a nice collection of those, so that makes an obvious starting point...'"

Complete Story

Related Stories:

• Linux Guru Offers Sneak Peek at Kernel Report(Jan 10, 2008)
• Kernel Space: Kerneloops, Read-Mostly, and I/O Port 80(Jan 10, 2008)
• Decoding Oops(Jan 10, 2008)