From: Jesse Allen <the3dfxdude@hotmail.com>
To: Ross Dickson <ross@datscreative.com.au>
Cc: Len Brown <len.brown@intel.com>,
a.verweij@student.tudelft.nl,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
Craig Bradney <cbradney@zip.com.au>,
christian.kroener@tu-harburg.de, linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Jamie Lokier <jamie@shareable.org>,
Daniel Drake <dan@reactivated.net>, Ian Kumlien <pomac@vapor.com>,
Allen Martin <AMartin@nvidia.com>
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5
Date: Thu, 29 Apr 2004 13:24:13 -0700 [thread overview]
Message-ID: <20040429202413.GA1982@tesore.local> (raw)
In-Reply-To: <200404292144.37479.ross@datscreative.com.au>
On Thu, Apr 29, 2004 at 09:44:37PM +1000, Ross Dickson wrote:
> On Thursday 29 April 2004 06:59, Jesse Allen wrote:
> > almost in unison with the sound coming from the computer. Maybe the IDE or
> > hard drive is related, but it is too much related to C1 disconnect.
>
> I think I might break out my oscilloscope this weekend and have a look at how
> clean the supply rails are around the cpu and northbridge and southbridge.
> Who knows I might get lucky and see some unexpected ripple or spikes.
I'd be interested in knowing the results.
> > resonance can break systems. But to think that my board is doing emmitting
> > noise like that is pretty bizarre.
>
> Not as bizarre as you may think. I have heard coils and even capacitors "sing"
> in years past whilst servicing electronics.
Yes, I know that these things can theorectically happen. But when it happens
to me, it's a suprise. To an electronics genius, he probably encounters it
more often. =)
> > C1 handshake time? Isn't that much like what your patch does?
>
> I had not really thought about it from that perspective. Whilst my patch cannot
> alter the handshake times it does prevent consecutive C1 cycles from occurring
> too close together. Too close together I think being less than about 800ns. I
ah, ok.
> guess I could look at that with a cro too - use an appropriate pin as the
> trigger source and see if supply rails have load dump voltage rises when
> going into disconnect. Maybe rail voltage rings for about 700ns and might be
> out of tolerence inside Athlon during that time. Would be very interesting if
> a few hundred picofarad of low esr decoupling cap placed on a supply rail
> near a chip makes a difference? A pinout of the nforce2 chipset would help a
> great deal here but I do not have one. Can anyone oblige me?
What I'd like to know is where the sound chip is really at on my board. I've
tried looking before, but find myself confused.
A pic:
http://us.shuttle.com/images/productimages/AN35.jpg
According to a diagram that I have, it points to an AC'97 6-CH AUDIO as a chip
near of the top of the board in the image that I link to, above 2nd PCI slot
left of the AGP. But I'm am also left thinking, how does the NForce2 MCP come
into play. Specs would help. Maybe if we can figure out how the sound is
wired on the board, we could also trace the source of noise to the exact
component.
Jesse
next prev parent reply other threads:[~2004-04-29 20:24 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 1:17 IO-APIC on nforce2 Ross Dickson
2004-04-13 4:01 ` really bensoo_at_soo_dot_com
2004-04-13 4:55 ` Ross Dickson
2004-04-13 17:22 ` Christian Kröner
2004-04-13 21:18 ` really bensoo_at_soo_dot_com
2004-04-14 4:24 ` really bensoo_at_soo_dot_com
2004-04-13 5:08 ` Len Brown
2004-04-13 7:03 ` Ross Dickson
2004-04-13 13:46 ` Maciej W. Rozycki
2004-04-14 1:02 ` IO-APIC on nforce2 [PATCH] Len Brown
2004-04-14 5:02 ` Ross Dickson
2004-04-14 6:30 ` Jamie Lokier
2004-04-14 10:37 ` Maciej W. Rozycki
2004-04-15 19:28 ` Len Brown
2004-04-14 19:57 ` Christian Kröner
2004-04-15 0:17 ` Len Brown
2004-04-15 1:48 ` Ross Dickson
2004-04-15 17:09 ` Christian Kröner
2004-04-15 15:10 ` IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Ross Dickson
2004-04-15 20:17 ` Len Brown
2004-04-15 21:04 ` Craig Bradney
2004-04-21 20:22 ` Len Brown
2004-04-21 20:33 ` Ian Kumlien
2004-04-21 20:45 ` Craig Bradney
2004-04-21 21:28 ` Prakash K. Cheemplavam
2004-04-21 22:41 ` Len Brown
2004-04-22 7:26 ` Prakash K. Cheemplavam
2004-04-22 14:58 ` Len Brown
2004-04-22 8:45 ` Craig Bradney
2004-04-22 15:03 ` Len Brown
2004-04-22 20:50 ` Craig Bradney
2004-04-22 8:50 ` Arjen Verweij
2004-04-22 16:39 ` Jesse Allen
2004-04-22 17:21 ` Len Brown
2004-04-22 21:29 ` Len Brown
2004-04-23 8:48 ` Prakash K. Cheemplavam
2004-04-23 9:01 ` Arjen Verweij
2004-04-23 9:08 ` Prakash K. Cheemplavam
2004-04-23 9:11 ` Prakash K. Cheemplavam
2004-04-23 12:18 ` Maciej W. Rozycki
2004-04-27 7:57 ` ACPI broken on nforce2? Prakash K. Cheemplavam
2004-04-26 11:41 ` IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Ross Dickson
2004-04-27 17:02 ` Arjen Verweij
2004-04-27 17:35 ` Ian Kumlien
2004-04-27 18:00 ` Len Brown
2004-04-27 18:24 ` Arjen Verweij
2004-04-27 18:51 ` Jussi Laako
2004-04-28 11:33 ` Ross Dickson
2004-04-28 20:59 ` Jesse Allen
2004-04-29 11:44 ` Ross Dickson
2004-04-29 11:54 ` Maciej W. Rozycki
2004-04-29 12:00 ` Jamie Lokier
2004-04-29 12:26 ` Maciej W. Rozycki
2004-04-29 11:57 ` Jamie Lokier
2004-04-29 12:16 ` Craig Bradney
2004-04-29 20:24 ` Jesse Allen [this message]
2004-04-29 20:31 ` Prakash K. Cheemplavam
2004-05-03 20:45 ` Jesse Allen
2004-05-17 15:26 ` Prakash K. Cheemplavam
2004-05-17 19:32 ` Craig Bradney
2004-05-17 19:37 ` Prakash K. Cheemplavam
2004-05-17 19:57 ` Craig Bradney
2004-04-27 21:31 ` Prakash K. Cheemplavam
2004-04-28 11:26 ` Prakash K. Cheemplavam
2004-05-01 6:51 ` Prakash K. Cheemplavam
2004-04-15 21:56 ` Arjen Verweij
2004-04-15 15:21 ` IO-APIC on nforce2 [PATCH] Zwane Mwaikambo
[not found] <1KkKQ-2v9-9@gated-at.bofh.it>
[not found] ` <1Kqdx-6E1-5@gated-at.bofh.it>
[not found] ` <1KH4I-3W9-11@gated-at.bofh.it>
[not found] ` <1LgOQ-7px-3@gated-at.bofh.it>
[not found] ` <1LlEY-36q-11@gated-at.bofh.it>
2004-04-15 23:07 ` IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Andi Kleen
2004-04-21 22:00 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 1:30 Jesse Allen
2004-05-07 4:47 ` Richard James
2004-05-07 7:13 ` Craig Bradney
2004-05-08 5:33 ` Richard James
2004-05-03 8:08 Allen Martin
2004-05-03 22:09 Allen Martin
2004-05-03 23:11 ` Bartlomiej Zolnierkiewicz
2004-05-04 8:28 ` Prakash K. Cheemplavam
2004-05-04 21:10 ` Jeff Garzik
2004-05-04 21:29 ` Bartlomiej Zolnierkiewicz
2004-05-05 12:14 ` Ross Dickson
2004-05-05 12:27 ` Ian Kumlien
2004-05-05 13:12 ` Ross Dickson
2004-05-05 13:23 ` Ian Kumlien
2004-05-05 12:58 ` Maciej W. Rozycki
2004-05-05 12:48 ` Patrick Dreker
2004-05-05 13:34 ` Patrick Dreker
2004-05-05 11:24 ` Ross Dickson
2004-05-05 12:18 ` Ian Kumlien
2004-05-05 12:52 ` Ross Dickson
2004-05-05 13:08 ` Ian Kumlien
2004-05-06 1:50 ` Jesse Allen
2004-05-04 20:38 Jesse Allen
2004-05-04 21:14 ` Craig Bradney
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=20040429202413.GA1982@tesore.local \
--to=the3dfxdude@hotmail.com \
--cc=AMartin@nvidia.com \
--cc=PrakashKC@gmx.de \
--cc=a.verweij@student.tudelft.nl \
--cc=cbradney@zip.com.au \
--cc=christian.kroener@tu-harburg.de \
--cc=dan@reactivated.net \
--cc=jamie@shareable.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=pomac@vapor.com \
--cc=ross@datscreative.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.