acpi problem with nforce motherboards and ethernet

acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

Hi:

Since Andrew Morton picked up latest acpi bk updates, nforce motherboards have problems, mainly with ethernet adapters. Reporters say that with acpi=off, the problm gets fixed, so we think the problem could be acpi. Some more useful info:



On Tue, 3 Feb 2004, [ISO-8859-1] Luis Miguel García wrote:


>> When I try to boot with latest mm series (such as actual rc3-mm1 or
>> rc2-mm2), my nforce ethernet device doesn't works. It worked in the past
>> with the forcedeth reverse engineered driver but now it keeps for 30 or
>> more seconds halted (at boot) and then the network device dosn't run.
>>
>> Here is the dmesg of rc3-mm1. Do you want for me to test something? Thanks!
>>
>> P.S.:   The ACPI related messages are larger that in rc3.
>  
>

My e100 on an nforce2 won't work in rc3-mm1.
The "acpi=off" boot parameter makes it go.


And for the record, I can boot with that kernel and save one dmesg for you if you want. Only send me a request and I'll send it to you.

P.S.: Sent any messages you want directly to me as i'm not subscribed to acpi-devel.

Thanks,

Luis Miguel García





>Which part of nforce support are you talking about luis?

>On Thu, 5 Feb 2004, Andrew Morton wrote:


>> Luis Miguel Garc?a <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>  
>
>>> >
>>> > Andrew Morton wrote:
>>> >
>>    
>>
>>>> > >
>>>      
>>>
>>>>> > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2/2.6.2-mm1/
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> - Merged some page reclaim fixes from Nick and Nikita.  These yield some
>>>>> > >>  performance improvements in low memory and heavy paging situations.
>>>>> > >>
>>>>> > >>
>>>>        
>>>>
>>> >
>>> > Andrew, do you know if this acpi pull down has nforce support fixed?
>>    
>>
>>
>> It doesn't appear that way.
>>
>  
>
>>> > Or perhaps it's even unnotified to the acpi team?
>>    
>>
>>
>> I do not know.  Sending them a bugzilla ID would help, if such a thing exists.
>>
>>
>>
>> -------------------------------------------------------
>> The SF.Net email is sponsored by EclipseCon 2004
>> Premiere Conference on Open Tools Development and Integration
>> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>> http://www.eclipsecon.org/osdn
>> _______________________________________________
>> Acpi-devel mailing list
>> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>
>>
>  
>


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

(sorry with my sucking english)

ok, let me know if you know for me to test something with this newer mm 
kernels.

by the way, yes, I'm experiencing the lockups. Not with heavy io, but 
almost when I boot and enter X. The system gets completly frozzened and 
the HD led keps on. When I reboot with a sane kernel, I found several 
files from my /home directory are deleted or filled with garbage.

Now, I patch each kernel I use with the two patches Andrew sent to me 
and I'm having no problems.

Actually i'm running 2.6.2-ck1 + nforce-patches and the temperature of 
the system is 55º while idle, and 631 while compiling (only cpu fan, no 
case fans). I don't know if it's high (some people reported high 
temperatures with this patches) but it runs very well this way.

If you want for me to test some patches or something, please drop me a note.

Thanks a lot...

Luis Miguel García

P.S.: by the way, why am I getting strage "arabesque" characters when I 
reply to your emails? Perhaps something with wrong encoding?

>This is interesting, I will test it myself later on. At one point Len
>admitted to owning "foreign hardware :p" so maybe this could get resolved.
>
>Personally I haven't tried kernels with newer forcedeth drivers, because I
>can no longer explicitely set the power state of the NIC to D3. The
>machine complains about irqs (new debugging code since forcedeth v.20 or
>so) and will not powerdown.
>
>On another note, have you noticed lockups of your system with heavy io?
>Think of fsck'ing, burning cdroms, du on large dirs etc? Maybe it is
>helpful to set up a list of boards and document what works or doesn't work
>with which kernel. For instance the lockups with heavy io seem to be
>resolved here if I leave APIC from my kernel.
>
>Arjen
>
>On Thu, 5 Feb 2004, [ISO-8859-15] Luis Miguel Garc?a wrote:
>
>  
>
>>> Hi:
>>>
>>> Since Andrew Morton picked up latest acpi bk updates, nforce motherboards have problems, mainly with ethernet adapters. Reporters say that with acpi=off, the problm gets fixed, so we think the problem could be acpi. Some more useful info:
>>>
>>>
>>>
>>> On Tue, 3 Feb 2004, [ISO-8859-1] Luis Miguel Garc?a wrote:
>>>
>>>
>>    
>>
>>>>> >> When I try to boot with latest mm series (such as actual rc3-mm1 or
>>>>> >> rc2-mm2), my nforce ethernet device doesn't works. It worked in the past
>>>>> >> with the forcedeth reverse engineered driver but now it keeps for 30 or
>>>>> >> more seconds halted (at boot) and then the network device dosn't run.
>>>>> >>
>>>>> >> Here is the dmesg of rc3-mm1. Do you want for me to test something? Thanks!
>>>>> >>
>>>>> >> P.S.:   The ACPI related messages are larger that in rc3.
>>>>        
>>>>
>>>> >
>>>> >
>>>      
>>>
>>>
>>> My e100 on an nforce2 won't work in rc3-mm1.
>>> The "acpi=off" boot parameter makes it go.
>>>
>>>
>>> And for the record, I can boot with that kernel and save one dmesg for you if you want. Only send me a request and I'll send it to you.
>>>
>>> P.S.: Sent any messages you want directly to me as i'm not subscribed to acpi-devel.
>>>
>>> Thanks,
>>>
>>> Luis Miguel Garc?a
>>>
>>>
>>>
>>>
>>>
>>    
>>
>>>> >Which part of nforce support are you talking about luis?
>>>      
>>>
>>>
>>    
>>
>>>> >On Thu, 5 Feb 2004, Andrew Morton wrote:
>>>      
>>>
>>>
>>>
>>    
>>
>>>>> >> Luis Miguel Garc?a <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>>>>        
>>>>
>>>> >
>>>> >
>>>      
>>>
>>>>>>> >>> >
>>>>>>> >>> > Andrew Morton wrote:
>>>>>>> >>> >
>>>>>>            
>>>>>>
>>>>> >>
>>>>> >>
>>>>        
>>>>
>>>>>>>>> >>>> > >
>>>>>>>>                
>>>>>>>>
>>>>>> >>>
>>>>>> >>>
>>>>>          
>>>>>
>>>>>>>>>>> >>>>> > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2/2.6.2-mm1/
>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>> >>>>> > >> - Merged some page reclaim fixes from Nick and Nikita.  These yield some
>>>>>>>>>>> >>>>> > >>  performance improvements in low memory and heavy paging situations.
>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>                    
>>>>>>>>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>> >
>>>>>>> >>> > Andrew, do you know if this acpi pull down has nforce support fixed?
>>>>>>            
>>>>>>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> It doesn't appear that way.
>>>>> >>
>>>>        
>>>>
>>>> >
>>>> >
>>>      
>>>
>>>>>>> >>> > Or perhaps it's even unnotified to the acpi team?
>>>>>>            
>>>>>>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> I do not know.  Sending them a bugzilla ID would help, if such a thing exists.
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> -------------------------------------------------------
>>>>> >> The SF.Net email is sponsored by EclipseCon 2004
>>>>> >> Premiere Conference on Open Tools Development and Integration
>>>>> >> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>>>>> >> http://www.eclipsecon.org/osdn
>>>>> >> _______________________________________________
>>>>> >> Acpi-devel mailing list
>>>>> >> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>>> >> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>>> >>
>>>>> >>
>>>>        
>>>>
>>>> >
>>>> >
>>>      
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> The SF.Net email is sponsored by EclipseCon 2004
>>> Premiere Conference on Open Tools Development and Integration
>>> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>>> http://www.eclipsecon.org/osdn
>>> _______________________________________________
>>> Acpi-devel mailing list
>>> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>
>>    
>>
>
>
>  
>


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[David Ford]

I have the same problem.  I "solved" it a while ago by mucking with the 
AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or something 
similar in cmos.  Went from incredibly broken to stable instantly.  I'll 
check my cmos settings in a bit and refresh my memory.

What patches are you using?

p.s. reiserfs is pretty useless against crashes.  hundreds of files 
around the harddrive get messed up everytime the machine locks 
up...files that haven't been used in weeks, as well as files opened 
read-only, i.e. libraries.

Luis Miguel García wrote:

> (sorry with my sucking english)
>
> ok, let me know if you know for me to test something with this newer 
> mm kernels.
>
> by the way, yes, I'm experiencing the lockups. Not with heavy io, but 
> almost when I boot and enter X. The system gets completly frozzened 
> and the HD led keps on. When I reboot with a sane kernel, I found 
> several files from my /home directory are deleted or filled with garbage.
>
> Now, I patch each kernel I use with the two patches Andrew sent to me 
> and I'm having no problems.
>
> Actually i'm running 2.6.2-ck1 + nforce-patches and the temperature of 
> the system is 55º while idle, and 631 while compiling (only cpu fan, 
> no case fans). I don't know if it's high (some people reported high 
> temperatures with this patches) but it runs very well this way.
>
> If you want for me to test some patches or something, please drop me a 
> note.
>
> Thanks a lot...
>
> Luis Miguel García
>
> P.S.: by the way, why am I getting strage "arabesque" characters when 
> I reply to your emails? Perhaps something with wrong encoding?
>
>> This is interesting, I will test it myself later on. At one point Len
>> admitted to owning "foreign hardware :p" so maybe this could get 
>> resolved.
>>
>> Personally I haven't tried kernels with newer forcedeth drivers, 
>> because I
>> can no longer explicitely set the power state of the NIC to D3. The
>> machine complains about irqs (new debugging code since forcedeth v.20 or
>> so) and will not powerdown.
>>
>> On another note, have you noticed lockups of your system with heavy io?
>> Think of fsck'ing, burning cdroms, du on large dirs etc? Maybe it is
>> helpful to set up a list of boards and document what works or doesn't 
>> work
>> with which kernel. For instance the lockups with heavy io seem to be
>> resolved here if I leave APIC from my kernel.
>>
>> Arjen
>>
>> On Thu, 5 Feb 2004, [ISO-8859-15] Luis Miguel Garc?a wrote:
>>
>>  
>>
>>>> Hi:
>>>>
>>>> Since Andrew Morton picked up latest acpi bk updates, nforce 
>>>> motherboards have problems, mainly with ethernet adapters. 
>>>> Reporters say that with acpi=off, the problm gets fixed, so we 
>>>> think the problem could be acpi. Some more useful info:
>>>>
>>>>
>>>>
>>>> On Tue, 3 Feb 2004, [ISO-8859-1] Luis Miguel Garc?a wrote:
>>>>
>>>>
>>>   
>>>
>>>>>> >> When I try to boot with latest mm series (such as actual 
>>>>>> rc3-mm1 or
>>>>>> >> rc2-mm2), my nforce ethernet device doesn't works. It worked 
>>>>>> in the past
>>>>>> >> with the forcedeth reverse engineered driver but now it keeps 
>>>>>> for 30 or
>>>>>> >> more seconds halted (at boot) and then the network device 
>>>>>> dosn't run.
>>>>>> >>
>>>>>> >> Here is the dmesg of rc3-mm1. Do you want for me to test 
>>>>>> something? Thanks!
>>>>>> >>
>>>>>> >> P.S.:   The ACPI related messages are larger that in rc3.
>>>>>
>>>>>       
>>>>> >
>>>>> >
>>>>
>>>>     
>>>>
>>>> My e100 on an nforce2 won't work in rc3-mm1.
>>>> The "acpi=off" boot parameter makes it go.
>>>>
>>>>
>>>> And for the record, I can boot with that kernel and save one dmesg 
>>>> for you if you want. Only send me a request and I'll send it to you.
>>>>
>>>> P.S.: Sent any messages you want directly to me as i'm not 
>>>> subscribed to acpi-devel.
>>>>
>>>> Thanks,
>>>>
>>>> Luis Miguel Garc?a
>>>>
>>>>
>>>>
>>>>
>>>>
>>>   
>>>
>>>>> >Which part of nforce support are you talking about luis?
>>>>
>>>>     
>>>>
>>>   
>>>
>>>>> >On Thu, 5 Feb 2004, Andrew Morton wrote:
>>>>
>>>>     
>>>>
>>>>
>>>   
>>>
>>>>>> >> Luis Miguel Garc?a <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>>>>>
>>>>>       
>>>>> >
>>>>> >
>>>>
>>>>     
>>>>
>>>>>>>> >>> >
>>>>>>>> >>> > Andrew Morton wrote:
>>>>>>>> >>> >
>>>>>>>
>>>>>>>           
>>>>>>
>>>>>> >>
>>>>>> >>
>>>>>
>>>>>       
>>>>>
>>>>>>>>>> >>>> > >
>>>>>>>>>
>>>>>>>>>               
>>>>>>>>
>>>>>>> >>>
>>>>>>> >>>
>>>>>>
>>>>>>         
>>>>>>
>>>>>>>>>>>> >>>>> > >> 
>>>>>>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2/2.6.2-mm1/ 
>>>>>>>>>>>>
>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>> >>>>> > >> - Merged some page reclaim fixes from Nick and 
>>>>>>>>>>>> Nikita.  These yield some
>>>>>>>>>>>> >>>>> > >>  performance improvements in low memory and 
>>>>>>>>>>>> heavy paging situations.
>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>
>>>>>>>>>>>                   
>>>>>>>>>>
>>>>>>>> >>>>
>>>>>>>> >>>>
>>>>>>>> >>> >
>>>>>>>> >>> > Andrew, do you know if this acpi pull down has nforce 
>>>>>>>> support fixed?
>>>>>>>
>>>>>>>           
>>>>>>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> It doesn't appear that way.
>>>>>> >>
>>>>>
>>>>>       
>>>>> >
>>>>> >
>>>>
>>>>     
>>>>
>>>>>>>> >>> > Or perhaps it's even unnotified to the acpi team?
>>>>>>>
>>>>>>>           
>>>>>>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> I do not know.  Sending them a bugzilla ID would help, if such 
>>>>>> a thing exists.
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> -------------------------------------------------------
>>>>>> >> The SF.Net email is sponsored by EclipseCon 2004
>>>>>> >> Premiere Conference on Open Tools Development and Integration
>>>>>> >> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>>>>>> >> http://www.eclipsecon.org/osdn
>>>>>> >> _______________________________________________
>>>>>> >> Acpi-devel mailing list
>>>>>> >> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>>>> >> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>>>> >>
>>>>>> >>
>>>>>
>>>>>       
>>>>> >
>>>>> >
>>>>
>>>>     
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> The SF.Net email is sponsored by EclipseCon 2004
>>>> Premiere Conference on Open Tools Development and Integration
>>>> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>>>> http://www.eclipsecon.org/osdn
>>>> _______________________________________________
>>>> Acpi-devel mailing list
>>>> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>>
>>>   
>>
>>
>>
>>  
>>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

