Re: How to find what was wrong when kernel is panic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 16, 2003 at 05:44:59PM -0400, Hong Hsu wrote:
> Hi,
> 
> Recently I installed a standalone module on redhat kernel 2.4.18-3. 
> After setup device file,
> #mknod  /dev/x10/c3   c  120  34
> 
> The lsmod shows the module x10_plusb is loaded.  The hwbrowser shows the 
> hardware PowerLincUSB is recognized.
> I tried to test it:
> #echo on > /dev/x10/c3
> 
> it locked system with error message:
> kernel panic: Aiee, killing interrupt handler!
> 
> At this point, I have to reboot the machine.  Where I should start to 
> find out what is wrong with the driver, OR module?    
> 
> Thanks for your help,

Check out lkcd kernel patch, it produces core dump and it enables you to
backtrace what was going on before panic.

-- 
[Time is a great teacher, but unfortunately it kills all its pupils]
			[Hector Berlioz]
[tjup$gazeta%pl] - Krzysztof Witkowski
./mmu_context.h:/* Fuck.  The f-word is here so you can grep for it :-)  */
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux