From: YhLu <YhLu@tyan.com>
To: Andi Kleen <ak@suse.de>
Cc: Peter Buckingham <peter@pantasys.com>, linux-kernel@vger.kernel.org
Subject: RE: 2.6.12 with dual way dual core ck804 MB
Date: Fri, 24 Jun 2005 11:56:23 -0700 [thread overview]
Message-ID: <3174569B9743D511922F00A0C94314230AF97123@TYANWEB> (raw)
Andi,
Thanks for the patch, I tried that with my LinuxBIOS + 8way dual core.
It works well.
I'm using that with 2.6.12, because 2.6.11 has problem with nvidia
chipset....
~ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12
CPU13 CPU14 CPU15
0: 378977 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge timer
2: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 XT-PIC cascade
4: 1284 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge serial
8: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-edge rtc
20: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ehci_hcd:usb1
21: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level ohci_hcd:usb2
22: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
23: 0 0 0 0 0 0
0 0 0 0 0 0 0
0 0 0 IO-APIC-level libata
NMI: 781 661 48 51 51 51
51 51 51 51 53 52 53
53 53 53
LOC: 378822 378680 379254 379214 379172 379131
379088 379046 379004 378962 378921 378877 378834
378791 378748 378705
ERR: 55
and all int come to first cpu now.
the problem is the 2.6.12 timing problem with nvidia chipset is still there,
i hope that i have time to dubug it for your next week.
YH
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Wednesday, June 22, 2005 5:13 PM
> To: YhLu
> Cc: Andi Kleen; Peter Buckingham; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 with dual way dual core ck804 MB
>
> On Wed, Jun 22, 2005 at 05:07:44PM -0700, YhLu wrote:
> > actually with LinuxBIOS I can boot into 8 way dual core system.
> >
> > But it will randomly hang. acutally when using cat /proc/interrupts.
>
> Because it needs physical addressing, not logical like it is
> used right now.
> That it works at all is surprising.
>
> -Andi
>
next reply other threads:[~2005-06-24 18:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 18:56 YhLu [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 1:01 2.6.12 with dual way dual core ck804 MB YhLu
2005-06-24 23:47 YhLu
2005-06-29 2:40 ` Eric W. Biederman
2005-06-30 18:54 ` Andrew Vasquez
2005-06-30 20:54 ` Eric W. Biederman
2005-06-24 23:42 YhLu
2005-06-24 23:42 ` Andi Kleen
2005-06-23 0:07 YhLu
2005-06-23 0:12 ` Andi Kleen
2005-06-22 23:37 YhLu
2005-06-22 23:37 ` Andi Kleen
2005-06-21 22:50 YhLu
2005-06-21 23:55 ` Andi Kleen
2005-06-21 22:17 YhLu
2005-06-21 21:41 YhLu
2005-06-21 22:12 ` Andi Kleen
2005-06-22 22:26 ` Peter Buckingham
2005-06-22 23:10 ` Andi Kleen
2005-06-22 23:31 ` Peter Buckingham
2005-06-21 22:36 ` Andi Kleen
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=3174569B9743D511922F00A0C94314230AF97123@TYANWEB \
--to=yhlu@tyan.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@pantasys.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 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.