Lines Matching refs:that

3 the Oops" or "running it through ksymoops".  If you post an Oops from 2.6 that
9 Find the Oops and send it to the maintainer of the kernel area that seems to be
28 If the machine has crashed so badly that you cannot enter commands or
36     may find that booting with a higher resolution (eg, vga=791)
63 Actually, there are things you can do that make this easier. I have two 
71 information of which function and the offset in the function that it 
74 Oh, it helps if the report happens on a kernel that is compiled with the 
86 and do a replace of spaces to "\x" - that's what I do, as I'm too lazy 
92 The hex bytes that follow "Code:" may (in some architectures) have a series
93 of bytes that precede the current instruction pointer as well as bytes at and
114 also get from the "oops" message - that can be useful to see _what_ the 
120 "Code" disassembly that didn't match with what the compiler generated). 
122 see that the code uses a NULL pointer and then you look at the code and 
126 Now, if somebody gets the idea that this is time-consuming and requires 
128 mostly just ignore any panic reports that don't have the symbol table 
132 that really requires pretty good knowledge of the kernel just to be able 
135 _Sometimes_ it happens that I just see the disassembled code sequence 
137 I get worried that I've been doing this for too long ;-)
159 translation uses the System.map file in much the same manner that
183 allow klogd to signal the currently executing daemon that symbol
225 counter. This indicates that the kernel has been tainted by some
231      MODULE_LICENSE or with a MODULE_LICENSE that is not recognised by
237   3: 'S' if the oops occurred on an SMP kernel running on hardware that
239      Currently this occurs only on various Athlons that are not
251   7: 'U' if a user or user application specifically requested that the
278 unloaded, the tainted value remains to indicate that the kernel is not