LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Oops at loading kernel module on AMCC Sequoia board. (https://www.linuxquestions.org/questions/linux-newbie-8/oops-at-loading-kernel-module-on-amcc-sequoia-board-711138/)

ynedel 03-12-2009 02:14 PM

Oops at loading kernel module on AMCC Sequoia board.
 
I am porting some special device driver from kernel 2.4.18 on PC platform to DENX kernel 2.4.27 on PowerPC platform (4xxFP) which is an AMCC development board "Sequoia".

When the driver is loaded and device is being initialized I get "Oops" as follows:
[SIZE="3"]Machine check in kernel mode.
Data Read PLB Error
Oops: Machine check, sig: 7 [#1]
PowerPC 44x Platform
Modules linked in: udm(P+)
NIP: d5113efc LR: d5113eec CTR: c0154f18
REGS: cfff7f10 TRAP: 0214 Tainted: P (2.6.28.7)
MSR: 00029000 <EE,ME> CR: 24008022 XER: 2000005f
TASK = cf916520[967] 'insmod' THREAD: cf978000
GPR00: d5113eec cf979cf0 cf916520 f0e82cc0 00001bea ffffffff c015509c 00000031
GPR08: 00000000 d5180000 00001bea 00001bea 24008022 00000000 00000000 100c5c70
GPR16: 100c0000 00000000 100c0000 d5110000 d5150000 d5150000 d5150000 00000000
GPR24: 000000fe d51496a0 d5120000 d511e14c d51496a0 00000001 00000190 d51496a0
NIP [d5113efc] udm_read32+0x70/0xa0 [udm]
LR [d5113eec] udm_read32+0x60/0xa0 [udm]
Call Trace:
[cf979cf0] [d5113eec] udm_read32+0x60/0xa0 [udm] (unreliable)
[cf979d00] [d5104c74] udm_chip_revision_match+0x1a0/0x2ac [udm]
[cf979d50] [d51148f4] udm_init+0x18c/0x3b4 [udm]
[cf979db0] [c0001414] do_one_initcall+0x34/0x198
[cf979f20] [c0048c60] sys_init_module+0xb0/0x1a8
[cf979f40] [c000d954] ret_from_syscall+0x0/0x3c
Instruction dump:
3c60d512 3c80d515 388494e8 38a0024f 7fe6fb78 7fc8f378 38639c64 480018c9
813f0010 7c69f214 7c0004ac 7c601c2c <0c030000> 4c00012c 80010014 bbc10008
---[ end trace e800dccb06ff08f5 ]---


I can see that this happens when driver tries to read the contents of the memory referred to by the BAR in the device's PCI header. This physical address of 0x80000000 has been remapped appropriately by calling ioremap(). It feels like this physical address is not accessible.
Does anybody know how to fix this?
Thanks.

unSpawn 03-14-2009 05:00 AM

Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread should be closed because it is a duplicate of http://www.linuxquestions.org/questi...board.-711152/.


All times are GMT -5. The time now is 03:35 AM.