| 1 |
Joseph wrote: |
| 2 |
|
| 3 |
>[snip] |
| 4 |
> |
| 5 |
> |
| 6 |
> |
| 7 |
>>>No, I still have the same Sata Drive is just I'm playing with IRQ |
| 8 |
>>>assignment and configuration. |
| 9 |
>>>I've changed to BIOS PnP to YES, so my skge (network controller) and |
| 10 |
>>>libata (Sata Controller are shifted to IRQ 10 |
| 11 |
>>> |
| 12 |
>>>But it makes me wonder both controllers on the Motherboard are different |
| 13 |
>>>chips, so why do they share IRQ? Is there a way to shift them to a |
| 14 |
>>>different IRQ since Linux control IRQ assignment now? |
| 15 |
>>> |
| 16 |
>>> |
| 17 |
>>> |
| 18 |
>>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. |
| 19 |
>> |
| 20 |
>>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 ;-). |
| 21 |
>> |
| 22 |
>>Zac |
| 23 |
>> |
| 24 |
>> |
| 25 |
> |
| 26 |
>Here is what I have done: |
| 27 |
>1.) Disable Network controller on the motherboard and install another |
| 28 |
>one on PCI bus - this eliminate possible IRQ conflict. |
| 29 |
>But it didn't help. |
| 30 |
> |
| 31 |
>2.) Removed the heatsink clean it with 99% isopropyl alcohol and applied |
| 32 |
>thin layer of new heatsink grease. |
| 33 |
> |
| 34 |
>Nothing helped, still getting that message: |
| 35 |
>Kernel panic - not syncing: Aiee, killing interupt handler. |
| 36 |
> |
| 37 |
>Next option, is to try to remove SATA drive and try to install Gentoo on |
| 38 |
>standard IDE drive; this would eliminate SCSI problem and/or buggy |
| 39 |
>driver. |
| 40 |
> |
| 41 |
>Does anybody has any other solutions? |
| 42 |
> |
| 43 |
> |
| 44 |
> |
| 45 |
This isn't exactly a solution and its just a stab in the dark, but... |
| 46 |
|
| 47 |
You're using -march=k8, If I recall. I've read that this causes (or |
| 48 |
used to cause) problems for some people. I believe it had to do with |
| 49 |
poor support by some versions of gcc. I'm sure this is probably no |
| 50 |
longer the case, but I haven't heard one way or the other. I'm using |
| 51 |
-march=athlon64 without any trouble. I don't think you can change this |
| 52 |
flag after the initial installation, though. |
| 53 |
|
| 54 |
-- |
| 55 |
"Pluralitas non est ponenda sine necessitate" - W. of O. |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives