From: "Luis Miguel García" <ktech@wanadoo.es>
To: akpm@digeo.com, acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, a.verweij@student.tudelft.nl
Subject: Re: [ACPI] acpi problem with nforce motherboards and ethernet
Date: Thu, 05 Feb 2004 20:25:59 +0100 [thread overview]
Message-ID: <402298C7.5050405@wanadoo.es> (raw)
(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@wanadoo.es> 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@lists.sourceforge.net
>>>>> >> 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@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>>
>>
>>
>
>
>
>
next reply other threads:[~2004-02-05 19:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 19:25 Luis Miguel García [this message]
2004-02-05 19:44 ` [ACPI] acpi problem with nforce motherboards and ethernet David Ford
2004-02-05 21:27 ` Luis Miguel García
2004-02-05 23:40 ` Andrew Morton
2004-02-06 0:08 ` Prakash K. Cheemplavam
2004-02-06 0:14 ` Craig Bradney
2004-02-06 0:22 ` Luis Miguel García
2004-02-06 0:38 ` Prakash K. Cheemplavam
2004-02-06 0:46 ` Luis Miguel García
2004-02-06 0:58 ` Prakash K. Cheemplavam
2004-02-06 1:01 ` Craig Bradney
2004-02-06 1:09 ` Luis Miguel García
2004-02-06 9:28 ` Prakash K. Cheemplavam
2004-02-06 9:26 ` Prakash K. Cheemplavam
2004-02-06 10:07 ` Craig Bradney
2004-02-06 10:40 ` Prakash K. Cheemplavam
2004-02-06 9:44 ` Daniel Drake
2004-02-06 11:04 ` Prakash K. Cheemplavam
2004-02-06 11:15 ` Prakash K. Cheemplavam
2004-02-06 12:51 ` Craig Bradney
2004-02-06 13:10 ` Arjen Verweij
2004-02-06 13:20 ` Prakash K. Cheemplavam
2004-02-06 13:34 ` Arjen Verweij
2004-02-06 13:41 ` Prakash K. Cheemplavam
2004-02-06 13:43 ` Prakash K. Cheemplavam
2004-02-06 11:08 ` Craig Bradney
2004-02-06 0:59 ` Craig Bradney
2004-02-06 0:56 ` Craig Bradney
2004-02-06 23:33 ` Maciej W. Rozycki
2004-02-07 2:50 ` Andi Kleen
2004-02-07 6:39 ` Josh McKinney
2004-02-07 10:04 ` Maciej W. Rozycki
2004-02-07 6:29 ` Luis Miguel García
2004-02-06 9:47 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:41 Luis Miguel García
2004-02-05 18:41 ` [ACPI] " Arjen Verweij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=402298C7.5050405@wanadoo.es \
--to=ktech@wanadoo.es \
--cc=a.verweij@student.tudelft.nl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox