Re: Resetting PCI-E devices after linux boot

2010-04-14 Thread Jake Magee 
Dan,

Were you able to get PCI-E hotplug working?  I could not get this working
myself and assumed that driver support was lacking.  I'm actually using a
PPC405.

Thanks,
Jake


On Thu, Mar 25, 2010 at 8:26 PM, Dan Wilson wrote:

> We are building a PCI-E device for use in an embedded system with an 85xx
> processor.  One of our customers is adamant that linux PCI-E hot-swap
> support will not allow us to either bring the device up after linux boot
> (i.e., the PCI-E device must be present when linux scans for PCI-E devices
> at startup) or to reset the device once linux is up.  It was our impression
> that the PCI-E hot-swap support should allow for devices to appear after
> linux boot, be properly initialized, and then later be able to shut them
> down and bring them back up again.
>
> Has anyone successfully used the PCI-E hot-swap capabilities in the linux
> kernel in a PPC 85xx environment?  Any known gotchas we need to be aware of?
>
> Thanks in advance for your responses,
>
> Dan.
>
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: BUG: Bad page map in process mm2

2010-03-08 Thread Jake Magee 
Steven,

Try these patches...
http://patchwork.ozlabs.org/patch/34047/
http://patchwork.ozlabs.org/patch/34113/

Both patches work for my situation, but I went with the second set as a
final patch(34113).


On Mon, Mar 8, 2010 at 3:32 PM, Steven A. Falco  wrote:

> Steven A. Falco wrote:
>
> Apologies - previous crash dump was mangled by the
> interspersed program output.  Here is one showing
> just the crash dump.
>
> Interestingly, the program does produce correct output,
> as verified by dd'ing from /dev/mem to a file, then
> doing "od" on the result.  So in some sense, the error
> is spurious.
>
>Steve
>
> # ./mm2 > foo 2>&1
> BUG: Bad page map in process mm2  pte:0452 pmd:0f6c8400
> page:c0396000 flags:0404 count:1 mapcount:-1 mapping:(null) index:0
> addr:4801f000 vm_flags:400844fb anon_vma:(null) mapping:cea78430 index:0
> vma->vm_ops->fault: 0x0
> vma->vm_file->f_op->mmap: mmap_mem+0x0/0xa4
> Call Trace:
> [cf4c5d90] [c0006cf4] show_stack+0x44/0x16c (unreliable)
> [cf4c5dd0] [c0067800] print_bad_pte+0x140/0x1cc
> [cf4c5e00] [c0068640] unmap_vmas+0x41c/0x594
> [cf4c5e80] [c006c8f0] exit_mmap+0xb8/0x150
> [cf4c5ea0] [c0020948] mmput+0x50/0xe0
> [cf4c5eb0] [c0024504] exit_mm+0xec/0x10c
> [cf4c5ee0] [c0025bd0] do_exit+0xc4/0x5d4
> [cf4c5f20] [c0026124] do_group_exit+0x44/0xa4
> [cf4c5f30] [c0026198] sys_exit_group+0x14/0x28
> [cf4c5f40] [c000edcc] ret_from_syscall+0x0/0x3c
> Disabling lock debugging due to kernel taint
> BUG: Bad page state in process mm2  pfn:0
> page:c0396000 flags:0404 count:0 mapcount:-1 mapping:(null) index:0
> Call Trace:
> [cf4c5d80] [c0006cf4] show_stack+0x44/0x16c (unreliable)
> [cf4c5dc0] [c00585bc] bad_page+0x94/0x12c
> [cf4c5de0] [c005d234] put_page+0x4c/0x170
> [cf4c5df0] [c0073e54] free_page_and_swap_cache+0x34/0x8c
> [cf4c5e00] [c0068490] unmap_vmas+0x26c/0x594
> [cf4c5e80] [c006c8f0] exit_mmap+0xb8/0x150
> [cf4c5ea0] [c0020948] mmput+0x50/0xe0
> [cf4c5eb0] [c0024504] exit_mm+0xec/0x10c
> [cf4c5ee0] [c0025bd0] do_exit+0xc4/0x5d4
> [cf4c5f20] [c0026124] do_group_exit+0x44/0xa4
> [cf4c5f30] [c0026198] sys_exit_group+0x14/0x28
> [cf4c5f40] [c000edcc] ret_from_syscall+0x0/0x3c
> # cat foo
> : 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378
> 0010: 7cfb3b78 480022ad 3c02 60001032
> 0020: 7c1b03a6 3c00c000 60002210 7c1a03a6
> 0030: 4c64 4800  
> # dd count=1 if=/dev/mem of=goo
> # od -X goo
> 000 7c7f1b787c9e23787cbd2b787cdc3378
> 020 7cfb3b78480022ad3c0260001032
> 040 7c1b03a63c00c000600022107c1a03a6
> 060 4c644800
> 100
>
>
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: BUG: Bad page map in process

2009-12-03 Thread Jake Magee 
Have you tried the following patches?  I'm not sure if they have made
it into the newer releases.
http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg37188.html

Also for reference... http://patchwork.ozlabs.org/patch/34047/


On Thu, Dec 3, 2009 at 1:18 PM, Sean MacLennan  wrote:
> With 2.6.32 I sometimes get lots and lots of "Bad page map" errors as
> shown below. I believe these started in 2.6.32-rc8 or possibly
> 2.6.32-rc7. Pika just switched to 2.6.31 so I have been concentrating
> on that release, and not really testing the 2.6.32 stream.
>
> I wish I could give more info, but I don't really even have the time to
> write this email :( I am hoping somebody will have a eureka moment.
>
> Cheers,
>   Sean
>
>
> [  147.410448] BUG: Bad page map in process udevd  pte: 
> pmd:cd883000
> [  147.417989] addr:48003000 vm_flags:08000875 anon_vma:(null) 
> mapping:cf4150ac index:3
> [  147.425837] vma->vm_ops->fault: filemap_fault+0x0/0x410
> [  147.431101] vma->vm_file->f_op->mmap: nfs_file_mmap+0x0/0x94
> [  147.436795] Call Trace:
> [  147.439268] [cf2dbd80] [c00065a4] show_stack+0x48/0x168 (unreliable)
> [  147.445708] [cf2dbdb0] [c0064ac8] print_bad_pte+0x14c/0x204
> [  147.451337] [cf2dbde0] [c0064cd4] vm_normal_page+0x90/0x98
> [  147.456875] [cf2dbdf0] [c0064ee8] unmap_vmas+0x20c/0x638
> [  147.462239] [cf2dbe80] [c0069194] exit_mmap+0xc8/0x170
> [  147.467441] [cf2dbea0] [c001caa4] mmput+0x50/0xf4
> [  147.472195] [cf2dbeb0] [c0020808] exit_mm+0x100/0x138
> [  147.477299] [cf2dbee0] [c00211b0] do_exit+0xb0/0x580
> [  147.482315] [cf2dbf20] [c00216c4] do_group_exit+0x44/0x9c
> [  147.487766] [cf2dbf30] [c0021730] sys_exit_group+0x14/0x28
> [  147.493308] [cf2dbf40] [c000dde4] ret_from_syscall+0x0/0x3c
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Page map BUG on program exit

2009-10-22 Thread Jake Magee 
Here ya go Jonathan,
http://patchwork.ozlabs.org/patch/34047/
http://patchwork.ozlabs.org/patch/34113/

Both patches work for my situation, but I went with the second set as a
final patch(34113).

- Jake Magee

On Thu, Oct 22, 2009 at 3:57 PM, Jonathan Haws wrote:

> All,
>
> I am using a 405EX CPU on a custom board.  The layout and hardware is very
> similar to the AMCC Kilauea board.  Here is the output of uname -a:
>
> Linux (none) 2.6.30.3-wolverine-dirty #3 PREEMPT Thu Sep 10 11:41:37 MDT
> 2009 ppc unknown
>
> I am getting the following BUG output when my program exits:
>
> BUG: Bad page map in process main  pte:980005d7 pmd:0d840400
> addr:4800 vm_flags:400844fb anon_vma:(null) mapping:cd8454f8
> index:98000
> vma->vm_file->f_op->mmap: fpga_mmap+0x0/0x178 [fpgaDriver]
> Call Trace:
> [cd84dc40] [c0006f0c] show_stack+0x44/0x16c (unreliable)
> [cd84dc80] [c00ba314] print_bad_pte+0x140/0x1d0
> [cd84dcb0] [c00ba3ec] vm_normal_page+0x48/0x50
> [cd84dcc0] [c00bb2ec] unmap_vmas+0x214/0x614
> [cd84dd40] [c00bffe0] exit_mmap+0xd0/0x1b4
> [cd84dd70] [c0031e40] mmput+0x50/0x134
> [cd84dd80] [c0036470] exit_mm+0x114/0x13c
> [cd84ddb0] [c0037d80] do_exit+0xc0/0x68c
> [cd84de00] [c0038390] do_group_exit+0x44/0xd8
> [cd84de10] [c0044468] get_signal_to_deliver+0x1f8/0x430
> [cd84de70] [c0008224] do_signal+0x54/0x29c
> [cd84df40] [c0010d5c] do_user_signal+0x74/0xc4
>
> I have an FPGA on the PCIe bus that I am mapping BAR0 to user space with a
> call to mmap().  The mapping works just fine and I can access all the
> registers in the BAR without a problem.  However, on exit this comes up.
>
> A Google search showed tons of people with similar problems in standard
> distributions (Ubuntu primarily), but no resolutions.
>
> Has anyone seen this crop up before and know what the issue is?  I include
> any source code, if that is required.
>
> Thanks!
>
> Jonathan
>
>
>
> ___
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

PPC405 RTC not working

2009-08-31 Thread Jake Magee 
I am currently trying to get a M41T65 sensor to work on a PPC405 based
board.  I am using the 2.6.26 kernel with a backported version of
rtc-m41t80.c (from 2.6.30).  Everything compiles and loads fine.  However,
there is no /dev/rtc node created.  "/proc/devices" returns "254 rtc" (which
I feel isn't correct).  And "/sys/bus/i2c/devices/" list nothing for the
RTC.  I do see the information from the device tree in
"/proc/device-tree/plb/opb/i...@ef600400/r...@68/"

Here is my dts information:
 IIC0: i...@ef600400 {
compatible = "ibm,iic-405exr", "ibm,iic";
reg = ;
interrupt-parent = <&UIC0>;
interrupts = <2 4>;
index = <0>;
r...@68 {
compatible = "m41t65";
    reg = <68>;
};
};

Thanks!
Jake Magee
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev