On Thu, 6 Mar 2003, Eje Gustafsson wrote: > Ok. You can now call me stupid. I don't know how to use patch today. > > blah. > cd /usr/src/linux-2.4/ > patch -p1 < ../patch-2.4.20ctx-16
Actually -p0 works too and is what I found in the kernel documentation. > And we are done.. ugh. But still what can I do to help out better > track down the cause of the kernel crashes ? In my years of Linux I > never needed to do any kernel debugging. Usually just upgrade kernel > to newer version always fixed any kernel panics I had ;P I ran into a clash between an Adaptec 29160 SCSI card and the DAViCOM NICs. As soon as I swapped the cards out the system would boot. (I wasn't about to give up the 26160 card so I never swapped it out. :-) I also know of two system that use a 2.0.x kernel (RHL 6.x) and Equinox multiport boards. Around 248-255 days of up time the systems lock up tight. The messages on the console were useless. My point being sometimes there isn't a technique but a gut feeling. Rod -- "Open Source Software - Sometimes you get more than you paid for..."
