Joseph wrote:

[snip]

No, I still have the same Sata Drive is just I'm playing with IRQ
assignment and configuration.
I've changed to BIOS PnP to YES, so my skge (network controller) and
libata (Sata Controller are shifted to  IRQ 10

But it makes me wonder both controllers on the Motherboard are different
chips, so why do they share IRQ?  Is there a way to shift them to a
different IRQ since Linux control IRQ assignment now?
A quick look through linux/Documentation/kernel-parameters.txt shows that many 
drivers support direct irq assignment.  Also, linux/Documentation/pnp.txt may 
be of use.

Considering the positive results that you've gotten so far, it seems like you 
may be on the right track here.  It makes me less concerned about any possible 
overheating, but if you wanted to be paranoid about it, you could get another 
heat probe to double check the readings from the first one ;-).

Zac

Here is what I have done:
1.) Disable Network controller on the motherboard and install another
one on PCI bus - this eliminate possible IRQ conflict.
But it didn't help.

2.) Removed the heatsink clean it with 99% isopropyl alcohol and applied
thin layer of new heatsink grease.

Nothing helped, still getting that message:
Kernel panic - not syncing: Aiee, killing interupt handler.

Next option, is to try to remove SATA drive and try to install Gentoo on
standard IDE drive; this would eliminate SCSI problem and/or buggy
driver.

Does anybody has any other solutions?

This isn't exactly a solution and its just a stab in the dark, but...

You're using -march=k8, If I recall. I've read that this causes (or used to cause) problems for some people. I believe it had to do with poor support by some versions of gcc. I'm sure this is probably no longer the case, but I haven't heard one way or the other. I'm using -march=athlon64 without any trouble. I don't think you can change this flag after the initial installation, though.
--
"Pluralitas non est ponenda sine necessitate" - W. of O.

--
gentoo-user@gentoo.org mailing list

Reply via email to