David Ford wrote:

> I have the same problem.  I "solved" it a while ago by mucking with 
> the AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or 
> something similar in cmos.  Went from incredibly broken to stable 
> instantly.  I'll check my cmos settings in a bit and refresh my memory.
>
> What patches are you using?


I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
Andrew Morton have sent to me. I think they have been included in 
previous mm kernels but now are droped because they caused some 
temperature problems for some people with no nforce motherboards.

If you want it, I can send it to you.

By the way, is anyone involved in solving the IO-APIC thing in nforce 
motherboards? Anyone trying a different approach? Anyone contacting 
nvidia about this problem?


> p.s. reiserfs is pretty useless against crashes.  hundreds of files 
> around the harddrive get messed up everytime the machine locks 
> up...files that haven't been used in weeks, as well as files opened 
> read-only, i.e. libraries.

I don't think this could be a reiserfs problem, because all the computer 
gets frezzed and locked, but perhaps someone at Namesys can realize why 
files gets deleted all over the hard disc.



Thanks.

Luis Miguel Garcia


>
> p.s. reiserfs is pretty useless against crashes.  hundreds of files 
> around the harddrive get messed up everytime the machine locks 
> up...files that haven't been used in weeks, as well as files opened 
> read-only, i.e. libraries.
>
> Luis Miguel García wrote:
>
>> (sorry with my sucking english)
>>
>> ok, let me know if you know for me to test something with this newer 
>> mm kernels.
>>
>> by the way, yes, I'm experiencing the lockups. Not with heavy io, but 
>> almost when I boot and enter X. The system gets completly frozzened 
>> and the HD led keps on. When I reboot with a sane kernel, I found 
>> several files from my /home directory are deleted or filled with 
>> garbage.
>>
>> Now, I patch each kernel I use with the two patches Andrew sent to me 
>> and I'm having no problems.
>>
>> Actually i'm running 2.6.2-ck1 + nforce-patches and the temperature 
>> of the system is 55º while idle, and 631 while compiling (only cpu 
>> fan, no case fans). I don't know if it's high (some people reported 
>> high temperatures with this patches) but it runs very well this way.
>>
>> If you want for me to test some patches or something, please drop me 
>> a note.
>>
>> Thanks a lot...
>>
>> Luis Miguel García
>>
>> P.S.: by the way, why am I getting strage "arabesque" characters when 
>> I reply to your emails? Perhaps something with wrong encoding?
>>
>>> This is interesting, I will test it myself later on. At one point Len
>>> admitted to owning "foreign hardware :p" so maybe this could get 
>>> resolved.
>>>
>>> Personally I haven't tried kernels with newer forcedeth drivers, 
>>> because I
>>> can no longer explicitely set the power state of the NIC to D3. The
>>> machine complains about irqs (new debugging code since forcedeth 
>>> v.20 or
>>> so) and will not powerdown.
>>>
>>> On another note, have you noticed lockups of your system with heavy io?
>>> Think of fsck'ing, burning cdroms, du on large dirs etc? Maybe it is
>>> helpful to set up a list of boards and document what works or 
>>> doesn't work
>>> with which kernel. For instance the lockups with heavy io seem to be
>>> resolved here if I leave APIC from my kernel.
>>>
>>> Arjen
>>>
>>> On Thu, 5 Feb 2004, [ISO-8859-15] Luis Miguel Garc?a wrote:
>>>
>>>  
>>>
>>>>> Hi:
>>>>>
>>>>> Since Andrew Morton picked up latest acpi bk updates, nforce 
>>>>> motherboards have problems, mainly with ethernet adapters. 
>>>>> Reporters say that with acpi=off, the problm gets fixed, so we 
>>>>> think the problem could be acpi. Some more useful info:
>>>>>
>>>>>
>>>>>
>>>>> On Tue, 3 Feb 2004, [ISO-8859-1] Luis Miguel Garc?a wrote:
>>>>>
>>>>  
>>>>
>>>>>>> >> When I try to boot with latest mm series (such as actual 
>>>>>>> rc3-mm1 or
>>>>>>> >> rc2-mm2), my nforce ethernet device doesn't works. It worked 
>>>>>>> in the past
>>>>>>> >> with the forcedeth reverse engineered driver but now it keeps 
>>>>>>> for 30 or
>>>>>>> >> more seconds halted (at boot) and then the network device 
>>>>>>> dosn't run.
>>>>>>> >>
>>>>>>> >> Here is the dmesg of rc3-mm1. Do you want for me to test 
>>>>>>> something? Thanks!
>>>>>>> >>
>>>>>>> >> P.S.:   The ACPI related messages are larger that in rc3.
>>>>>>
>>>>>>
>>>>>    
>>>>> My e100 on an nforce2 won't work in rc3-mm1.
>>>>> The "acpi=off" boot parameter makes it go.
>>>>>
>>>>>
>>>>> And for the record, I can boot with that kernel and save one dmesg 
>>>>> for you if you want. Only send me a request and I'll send it to you.
>>>>>
>>>>> P.S.: Sent any messages you want directly to me as i'm not 
>>>>> subscribed to acpi-devel.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Luis Miguel Garc?a
>>>>>
>>>>>
>>>>>
>>>>  
>>>>
>>>>>> >Which part of nforce support are you talking about luis?
>>>>>
>>>>
>>>>>> >On Thu, 5 Feb 2004, Andrew Morton wrote:
>>>>>
>>>>  
>>>>
>>>>>>> >> Luis Miguel Garc?a <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>>>>>>
>>>>>
>>>>>>>>> >>> >
>>>>>>>>> >>> > Andrew Morton wrote:
>>>>>>>>> >>> >
>>>>>>>>
>>>>>>> >>>>> > >> 
>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2/2.6.2-mm1/ 
>>>>>>>
>>>>>>>
>>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>>> >>>>> > >> - Merged some page reclaim fixes from Nick and 
>>>>>>>>>>>>> Nikita.  These yield some
>>>>>>>>>>>>> >>>>> > >>  performance improvements in low memory and 
>>>>>>>>>>>>> heavy paging situations.
>>>>>>>>>>>>> >>>>> > >>
>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> >>> >
>>>>>>>>> >>> > Andrew, do you know if this acpi pull down has nforce 
>>>>>>>>> support fixed?
>>>>>>>>
>>>>>>>
>>>>>>> >>
>>>>>>> >> It doesn't appear that way.
>>>>>>> >>
>>>>>>
>>>>>   
>>>>>
>>>>>>>>> >>> > Or perhaps it's even unnotified to the acpi team?
>>>>>>>>
>>>>>>>
>>>>>>> >>
>>>>>>> >> I do not know.  Sending them a bugzilla ID would help, if 
>>>>>>> such a thing exists.
>>>>>>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Andrew Morton]

