Andi Kleen <ak@suse.de> writes:In which case complaining is still correct (the BIOS was out of sync), enabling bit 17 is still correct and we are just in overkill mode. This has everything to do with how AMD coherent hypertransport works and little if anything to do with how the NV bridge operated. Basically the NV bridge seems to be sending a standard hypertransport x86 legacy interrupt packet (that doesn't have any target information) and when that packet hits the coherent hypertransport domain it isn't being converted into whatever would send it to all cpus. ..... The real practical problem is if somehow the BIOS goofs up this way and it then decides to ask us to boot on one of these cpus with an extended apic id. We will hang in calibrate_delay. So far this only seems to happen in the kdump case but in theory the BIOS could be completely crazy. Eric --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Ingo Molnar | Re: [RFT] x86 acpi: normalize segment descriptor register on resume |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Ingo Molnar | [bug] stuck localhost TCP connections, v2.6.26-rc3+ |
