Well, interrupts (irq's) and signals are quite different beasts.
Interrupts are notifications that hardware components send to the processor
(and thus to the driver software) to draw attention to specific events.
Signals (in a Unix context) are notifications the operation system (or some
other source) sends to a process. They have nothing in common, except
perhaps - they have numbers :-)
see 'man 7 signal' for infos about the latter.
sig 11 informs a process that it attempted to access unavailable/invalid
memory or similar. That can be caused by either: a broken program, or (more
probably when 'supposed to be well tested' programs are affected):
broken hardware (overclocked system, bad memory/processor/mainboard/pci....)
> done. Didn't seem to be any options in bios setup for forcing irqs per card
> or subsystem. Eventually doing manual config of ip settings solved the
> problem, although I fail to see how an ethernet driver doing bootp/dhcp
[...]
> problem right at the end of the file-copy process. The first time that the
> problem disappeared was when I turned of a scsi cdr drive before booting for
> the install... hmmm..... The bios of that box reports no such irq conflicts
> on boot.
again: raised signals are no irq-conflicts
>
Thorsten
-- | Thorsten Kranzkowski Internet: dl8bcu@gmx.net | | Mobile: ++49 161 7210230 Snail: Niemannsweg 30, 49201 Dissen, Germany | | Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/