lkml.org 
[lkml]   [2003]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] 2.4.23-pre4 add support for udma6 to nForce IDE drive r
Date
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.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.052 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site