Luis Miguel García <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>
> David Ford wrote:
> 
> > I have the same problem.  I "solved" it a while ago by mucking with 
> > the AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or 
> > something similar in cmos.  Went from incredibly broken to stable 
> > instantly.  I'll check my cmos settings in a bit and refresh my memory.
> >
> > What patches are you using?
> 
> 
> I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
> Andrew Morton have sent to me. I think they have been included in 
> previous mm kernels but now are droped because they caused some 
> temperature problems for some people with no nforce motherboards.

Yes, the patch which disables "Halt Disconnect and Stop Grant Disconnect"
apparently causes the CPU to run hot.

> By the way, is anyone involved in solving the IO-APIC thing in nforce 
> motherboards? Anyone trying a different approach? Anyone contacting 
> nvidia about this problem?

As far as I know, we're dead in the water on these problems.

Here's one:


[x86] do not wrongly override mp_ExtINT IRQ

From: Mathieu <cheuche+lkml-GANU6spQydw@public.gmane.org>.

With this patch timer IRQ0 is correctly set to IO-APIC-edge
(not XT-PIC) on nForce2 boards when using APIC and ACPI.

 arch/i386/kernel/mpparse.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletion(-)

diff -puN arch/i386/kernel/mpparse.c~nforce2-apic arch/i386/kernel/mpparse.c
--- linux-2.6.0-test11/arch/i386/kernel/mpparse.c~nforce2-apic	2003-12-08 00:12:25.782597272 +0100
+++ linux-2.6.0-test11-root/arch/i386/kernel/mpparse.c	2003-12-08 00:12:25.786596664 +0100
@@ -962,7 +962,8 @@ void __init mp_override_legacy_irq (
 	 */
 	for (i = 0; i < mp_irq_entries; i++) {
 		if ((mp_irqs[i].mpc_dstapic == intsrc.mpc_dstapic) 
-			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
+			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)
+			&& (mp_irqs[i].mpc_irqtype == intsrc.mpc_irqtype)) {
 			mp_irqs[i] = intsrc;
 			found = 1;
 			break;

_

Here's the other:


From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz-ZGDBLhmm9VR4rM3dGMyr8Q@public.gmane.org>

[PATCH] fix lockups with APIC support on nForce2

Add PCI quirk to disable Halt Disconnect and Stop Grant Disconnect
(based on athcool program by Osamu Kayasono).

(Mark McPherson <mark-HKnOa/PvsEVBDgjK7y7TUQ@public.gmane.org> reports that this patch causes his CPU
temperature to skyrocket).


 25-akpm/arch/i386/pci/fixup.c |   17 +++++++++++++++++
 1 files changed, 17 insertions(+)

diff -puN arch/i386/pci/fixup.c~nforce2-disconnect-quirk arch/i386/pci/fixup.c
--- 25/arch/i386/pci/fixup.c~nforce2-disconnect-quirk	Mon Jan  5 12:07:45 2004
+++ 25-akpm/arch/i386/pci/fixup.c	Mon Jan  5 12:07:45 2004
@@ -187,6 +187,22 @@ static void __devinit pci_fixup_transpar
 		dev->transparent = 1;
 }
 
+/*
+ * Halt Disconnect and Stop Grant Disconnect (bit 4 at offset 0x6F)
+ * must be disabled when APIC is used (or lockups will happen).
+ */
+static void __devinit pci_fixup_nforce2_disconnect(struct pci_dev *d)
+{
+	u8 t;
+
+	pci_read_config_byte(d, 0x6F, &t);
+	if (t & 0x10) {
+		printk(KERN_INFO "PCI: disabling nForce2 Halt Disconnect"
+				 " and Stop Grant Disconnect\n");
+		pci_write_config_byte(d, 0x6F, (t & 0xef));
+	}
+}
+
 struct pci_fixup pcibios_fixups[] = {
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82451NX,	pci_fixup_i450nx },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82454GX,	pci_fixup_i450gx },
@@ -205,5 +221,6 @@ struct pci_fixup pcibios_fixups[] = {
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_VIA,	PCI_DEVICE_ID_VIA_8367_0,	pci_fixup_via_northbridge_bug },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_NCR,	PCI_DEVICE_ID_NCR_53C810,	pci_fixup_ncr53c810 },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_ANY_ID,			pci_fixup_transparent_bridge },
+	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_NVIDIA,	PCI_DEVICE_ID_NVIDIA_NFORCE2,	pci_fixup_nforce2_disconnect },
 	{ 0 }
 };

