These are the most dangerous and useful defines. They do printk() during * the interrupt processing routine(s),

Related:

• printk("??? No FDIV bug? Lucky you...\n");
  2.2.16 /usr/src/linux/include/asm-i386/bugs...
• panic("esp_handle: current_SC == penguin within interrupt!");
  2.2.16 /usr/src/linux/drivers/scsi/esp...
• printk("autofs: Out of inode numbers -- what the heck did you do?
  \n"); 2.0.38 /usr/src/linux/fs/autofs/root...
• printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n");
  2.2.16 /usr/src/linux/drivers/char/msp3400...
• printk(KERN_WARNING "%s: Short circuit detected on the lobe\n",
  dev->name); 2.4.0-test2 /usr/src/linux/drivers/net/tokenring/lanstreamer...
• panic("IRQ, you lose...");
  2.2.16 /usr/src/linux/arch/mips/sgi/kernel/indy_int...
• interrupt 1. [techspeak] n. On a computer, an event that interrupts normal processing and temporarily diverts flow-of-control through an "interrupt handler" routine.
  See also trap. 2. interj. A request for attention...
• interrupt: 1. [techspeak] n. On a computer, an event that interrupts normal processing and temporarily diverts flow-of-control through an "interrupt handler" routine.
  See also {trap}. 2. interj. A request for attention...
• panic("mother...");
  2.2.16 /usr/src/linux/drivers/block/cpqarray...