> Call Trace > [<c01269b8>] __do_softirq + 0x4c/0xb1 > [<........>] do_softirq > ------------------------------------------ > ------------------------------------------ > [<........>] smp_apic_times_interrupt > [<........>] apic_times_interrupt > [<........>] mwait_idle > [<........>] cpu_idle > [<........>] start_kernel > > code : <hexadecimals...> > > It is a kernel panic/crash, right? I was wondering if > the crash was related to the program (it didn't core dump > even after setting ulimit -c <large number>) >
Right. Possibly not related to your program but due to a kernel module bug. > Is it possible for a software to crash a kernel? If > there's a bug, the program should have produce a > segmentation fault and exit without affecting the kernel. > Yes. Everything is interconnected. For example if your fire up a browser, eventually the http packets go down the network driver. So, if the network driver is buggy, the browser essentially could trigger the kernel panic. > Is there a way of knowing if the kernel panic is > caused by a flaky hardware or is caused by a buggy > software? > Kernel panic is caused by a buggy kernel module. In your case, it appears that the problem starts with the advanced programmable interrupt controller handling the timer interrupt. > I'm trying to make sure it is not the kernel per se > that causes the crash by downloading the latest kernel. > It may help only if the maintainer is aware and has fixed the problem. Might be a good idea to test your software on a different hardware. rowel _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