_



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Prakash K. Cheemplavam]

>>>What patches are you using?
>>
>>
>>I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
>>Andrew Morton have sent to me. I think they have been included in 
>>previous mm kernels but now are droped because they caused some 
>>temperature problems for some people with no nforce motherboards.
> 
> 
> Yes, the patch which disables "Halt Disconnect and Stop Grant Disconnect"
> apparently causes the CPU to run hot.

Well, my temp is about 6-9°C hotter in idle mode, but with current 
kernels APIC (and no CPU diconnect) seems to be more stable than PIC and 
CPU Disconnect with my nforce. I at least don't have problems with 
forcedeth driver and current acpi.

>>By the way, is anyone involved in solving the IO-APIC thing in nforce 
>>motherboards? Anyone trying a different approach? Anyone contacting 
>>nvidia about this problem?
> 
> 
> As far as I know, we're dead in the water on these problems.

I remember Jesse Allan sending some lspci outputs to Bart to investigate 
the BIOS fix. I wonder what has happened to it. I tried to do a 
comparison with my values, but due to lack of some smart tools to show 
what is common and what is not (diff is not very suitable) it is very 
hard, esp if you have no knowledge about the actual meanings of those 
parameters.

Prakash



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Craig Bradney]

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

On Fri, 2004-02-06 at 00:40, Andrew Morton wrote:
> Luis Miguel García <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
> >
> > David Ford wrote:
> > 
> > > I have the same problem.  I "solved" it a while ago by mucking with 
> > > the AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or 
> > > something similar in cmos.  Went from incredibly broken to stable 
> > > instantly.  I'll check my cmos settings in a bit and refresh my memory.
> > >
> > > What patches are you using?
> > 
> > 
> > I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
> > Andrew Morton have sent to me. I think they have been included in 
> > previous mm kernels but now are droped because they caused some 
> > temperature problems for some people with no nforce motherboards.
> 
> Yes, the patch which disables "Halt Disconnect and Stop Grant Disconnect"
> apparently causes the CPU to run hot.
> 
> > By the way, is anyone involved in solving the IO-APIC thing in nforce 
> > motherboards? Anyone trying a different approach? Anyone contacting 
> > nvidia about this problem?
> 
> As far as I know, we're dead in the water on these problems.


