mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] i386: port ATI timer fix from x86_64 to i386
Date: Wed, 1 Mar 2006 13:59:55 +0000	[thread overview]
Message-ID: <200603011359.55569.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200602281619_MC3-1-B984-ED75@compuserve.com>

On Tuesday 28 February 2006 21:17, Chuck Ebbert wrote:
> Disable timer routing over 8254 when an ATI chipset is detected
> (autodetect is only implemented for ACPI, but these are new systems
> and should be using ACPI anyway.)  Adds boot options for manually
> disabling and enabling this feature. Also adds a note to the timer
> error message caused by this change explaining that this error
> is expected on ATI chipsets.
[snip]
>
>  	pin1  = find_isa_irq_pin(0, mp_INT);
>  	apic1 = find_isa_irq_apic(0, mp_INT);
> @@ -2294,7 +2311,7 @@ static inline void check_timer(void)
>  		}
>  		clear_IO_APIC_pin(apic1, pin1);
>  		printk(KERN_ERR "..MP-BIOS bug: 8254 timer not connected to "
> -				"IO-APIC\n");
> +				"IO-APIC (expected on ATI chipsets)\n");
>  	}
>

This hunk looks bogus. My understanding is that this is a BIOS bug that some 
vendors have started to correct. We shouldn't acknowledge vendor BIOS bugs as 
"expected", imo..

I had this message for years with my nForce2/nForce3 boards and eventually it 
was repaired.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  parent reply	other threads:[~2006-03-01 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 21:17 Chuck Ebbert
2006-02-28 23:21 ` Andrew Morton
2006-03-01 13:59 ` Alistair John Strachan [this message]
2006-03-01  0:03 Chuck Ebbert
2006-03-01  0:15 ` Andrew Morton
2006-03-01 10:40   ` Andi Kleen
2006-03-01 10:52     ` Andrew Morton
2006-03-01 11:07       ` Andi Kleen
2006-03-01  1:18 Parag Warudkar
2006-03-01  2:22 Chuck Ebbert
2006-03-01 15:50 Chuck Ebbert
2006-03-01 17:10 Chuck Ebbert

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=200603011359.55569.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®