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?    

I recall that there was some option in kernel configuration, that talked
about verbose reporting. That could cause panic print backtrace just as
OOPS does. But I am not sure where exactly I saw it.

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
--
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