From: really bensoo_at_soo_dot_com <lnx-kern@soo.com>
To: "linux-kernel @ vger . kernel . org Allen Martin" <AMartin@nvidia.com>
Subject: Re: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
Date: Thu, 30 Oct 2003 07:46:40 -0500 [thread overview]
Message-ID: <20031030074640.A3992@Sophia.soo.com> (raw)
In-Reply-To: <DCB9B7AA2CAB7F418919D7B59EE45BAF49F79E@mail-sc-6.nvidia.com>; from AMartin@nvidia.com on Wed, Oct 29, 2003 at 11:17:26AM -0800
Just as a point of info; i have had these lockup
probs too. Have a MSI K7N2 with nVidia TNT2
vidcard. Using kernel 2.6.0-test9.
When i run mldonkey (file sharing) the box will
lock up solid after a random amount of time in
X no matter what combo of ACPI / no ACPI, PIO / UDMA.
Sometimes the mouse pointer keeps moving for up
to ~30 sec before it too freezes. During this
interval there's no ATA activity and i can reboot
the box with SysReq key combos. If i wait until
the mouse freezes then the box is completely
locked and the SysReq keys don't work anymore.
HOWEVER, if i adjust the process priority of
mldonkey to -20, then the box doesn't lock up
anymore with ACPI and local APIC enabled and will
keep running forever and even burn DVD or CD's
while playing a video rip while compiling something.
There's the sporatic ~1 sec freeze when mldonkey
grabs the whole CPU but it always comes back.
regards,
On Wed, Oct 29, 2003 at 11:17:26AM -0800, Allen Martin wrote:
> Hi Ross, can you post the contents of /proc/interrupts, /proc/ide/amd74xx
> and /proc/ide/ide*/config, and also the output of "hdparm -I /dev/hd*" for
> each of your ATA / ATAPI devices?
>
> If the PIO and UDMA modes are setup correctly I can't think of anything
> inside the IDE driver that should be causing random lockups. I'd be much
> more suspicious of ACPI / APIC / interrupt setup.
>
> -Allen
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-10-30 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 19:17 nforce2 stability on 2.6.0-test5 and 2.6.0-test9 Allen Martin
2003-10-30 9:11 ` ross.alexander
2003-10-30 12:46 ` really bensoo_at_soo_dot_com [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 5:08 Justin Ossevoort
2003-11-05 0:38 Allen Martin
2003-11-04 9:00 ross.alexander
2003-11-03 18:36 Allen Martin
2003-10-29 15:07 Denis Perchine
2003-10-29 11:57 ross.alexander
2003-10-29 14:13 ` Brad House
2003-10-29 14:35 ` ross.alexander
2003-10-29 14:52 ` Brad House
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=20031030074640.A3992@Sophia.soo.com \
--to=lnx-kern@soo.com \
--cc=AMartin@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).