mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Allen Martin <AMartin@nvidia.com>, "'Merlin Hughes'" <lnx@merlin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.23-pre4 add support for udma6 to nForce IDE drive  r
Date: Sat, 20 Sep 2003 09:33:48 +0100	[thread overview]
Message-ID: <200309200933.48696.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <8F12FC8F99F4404BA86AC90CD0BFB04F039F714A@mail-sc-6.nvidia.com>

On Saturday 20 September 2003 00:49, Allen Martin wrote:
> > Interesting; lots of ACPI edge-triggered interrupts:
> >
> >   dagda:~# cat /proc/interrupts
> >              CPU0
> >     0:     519365    IO-APIC-edge  timer
> >     1:      16713    IO-APIC-edge  keyboard
> >     2:          0          XT-PIC  cascade
> >     8:          4    IO-APIC-edge  rtc
> >     9:          0   IO-APIC-level  acpi
> >    14:     863415    IO-APIC-edge  ide0
> >    15:     201651    IO-APIC-edge  ide1
> >    19:     306188   IO-APIC-level  nvidia
> >    20:      57261   IO-APIC-level  usb-ohci, eth0
> >    21:          0   IO-APIC-level  ehci_hcd, NVidia nForce2
> >    22:          3   IO-APIC-level  usb-ohci, ohci1394
> >   NMI:          0
> >   LOC:     519312
> >   ERR:          0
> >   MIS:          0
>
> Your interrupts look fine, this is the way they should be.
>
> > ... but no stability problems since the primary drive has been
> > running at UDMA133. Earlier UDMA100 freezes were completely
> > repeatable; identical kernel, just without your two patches.
>
> You can try downgrading your drive to udma5 to see if udma6 really does
> make it more stable (hdparm -X udma5 /dev/hdX) but I can't think of any
> reason why it should.
>
> > I take it that I should boot with noapic in future to be safe.
>
> I've been telling people to disable APIC / ACPI because of the interrupt
> problem, but your interrupts are fine, so I'd leave it alone.  I'm curious,
> what version BIOS do you have?

ACPI/APIC should work on most nforce/nforce2 boards in 2.4.22 upwards. If not, 
let me know, and I'll look into it.


  parent reply	other threads:[~2003-09-20  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 23:49 Allen Martin
2003-09-20  2:26 ` Merlin Hughes
2003-09-20  8:33 ` Andrew de Quincey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-19 23:08 Allen Martin
2003-09-19 23:34 ` Merlin Hughes
2003-09-18  4:09 Allen Martin

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=200309200933.48696.adq_dvb@lidskialf.net \
    --to=adq_dvb@lidskialf.net \
    --cc=AMartin@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnx@merlin.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

all inboxes | Powered by JetHome®