linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Miroslaw Mieszczak <mirek@mieszczak.com.pl>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, "Seth, Rohit" <rohit.seth@intel.com>,
	ajk <a@oo.ms>
Subject: Re: [2.6] Problem with PDC20265 on system with I865 chipset and PIV HT
Date: Fri, 13 Jan 2006 09:14:47 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601130910420.1579@montezuma.fsmlabs.com> (raw)
In-Reply-To: <20060113001618.66821fcb.akpm@osdl.org>

On Fri, 13 Jan 2006, Andrew Morton wrote:

> This decode from eip onwards should be reliable
> 
> Code;  c0110471 No symbols available
> 00000000 <_EIP>:
> Code;  c0110471 No symbols available   <=====
>    0:   c7 05 b0 d0 ff ff 00      movl   $0x0,0xffffd0b0   <=====
> Code;  c0110478 No symbols available
>    7:   00 00 00 
> Code;  c011047b No symbols available
>    a:   f0 0f b3 15 38 d6 57      lock btr %edx,0xc057d638
> Code;  c0110482 No symbols available
>   11:   c0 
> Code;  c0110483 No symbols available
>   12:   c3                        ret    
> Code;  c0110484 No symbols available
>   13:   83                        .byte 0x83
> Code;  c0110485 No symbols available
>   14:   78                        .byte 0x78
> 
> 
> That's oopsing when trying to write to the APIC:
> 
> 	apic_write_around(APIC_EOI, 0);
> 
> <cc's x86 people>
> 
> Is there any sane way in which APIC accesses can fault, or does this
> indicate bad hardware?

Without pagetable corruption no they shouldn't fault, interestingly this 
looks like;

http://bugzilla.kernel.org/show_bug.cgi?id=5565

Albeit with a pdc20262. Miroslaw, are there any other similarities in 
hardware with that bugzilla entry?

Thanks,
	Zwane


  reply	other threads:[~2006-01-13 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 22:39 [2.6] Problem with PDC20265 on system with I865 chipset and PIV HT Miroslaw Mieszczak
2006-01-13  8:16 ` Andrew Morton
2006-01-13 17:14   ` Zwane Mwaikambo [this message]
2006-01-15 19:18     ` Miroslaw Mieszczak
2006-01-14  6:48   ` Ingo Molnar

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=Pine.LNX.4.64.0601130910420.1579@montezuma.fsmlabs.com \
    --to=zwane@arm.linux.org.uk \
    --cc=a@oo.ms \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mirek@mieszczak.com.pl \
    --cc=rohit.seth@intel.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;
as well as URLs for NNTP newsgroup(s).