linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@coritel.it>
To: Jon Loeliger <jdl@freescale.com>
Cc: Timur Tabi <timur@freescale.com>,
	LinuxPPC-Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC8641D PCI-Express error
Date: Thu, 21 Feb 2008 16:37:50 +0100	[thread overview]
Message-ID: <47BD9ACE.1090003@coritel.it> (raw)
In-Reply-To: <47BD9815.9020002@freescale.com>

Jon Loeliger ha scritto:
> Timur Tabi wrote:
>> Marco Stornelli wrote:
>>
>>> No, it didn't. I have the same problem even with the 2.6.18 plus the
>>> 2.6.24 PCI-Express code. I performed this action because I can't change
>>> kernel version but I can modify it.
>>
>> Please try 2.6.24 (or even better, 2.6.25-rc2).  You may have done
>> something wrong in back-porting the code to 2.6.18.  There's no reason
>> why you can't at least try the latest version of the code for testing
>> purposes, even if you can't use it in production.
>>
> 
> Also, once you back-ported it and all the DTS changes, and all
> the fsl_soc.c changes needed and , and, and otherwise made it
> look _like_, 2.6.24 but still called it 2.6.18, after all that,
> can you remind us what was the error or failure mode that you saw?
> 
> jdl
> 
> 

When I try to read some register from my FPGA (virtex5) I have this bus
error:

Machine check in kernel mode.
Caused by (from SRR1=149030): Transfer error ack signal
Oops: Machine check, sig: 7 [#1]
PREEMPT SMP NR_CPUS=2
Modules linked in: virtex5
LTT NESTING LEVEL : 0
NIP: F108019C LR: F1080198 CTR: 00000001
REGS: c044dd60 TRAP: 0200   Not tainted      (2.6.18-mpc8641d_hpcn)
MSR: 00149030 <EE,ME,IR,DR>  CR: 22000222  XER: 00000000
TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0
GPR00: F1080198 C044DE10 C20E9990 0000002E 80000000 FFFFFFFF 00008000
00002EA3
GPR08: C20E9990 00000000 C04C0220 C044C000 22000222 1001956C 00000000
00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
GPR24: 3000EAA0 7FD6FDC0 00000000 C045FCC0 F107E594 F10A0000 00000000
C2036000
NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5]
LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5]
Call Trace:
[C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable)
[C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc
[C044DE50] [C0213754] driver_probe_device+0x60/0x118
[C044DE70] [C0213890] __driver_attach+0x84/0x88
[C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94
[C044DEC0] [C02135D4] driver_attach+0x24/0x34
[C044DED0] [C0212AC8] bus_add_driver+0x88/0x164
[C044DEF0] [C021397C] driver_register+0x70/0xb8
[C044DF00] [C01D284C] __pci_register_driver+0x64/0x98
[C044DF10] [F1080030] init_module+0x30/0x6c [virtex5]
[C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c
[C044DF40] [C0011358] ret_from_syscall+0x0/0x38
--- Exception: c00 at 0xff6de0c
    LR = 0x10000de4
Instruction dump:
40820060 3c60f108 3863cea0 48000311 807f0238 3c800001 48000395 7c7d1b78
3c60f108 3863ced4 480002f5 809d0000 <3c60f108> 3863cf04 480002e5 3c60f108

  reply	other threads:[~2008-02-21 15:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 16:13 MPC8641D PCI-Express error Marco Stornelli
2008-02-21  2:20 ` Kumar Gala
2008-02-21  8:02   ` Marco Stornelli
2008-02-21 15:21     ` Timur Tabi
2008-02-21 15:26       ` Jon Loeliger
2008-02-21 15:37         ` Marco Stornelli [this message]
2008-02-21 15:58           ` Jon Loeliger
2008-02-22 13:52             ` Marco Stornelli
  -- strict thread matches above, loose matches on Subject: below --
2008-02-29  8:50 Marco Stornelli
2008-02-19  9:06 Marco Stornelli
2008-02-19 14:19 ` Jon Loeliger
2008-02-19 15:42   ` Marco Stornelli
2008-02-19 16:06     ` Jon Loeliger
2008-02-19 16:43       ` Marco Stornelli
2008-02-19 16:59         ` Jon Loeliger
2008-02-19 20:19           ` Kumar Gala

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=47BD9ACE.1090003@coritel.it \
    --to=marco.stornelli@coritel.it \
    --cc=jdl@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=timur@freescale.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).