From: Ross Dickson <ross@datscreative.com.au>
To: Craig Bradney <cbradney@zip.com.au>
Cc: recbo@nishanet.com, linux-kernel@vger.kernel.org,
Ian Kumlien <pomac@vapor.com>
Subject: Re: Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
Date: Tue, 16 Dec 2003 02:54:45 +1000 [thread overview]
Message-ID: <200312160254.45150.ross@datscreative.com.au> (raw)
In-Reply-To: <1071500545.6680.15.camel@athlonxp.bradney.info>
On Tuesday 16 December 2003 01:02, you wrote:
> Just to give the status here ...
> Im still running the original 2.6 test 11 patches for apic and ioapic.
> Uptime is now 2d 20h with lots of idle time and hard work too..
>
> /proc/interrupts as follows:
>
> CPU0
> 0: 245382420 IO-APIC-edge timer
> 1: 139577 IO-APIC-edge i8042
> 2: 0 XT-PIC cascade
> 8: 3 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 12: 1478615 IO-APIC-edge i8042
> 14: 1055548 IO-APIC-edge ide0
> 15: 737664 IO-APIC-edge ide1
> 19: 18405692 IO-APIC-level radeon@PCI:3:0:0
> 21: 5257090 IO-APIC-level ehci_hcd, NVidia nForce2, eth0
> 22: 3 IO-APIC-level ohci1394
> NMI: 14944
> LOC: 245087891
> ERR: 0
> MIS: 6
Uptime sounds good so far.
I am not convinced my v2 apic patch is a great overall improvement, I am
thinking v1 apic, is safer for now.
Having said that
Ian Kumlien currently has an uptime of
1 day, 15 hours +
on v2 patches but with the apic delay timeout increased from 600UL to 800UL.
He has a Barton core - see below.
>
> Craig
> A7N8X Deluxe V2 BIOS 1007
>
>
<snip>
> > I am currently trying the simpler v1 (always add a delay) patch but on all apic
> > acks as per this posting
> >
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-12/3291.html
> >
> > which is a reply to an earlier posting of the same name but I accidently
> > omitted the Re in the subject.
> >
I don't think it is necessary to put the delay in all apic acks - I just tried it
to see if it worked and have not yet put my code back the way it was.
My hard lockups went away with the original v1 apic
timer delay patch anyway.
Please note in that (above) posting I write that I stuffed up the #ifdefs
in my v1 and v2 patches and adjust code accordingly. Patches worked
but were only testing on the first config item after #ifdef
apic code should have had
#if defined(CONFIG_MK7) && defined(CONFIG_BLK_DEV_AMD74XX)
ioapic code should have had
#if defined(CONFIG_ACPI_BOOT) && defined(CONFIG_X86_UP_IOAPIC)
Brief summary at this point
1) 2? reports are in that latest award bios with "C1 disconnect" set to "auto?"
may remove need for apic ack delay patch and still keep cpu thermo managed
2) apic ack delay v1 patch seems safe for all cpu cores but introduces a small
delay of about half the time of an XTPIC access on each apic timer interrupt
3) apic ack delay v2 patch seems safe only on barton cores and gives more debugging
info and wastes less time than apic v1 patch
4) io-apic v2 patch gives more debugging info but functions same as io-apic v1 patch
Regards
Ross
next prev parent reply other threads:[~2003-12-15 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 14:30 Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ross Dickson
2003-12-15 15:02 ` Craig Bradney
2003-12-15 15:56 ` Maciej W. Rozycki
2003-12-15 16:54 ` Ross Dickson [this message]
2003-12-16 6:07 ` Bob
[not found] <200312132040.00875.ross@datscreative.com.au>
2003-12-13 12:00 ` Fwd: " Bob
2003-12-15 13:11 ` Maciej W. Rozycki
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=200312160254.45150.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--cc=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.com \
--cc=recbo@nishanet.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