The IRQ's are distributed pretty even between the CPU's. eth1 on IRQ5
shows just 1 IRQ and no change after pinging another of our servers. The
data is transmitted thou, as I receive the ping on the other machine.
The other one is also answering.
On my SMP machine I get an error that the IRQ can't be handled and that
may be another device uses it.
There is no other device (as I stripped the machine down to nothing) The
printer is disabled in BIOS. PCI just shows eth1 on IRQ5. And ther is
only one "action" in the IRQ setup.
During boot I looked at all IRQ's and printk'ed the "shared" which the
system is checking they all show a "shared=0" --> single IRQ source.
I looked at other postings and all of them had the redirects. But all
the Kernels were also 4GB kernels, while I am using the 64G Kernal as I
have 4GB RAM + swap. Is there any sense in removing some RAM for testing
The issue with the freezing system is persistent. The only question is
when. Compliling the kernel with standard "make" will hang up the system
hard. Using the option "make -j" will work with no problem.
Alan Cox wrote:
> On Tue, 2002-07-30 at 13:21, Thomas Mierau wrote:
>>I am trying to get the above board to work. Somehow it doesn't.
>>I tried kernel 2.4.18, 2.4.19-rc3, 2.4.19-rc3-ac3 and of course the latest
>>The machine itself is "working" stable under 2.4.18 with a limited
>>functionality (no network, no additional scsi ports, no printer, no usb ...)
> Start by disabling acpi support
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/