mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Allen Martin <AMartin@nvidia.com>
To: "'ross.alexander@uk.neceur.com'" <ross.alexander@uk.neceur.com>,
	Brad House <brad@mcve.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
Date: Wed, 29 Oct 2003 11:17:26 -0800	[thread overview]
Message-ID: <DCB9B7AA2CAB7F418919D7B59EE45BAF49F79E@mail-sc-6.nvidia.com> (raw)

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

> -----Original Message-----
> From: ross.alexander@uk.neceur.com 
> [mailto:ross.alexander@uk.neceur.com] 
> Sent: Wednesday, October 29, 2003 6:35 AM
> To: Brad House
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
> 
> 
> Brad,
> 
> My problem is one of the infamous nforce2 hardlockups.  You 
> don't get any
> kernel panic or anything that useful.  The system just locks 
> up completely
> and has to be manually reset.
> 
> The problem is known to associate with IDE activity and is 
> thought (as far
> as I know) to originate somewhere in the IDE driver.
> 
> Cheers,
> 
> Ross
> 
> --------------------------------------------------------------
> -------------------
> Ross Alexander                           "We demand clearly defined
> MIS - NEC Europe Limited            boundaries of uncertainty and
> Work ph: +44 20 8752 3394         doubt."
> 
> 
> 
> 
> Brad House <brad@mcve.com>
> 10/29/2003 02:13 PM
>  
>         To:     ross.alexander@uk.neceur.com
>         cc:     Brad House <brad_mssw@gentoo.org>, 
> linux-kernel@vger.kernel.org
>         Subject:        Re: nforce2 stability on 2.6.0-test5 and 
> 2.6.0-test9
> 
> 
> Hmm, interesting. The patches I submitted were strictly
> for IDE/ATA133 improvements, apparently your problems don't
> lie there.  I'd assume this was a kernel panic you had, any
> output available that would tell you where it paniced ?
> 
> -Brad
> 
> ross.alexander@uk.neceur.com wrote:
> > Brad,
> > 
> > I'm running an ASUS A7N8X Deluxe mobo (nforce2 chipset) and still
> > getting hardlockups.  I applied your patch but my system 
> still locked
> > up after about a day.  However 2.6.0-test5 seems to be 
> stable.  I have
> > had my system up for over three weeks with APIC and ACPI turned on.
> > 
> > Just to let you know,
> > 
> > Ross
> > 
> > 
> --------------------------------------------------------------
> -------------------
> > Ross Alexander                           "We demand clearly defined
> > MIS - NEC Europe Limited            boundaries of uncertainty and
> > Work ph: +44 20 8752 3394         doubt."
> > 
> 
> 
> 
> 
> -
> 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/
> 

             reply	other threads:[~2003-10-29 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 19:17 Allen Martin [this message]
2003-10-30  9:11 ` ross.alexander
2003-10-30 12:46 ` really bensoo_at_soo_dot_com
  -- 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=DCB9B7AA2CAB7F418919D7B59EE45BAF49F79E@mail-sc-6.nvidia.com \
    --to=amartin@nvidia.com \
    --cc=brad@mcve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.alexander@uk.neceur.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

all inboxes | Powered by JetHome®