One day hopefully this will be sorted in the BIOSes and in mainline. I
keep having to patch for every release (although as thats the only patch
I have to do I'm sure there are many worse off than me). I use the 3com
n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.

Best patches are at:
http://lkml.org/lkml/2003/12/21/7

Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
issues.

 (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
+exhaust fans in box)

Craig

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

Craig Bradney wrote:

>On Fri, 2004-02-06 at 00:40, Andrew Morton wrote:
>  
>
>>Luis Miguel García <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
>>    
>>
>>>David Ford wrote:
>>>
>>>      
>>>
>>>>I have the same problem.  I "solved" it a while ago by mucking with 
>>>>the AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or 
>>>>something similar in cmos.  Went from incredibly broken to stable 
>>>>instantly.  I'll check my cmos settings in a bit and refresh my memory.
>>>>
>>>>What patches are you using?
>>>>        
>>>>
>>>I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
>>>Andrew Morton have sent to me. I think they have been included in 
>>>previous mm kernels but now are droped because they caused some 
>>>temperature problems for some people with no nforce motherboards.
>>>      
>>>
>>Yes, the patch which disables "Halt Disconnect and Stop Grant Disconnect"
>>apparently causes the CPU to run hot.
>>
>>    
>>
>>>By the way, is anyone involved in solving the IO-APIC thing in nforce 
>>>motherboards? Anyone trying a different approach? Anyone contacting 
>>>nvidia about this problem?
>>>      
>>>
>>As far as I know, we're dead in the water on these problems.
>>    
>>
>
>
>One day hopefully this will be sorted in the BIOSes and in mainline. I
>keep having to patch for every release (although as thats the only patch
>I have to do I'm sure there are many worse off than me). I use the 3com
>n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
>
>Best patches are at:
>http://lkml.org/lkml/2003/12/21/7
>
>Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
>issues.
>
> (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
>+exhaust fans in box)
>
>Craig
>  
>
you mean 31 - 38 C readed from /proc/acpi/temp[........]????

I'm having readings of 53 in idle and even 64 while compiling!! I have 
no case fan, but I don't think it's so important for this bug difference.

by the way, has anyone tried to contact nvidia with detailed information 
of this bug? Perhaps they can tell us something, not to?



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Prakash K. Cheemplavam]

Luis Miguel García wrote:
> Craig Bradney wrote:
> 
>>
>>
>>
>> One day hopefully this will be sorted in the BIOSes and in mainline. I
>> keep having to patch for every release (although as thats the only patch
>> I have to do I'm sure there are many worse off than me). I use the 3com
>> n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
>>
>> Best patches are at:
>> http://lkml.org/lkml/2003/12/21/7
>>
>> Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
>> issues.

Unfortunately that patch doesn't work for me. Still locks if I try APIC 
+CPU DIsc.

>>
>> (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
>> +exhaust fans in box)
>>
>> Craig
>>  
>>
> you mean 31 - 38 C readed from /proc/acpi/temp[........]????
> 
> I'm having readings of 53 in idle and even 64 while compiling!! I have 
> no case fan, but I don't think it's so important for this bug difference.

The problem is, you cannot trust those infos esp not across board 
manufacturers. In case of Abit nearly every bios shows different values...

I have an Athon XP running at 2.1Gz with 1.65vcore. Idle: 50°C (with CPU 
Disc usually about 44-40°C) and under load about 54°C. I am usign a more 
or less self-made watercooling.


Prakash


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [ACPI] acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

Prakash K. Cheemplavam wrote:

> Luis Miguel García wrote:
>
>> Craig Bradney wrote:
>>
>>>
>>>
>>>
>>> One day hopefully this will be sorted in the BIOSes and in mainline. I
>>> keep having to patch for every release (although as thats the only 
>>> patch
>>> I have to do I'm sure there are many worse off than me). I use the 3com
>>> n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
>>>
>>> Best patches are at:
>>> http://lkml.org/lkml/2003/12/21/7
>>>
>>> Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
>>> issues.
>>
>
> Unfortunately that patch doesn't work for me. Still locks if I try 
> APIC +CPU DIsc.
>
>>>
>>> (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
>>> +exhaust fans in box)
>>>
>>> Craig
>>>  
>>>
>> you mean 31 - 38 C readed from /proc/acpi/temp[........]????
>>
>> I'm having readings of 53 in idle and even 64 while compiling!! I 
>> have no case fan, but I don't think it's so important for this bug 
>> difference.
>
>
> The problem is, you cannot trust those infos esp not across board 
> manufacturers. In case of Abit nearly every bios shows different 
> values...
>
> I have an Athon XP running at 2.1Gz with 1.65vcore. Idle: 50°C (with 
> CPU Disc usually about 44-40°C) and under load about 54°C. I am usign 
> a more or less self-made watercooling.
>
>
> Prakash
>

There is a way to "activate" cpu Disconnect? or it gets enabled by 
simply applying it?

Yes, I have a Abit motherboards, perhaps it's the problem with the bios.

Re: acpi problem with nforce motherboards and ethernet

[Craig Bradney]

[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]

On Fri, 2004-02-06 at 01:22, Luis Miguel García wrote:
> Craig Bradney wrote:
> 
> >On Fri, 2004-02-06 at 00:40, Andrew Morton wrote:
> >  
> >
> >>Luis Miguel García <ktech-39ZsbGIQGT7e5aOfsHch1g@public.gmane.org> wrote:
> >>    
> >>
> >>>David Ford wrote:
> >>>
> >>>      
> >>>
> >>>>I have the same problem.  I "solved" it a while ago by mucking with 
> >>>>the AGP stuff.  IIRC, it was turning off AGP fast writes or 8x or 
> >>>>something similar in cmos.  Went from incredibly broken to stable 
> >>>>instantly.  I'll check my cmos settings in a bit and refresh my memory.
> >>>>
> >>>>What patches are you using?
> >>>>        
> >>>>
> >>>I'm using nforce2-apic.patch and nforce2-disconnect-quirk.patch that 
> >>>Andrew Morton have sent to me. I think they have been included in 
> >>>previous mm kernels but now are droped because they caused some 
> >>>temperature problems for some people with no nforce motherboards.
> >>>      
> >>>
> >>Yes, the patch which disables "Halt Disconnect and Stop Grant Disconnect"
> >>apparently causes the CPU to run hot.
> >>
> >>    
> >>
> >>>By the way, is anyone involved in solving the IO-APIC thing in nforce 
> >>>motherboards? Anyone trying a different approach? Anyone contacting 
> >>>nvidia about this problem?
> >>>      
> >>>
> >>As far as I know, we're dead in the water on these problems.
> >>    
> >>
> >
> >
> >One day hopefully this will be sorted in the BIOSes and in mainline. I
> >keep having to patch for every release (although as thats the only patch
> >I have to do I'm sure there are many worse off than me). I use the 3com
> >n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
> >
> >Best patches are at:
> >http://lkml.org/lkml/2003/12/21/7
> >
> >Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
> >issues.
> >
> > (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
> >+exhaust fans in box)
> >
> >Craig
> >  
> >
> you mean 31 - 38 C readed from /proc/acpi/temp[........]????
> 
> I'm having readings of 53 in idle and even 64 while compiling!! I have 
> no case fan, but I don't think it's so important for this bug difference.
> 
> by the way, has anyone tried to contact nvidia with detailed information 
> of this bug? Perhaps they can tell us something, not to?


no.. /sys/bus/i2c

I was highly sceptical that these values were wrong.. but if I was to
shut down and immediately look at the BIOS values.. they are close
enough to make the values I'm quoting to be on the mark. Of course, the
BIOS values could be wrong.

I had the normal Athlon cooler and one rear case fan and it was maxing
out at around 50C. Putting on the Zalman cooler dropped it by 10C.
Adding in the rear fans means it never goes above 39C while compiling.
If the windows open and theres a draft through the room and cold
outside.. :) ..it will idle at 29ish.

Craig



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: acpi problem with nforce motherboards and ethernet

[Craig Bradney]

[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]

On Fri, 2004-02-06 at 01:46, Luis Miguel García wrote:
> Prakash K. Cheemplavam wrote:
> 
> > Luis Miguel García wrote:
> >
> >> Craig Bradney wrote:
> >>
> >>>
> >>>
> >>>
> >>> One day hopefully this will be sorted in the BIOSes and in mainline. I
> >>> keep having to patch for every release (although as thats the only 
> >>> patch
> >>> I have to do I'm sure there are many worse off than me). I use the 3com
> >>> n/w on my A7N8X Deluxe v2 BIOS 1007 so no need for nforcedeth.
> >>>
> >>> Best patches are at:
> >>> http://lkml.org/lkml/2003/12/21/7
> >>>
> >>> Ive applied them to 2.6.0 and 2.6.1 and give no crashes and no heat
> >>> issues.
> >>
> >
> > Unfortunately that patch doesn't work for me. Still locks if I try 
> > APIC +CPU DIsc.
> >
> >>>
> >>> (XP2600+ runs at 31/32C normal use and 38C compiling with Zalman cooler
> >>> +exhaust fans in box)
> >>>
> >>> Craig
> >>>  
> >>>
> >> you mean 31 - 38 C readed from /proc/acpi/temp[........]????
> >>
> >> I'm having readings of 53 in idle and even 64 while compiling!! I 
> >> have no case fan, but I don't think it's so important for this bug 
> >> difference.
> >
> >
> > The problem is, you cannot trust those infos esp not across board 
> > manufacturers. In case of Abit nearly every bios shows different 
> > values...
> >
> > I have an Athon XP running at 2.1Gz with 1.65vcore. Idle: 50°C (with 
> > CPU Disc usually about 44-40°C) and under load about 54°C. I am usign 
> > a more or less self-made watercooling.
> >
> >
> > Prakash
> >
> 
> There is a way to "activate" cpu Disconnect? or it gets enabled by 
> simply applying it?
> 
> Yes, I have a Abit motherboards, perhaps it's the problem with the bios.


I'm not activating Disconnect.. I'm using Ross's latest 2 patches.. one
of them avoids using Disconnect.

Craig

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: acpi problem with nforce motherboards and ethernet

[Daniel Drake]

Luis Miguel García wrote:
> By the way, is anyone involved in solving the IO-APIC thing in nforce 
> motherboards? Anyone trying a different approach? Anyone contacting 
> nvidia about this problem?

Ross said in previous mails that he had tried to contact nvidia through 
various methods, and had not recieved a response.
He also mentioned that AMD were being much more responsive, and he had a 
support request open with them, which he was assured was being investigated.

But yeah, doesn't look like we are getting anywhere with the manufacturers...

Daniel


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: acpi problem with nforce motherboards and ethernet

[Maciej W. Rozycki]

On Thu, 5 Feb 2004, Andrew Morton wrote:

> > By the way, is anyone involved in solving the IO-APIC thing in nforce 
> > motherboards? Anyone trying a different approach? Anyone contacting 
> > nvidia about this problem?
> 
> As far as I know, we're dead in the water on these problems.

 Not necessarily. :-)

> Here's one:
> 
> 
> [x86] do not wrongly override mp_ExtINT IRQ
> 
> From: Mathieu <cheuche+lkml-GANU6spQydw@public.gmane.org>.
> 
> With this patch timer IRQ0 is correctly set to IO-APIC-edge
> (not XT-PIC) on nForce2 boards when using APIC and ACPI.
> 
>  arch/i386/kernel/mpparse.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff -puN arch/i386/kernel/mpparse.c~nforce2-apic arch/i386/kernel/mpparse.c
> --- linux-2.6.0-test11/arch/i386/kernel/mpparse.c~nforce2-apic	2003-12-08 00:12:25.782597272 +0100
> +++ linux-2.6.0-test11-root/arch/i386/kernel/mpparse.c	2003-12-08 00:12:25.786596664 +0100
> @@ -962,7 +962,8 @@ void __init mp_override_legacy_irq (
>  	 */
>  	for (i = 0; i < mp_irq_entries; i++) {
>  		if ((mp_irqs[i].mpc_dstapic == intsrc.mpc_dstapic) 
> -			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
> +			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)
> +			&& (mp_irqs[i].mpc_irqtype == intsrc.mpc_irqtype)) {
>  			mp_irqs[i] = intsrc;
>  			found = 1;
>  			break;

 That's not the right fix.  There's a bug in Linux's ACPI IRQ setup as
I've discovered by comparing the code to the spec.  Here's a patch I sent
in December both to the LKML and the ACPI maintainer.  The feedback from
the list was positive, but the maintainer didn't bother to comment.

 I haven't pushed the patch more firmly, because the MIPS port is my
priority and I don't even have any ACPI-aware equipment.

 Maciej

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro-8Y0ljV8xnLVscumT1wHf3A@public.gmane.org, PGP key available        +

patch-mips-2.6.0-test11-20031209-acpi-irq0-1
diff -up --recursive --new-file linux-mips-2.6.0-test11-20031209.macro/arch/i386/kernel/mpparse.c linux-mips-2.6.0-test11-20031209/arch/i386/kernel/mpparse.c
--- linux-mips-2.6.0-test11-20031209.macro/arch/i386/kernel/mpparse.c	2003-11-25 04:57:01.000000000 +0000
+++ linux-mips-2.6.0-test11-20031209/arch/i386/kernel/mpparse.c	2003-12-11 09:43:26.000000000 +0000
@@ -940,7 +940,7 @@ void __init mp_override_legacy_irq (
 	 *      erroneously sets the trigger to level, resulting in a HUGE 
 	 *      increase of timer interrupts!
 	 */
-	if ((bus_irq == 0) && (global_irq == 2) && (trigger == 3))
+	if ((bus_irq == 0) && (trigger == 3))
 		trigger = 1;
 
 	intsrc.mpc_type = MP_INTSRC;
@@ -961,7 +961,7 @@ void __init mp_override_legacy_irq (
 	 * Otherwise create a new entry (e.g. global_irq == 2).
 	 */
 	for (i = 0; i < mp_irq_entries; i++) {
-		if ((mp_irqs[i].mpc_dstapic == intsrc.mpc_dstapic) 
+		if ((mp_irqs[i].mpc_srcbus == intsrc.mpc_srcbus) 
 			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
 			mp_irqs[i] = intsrc;
 			found = 1;
@@ -1008,9 +1008,10 @@ void __init mp_config_acpi_legacy_irqs (
 	 */
 	for (i = 0; i < 16; i++) {
 
-		if (i == 2) continue;			/* Don't connect IRQ2 */
+		if (i == 2)
+			continue;			/* Don't connect IRQ2 */
 
-		intsrc.mpc_irqtype = i ? mp_INT : mp_ExtINT;   /* 8259A to #0 */
+		intsrc.mpc_irqtype = mp_INT;
 		intsrc.mpc_srcbusirq = i;		   /* Identity mapped */
 		intsrc.mpc_dstirq = i;
 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [ACPI] acpi problem with nforce motherboards and ethernet

[Andi Kleen]

On Sat, 7 Feb 2004 00:33:04 +0100 (CET)
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:


>  That's not the right fix.  There's a bug in Linux's ACPI IRQ setup as
> I've discovered by comparing the code to the spec.  Here's a patch I sent
> in December both to the LKML and the ACPI maintainer.  The feedback from
> the list was positive, but the maintainer didn't bother to comment.

Thanks. I added the patch to the x86-64 sources and it indeed seems to fix
the Nforce3.

-Andi

Re: acpi problem with nforce motherboards and ethernet

[Luis Miguel García]

Maciej W. Rozycki wrote:

>On Thu, 5 Feb 2004, Andrew Morton wrote:
>
>  
>
>>>By the way, is anyone involved in solving the IO-APIC thing in nforce 
>>>motherboards? Anyone trying a different approach? Anyone contacting 
>>>nvidia about this problem?
>>>      
>>>
>>As far as I know, we're dead in the water on these problems.
>>    
>>
>
> Not necessarily. :-)
>
>  
>
>>Here's one:
>>
>>
>>[x86] do not wrongly override mp_ExtINT IRQ
>>
>>From: Mathieu <cheuche+lkml-GANU6spQydw@public.gmane.org>.
>>
>>With this patch timer IRQ0 is correctly set to IO-APIC-edge
>>(not XT-PIC) on nForce2 boards when using APIC and ACPI.
>>
>> arch/i386/kernel/mpparse.c |    3 ++-
>> 1 files changed, 2 insertions(+), 1 deletion(-)
>>
>>diff -puN arch/i386/kernel/mpparse.c~nforce2-apic arch/i386/kernel/mpparse.c
>>--- linux-2.6.0-test11/arch/i386/kernel/mpparse.c~nforce2-apic	2003-12-08 00:12:25.782597272 +0100
>>+++ linux-2.6.0-test11-root/arch/i386/kernel/mpparse.c	2003-12-08 00:12:25.786596664 +0100
>>@@ -962,7 +962,8 @@ void __init mp_override_legacy_irq (
>> 	 */
>> 	for (i = 0; i < mp_irq_entries; i++) {
>> 		if ((mp_irqs[i].mpc_dstapic == intsrc.mpc_dstapic) 
>>-			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
>>+			&& (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)
>>+			&& (mp_irqs[i].mpc_irqtype == intsrc.mpc_irqtype)) {
>> 			mp_irqs[i] = intsrc;
>> 			found = 1;
>> 			break;
>>    
>>
>
> That's not the right fix.  There's a bug in Linux's ACPI IRQ setup as
>I've discovered by comparing the code to the spec.  Here's a patch I sent
>in December both to the LKML and the ACPI maintainer.  The feedback from
>the list was positive, but the maintainer didn't bother to comment.
>
> I haven't pushed the patch more firmly, because the MIPS port is my
>priority and I don't even have any ACPI-aware equipment.
>
> Maciej
>
>  
>
Can you send us the specific patch or at least telling us if you're 
going to push it?

Thanks a lot for the fix ;)

LuisMi Garcia


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn