Re: RTC rtc-cmos.c : Fix warning on PowerPC
From 8435e5876fc3d629406c63b85bff82c25fc4bf75 Mon Sep 17 00:00:00 2001 From: Srikanth Krishnakar skris...@mvista.com Date: Fri, 8 Oct 2010 18:07:06 +0530 Subject: [PATCH] RTC: rtc-cmos.c: Fix warning on PowerPC The following warning is seen while compilation of PowerPC kernel: CC drivers/rtc/rtc-cmos.o drivers/rtc/rtc-cmos.c:697:2: warning: #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes. Fix it by adding defined(__powerpc__). Signed-off-by: Srikanth Krishnakar skris...@mvista.com --- drivers/rtc/rtc-cmos.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c index 5856167..7e6ce62 100644 --- a/drivers/rtc/rtc-cmos.c +++ b/drivers/rtc/rtc-cmos.c @@ -687,7 +687,8 @@ cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq) #ifdefined(CONFIG_ATARI) address_space = 64; #elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) \ - || defined(__sparc__) || defined(__mips__) + || defined(__sparc__) || defined(__mips__) \ + || defined(__powerpc__) address_space = 128; #else #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes. -- 1.6.3.3.333.gdf68 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RTC rtc-cmos.c : Fix warning on PowerPC
Hello, I noticed a compilation warning of RTC for powerpc. Found the fix existing for MIPS not for available for PowerPC. -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** From 8435e5876fc3d629406c63b85bff82c25fc4bf75 Mon Sep 17 00:00:00 2001 From: Srikanth Krishnakar skris...@mvista.com Date: Fri, 8 Oct 2010 18:07:06 +0530 Subject: [PATCH] RTC: rtc-cmos.c: Fix warning on PowerPC The following warning is seen while compilation of PowerPC kernel: CC drivers/rtc/rtc-cmos.o drivers/rtc/rtc-cmos.c:697:2: warning: #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes. Fix it by adding defined(__powerpc__). Signed-off-by: Srikanth Krishnakar skris...@mvista.com --- drivers/rtc/rtc-cmos.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c index 5856167..7e6ce62 100644 --- a/drivers/rtc/rtc-cmos.c +++ b/drivers/rtc/rtc-cmos.c @@ -687,7 +687,8 @@ cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq) #if defined(CONFIG_ATARI) address_space = 64; #elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) \ - || defined(__sparc__) || defined(__mips__) + || defined(__sparc__) || defined(__mips__) \ + || defined(__powerpc__) address_space = 128; #else #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes. -- 1.6.3.3.333.gdf68 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Port Linux to ML510
If any changes w.r.t board then John Linn (XILINX) should be able to provide some pointers. 2010/6/11 kostas padarnitsas kpad...@hotmail.com Hi Srikant, Thanks for your help. I checked the driver versions and they seem ok. The problem is that when I download the linux image the program counter is not set to the address of boot sector of linux kernel, so linux doesn't boot. On the other hand with the ML507 everything works perfectly. Any idea?? Thanks in advance, Kostas -- Date: Thu, 10 Jun 2010 12:34:56 +0530 Subject: Re: Port Linux to ML510 From: skrishna...@gmail.com To: kpad...@hotmail.com CC: linuxppc-dev@lists.ozlabs.org Hi kostas, You need to verify that the driver version of serial and Ethernet (probably X-LLTEMAC) provided in the virtex440.dts matches version used in kernel. Look for compatible = version in the drivers. You can probably use EDK 11.2 as it is the latest from Xilinx. Have you generated your own DTS and Bitstream (download.bit) files ? If not then you should look for suitable download.bit for you kernel. -Srikant 2010/6/10 kostas padarnitsas kpad...@hotmail.com Hello, I am trying to port Linux to PowerPC on the ML510 Xilinx board. I am using EDK 10.1.3 to build the hardware and also device tree generator and the linux kernel from xilinx git. I followed the tutorial from http://xilinx.wikidot.com/powerpc-linux but I have no output. I have attached my .mhs file and the .dts. Any ideas what may cause this problem because I did the same thing with ML507 and it was working perfectly? Thanks in advance, Kostas -- Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now. https://signup.live.com/signup.aspx?id=60969 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** -- Hotmail: Free, trusted and rich email service. Get it now.https://signup.live.com/signup.aspx?id=60969 -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Port Linux to ML510
Hi kostas, You need to verify that the driver version of serial and Ethernet (probably X-LLTEMAC) provided in the virtex440.dts matches version used in kernel. Look for compatible = version in the drivers. You can probably use EDK 11.2 as it is the latest from Xilinx. Have you generated your own DTS and Bitstream (download.bit) files ? If not then you should look for suitable download.bit for you kernel. -Srikant 2010/6/10 kostas padarnitsas kpad...@hotmail.com Hello, I am trying to port Linux to PowerPC on the ML510 Xilinx board. I am using EDK 10.1.3 to build the hardware and also device tree generator and the linux kernel from xilinx git. I followed the tutorial from http://xilinx.wikidot.com/powerpc-linux but I have no output. I have attached my .mhs file and the .dts. Any ideas what may cause this problem because I did the same thing with ML507 and it was working perfectly? Thanks in advance, Kostas -- Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now. https://signup.live.com/signup.aspx?id=60969 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: PowerPC kernel linux-2.6.29.6 PANIC's at include/linux/cred.h for ipsec enabled kernel
Hi all, Target : PowerPC440 Kernel : Linux-2.6.29.6 The issue still remains in kernel linux-2.6.29.6 enabling following options in kernel, the kernel panics and won't boot anymore The following kernel options enabled : # Networking support CONFIG_NET=y CONFIG_INET=y CONFIG_NET_KEY=y CONFIG_XFRM_USER=y CONFIG_INET_AH=y CONFIG_INET_ESP=y CONFIG_INET_IPCOMP=y CONFIG_INET_TUNNEL=y # IPV6 CONFIG_IPV6=y CONFIG_IPV6_TUNNEL=y CONFIG_INET6_AH=y CONFIG_INET6_ESP=y CONFIG_INET6_IPCOMP=y CONFIG_INET6_TUNNEL=y # Cryptographic API CONFIG_CRYPTO=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_NULL=y CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_DEFLATE=y and while bootup I am seeing the panic/crash message as : Looking up port of RPC 15/1 on 10.50.21.151 VFS: Mounted root (nfs filesystem) on device 0:13. Freeing unused kernel memory: 184k init INIT: version 2.86 booting Starting udevudevd version 124 started Remounting root file system... [ cut here ] kernel BUG at include/linux/cred.h:206! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT LTT NESTING LEVEL : 0 Xilinx PPC440 Modules linked in: NIP: c00a8414 LR: c0067804 CTR: c00a83ec REGS: ce977da0 TRAP: 0700 Not tainted (2.6.29.6-ipsec) MSR: 00029000 EE,ME,CE CR: 24028448 XER: 0005 TASK = cf9a9430[472] 'mount.sh' THREAD: ce976000 GPR00: ce977e50 cf9a9430 cf9e00c0 cf3c7ee0 fffeb038 0003 c04f2224 GPR08: 00bf 0001 cf8070e0 c05255e8 44022444 100db7bc 4802e5a4 bf9f09c8 GPR16: c0456670 c0511188 c05111a8 c0525624 0001 c0522ca0 ce976034 GPR24: c0511328 ce976034 ce976000 c05255e8 0003 cf3c7160 c00a83ec cf99aaa0 NIP [c00a8414] file_free_rcu+0x28/0x6c LR [c0067804] __rcu_process_callbacks+0x1e4/0x400 Call Trace: [ce977e50] [c00a8444] file_free_rcu+0x58/0x6c (unreliable) [ce977e60] [c0067804] __rcu_process_callbacks+0x1e4/0x400 [ce977e90] [c0067a4c] rcu_process_callbacks+0x2c/0x4c [ce977eb0] [c0038cb0] __do_softirq+0xfc/0x1e0 [ce977f00] [c0004124] do_softirq+0x5c/0x60 [ce977f10] [c0038b18] irq_exit+0x98/0xc4 [ce977f20] [c000b2b4] timer_interrupt+0x104/0x1cc [ce977f40] [c000e7d8] ret_from_except+0x0/0x18 Instruction dump: 4832cfa9 4bd8 9421fff0 7c0802a6 93e1000c 7c7f1b78 90010014 8063003c 8123 3809 7d290378 55290ffe 0f09 7c001828 3000 7c00192d Kernel panic - not syncing: Fatal exception in interrupt Rebooting in 180 seconds.. Any suggestions or the filed bug report anywhere ?? -Srikant On Tue, Aug 11, 2009 at 12:05 PM, srikanth krishnakar skrishna...@gmail.com wrote: Hi All, Target : PowerPC (ppc440) While testing kernel linux-2.6.29.6 with IPSEC enabled I observed frequent panic messages as shown below while bootup: VFS: Mounted root (nfs filesystem) on device 0:13. Freeing unused kernel memory: 184k init INIT: version 2.86 booting Starting udevudevd version 124 started Remounting root file system... logger: mount: mount point /proc/bus/usb does not exist FAT: invalid media value (0x01) VFS: Can't find a valid FAT filesystem on dev xsa. [ cut here ] kernel BUG at include/linux/cred.h:206! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT LTT NESTING LEVEL : 0 Xilinx Virtex440 Modules linked in: nls_iso8859_1 NIP: c0031800 LR: c0031864 CTR: c0033e2c REGS: c0515d00 TRAP: 0700 Not tainted (2.6.29.6.xilinx-ml507.0908071454-ipsec) MSR: 00029000 EE,ME,CE CR: 24028028 XER: 0005 TASK = c04e74c0[0] 'swapper' THREAD: c0514000 GPR00: c0515db0 c04e74c0 cf9e0120 c00539b4 0002 c04f2224 GPR08: 02fd 0001 02fc c05255e8 44022024 d6c4 dce9ee1f bfefe53f GPR16: c0456690 c0511188 c05111a8 c0525624 0001 c0522ca0 c0514034 GPR24: c0511328 c0514034 c0514000 c05255e8 000a cf3e7920 ce89e050 ce89e050 NIP [c0031800] __put_task_struct+0x8c/0xf4 LR [c0031864] __put_task_struct+0xf0/0xf4 Call Trace: [c0515db0] [c0031864] __put_task_struct+0xf0/0xf4 (unreliable) [c0515dc0] [c0033ecc] delayed_put_task_struct+0xa0/0xbc [c0515de0] [c0067804] __rcu_process_callbacks+0x1e4/0x400 [c0515e10] [c0067a4c] rcu_process_callbacks+0x2c/0x4c [c0515e30] [c0038cb0] __do_softirq+0xfc/0x1e0 [c0515e80] [c0004124] do_softirq+0x5c/0x60 [c0515e90] [c0038b18] irq_exit+0x98/0xc4 [c0515ea0] [c000b2b4] timer_interrupt+0x104/0x1cc [c0515ec0] [c000e7d8] ret_from_except+0x0/0x18 [c0515f80] [c0007294] cpu_idle+0x58/0xf4 [c0515fa0] [c03db4dc] __got2_end+0x80/0x94 [c0515fc0] [c04b6734] start_kernel+0x25c/0x2b0 [c0515ff0] [c218] skpinv+0x1a8/0x1e4 Instruction dump: 0f09 7c001828 3000 7c00192d 40a2fff4 2f80 419e0078 807f01a4 8123 3809 7d290378 55290ffe 0f09 7c001828 3000 7c00192d Kernel panic - not syncing: Fatal exception in interrupt Rebooting in 180 seconds.. Attachment: kernel config your early comments are appreciated ! Regards Srikanth Krishnakar ** -- The Good You Do, The Best
PowerPC kernel linux-2.6.29.6 PANIC's at include/linux/cred.h for ipsec enabled kernel
Hi All, Target : PowerPC (ppc440) While testing kernel linux-2.6.29.6 with IPSEC enabled I observed frequent panic messages as shown below while bootup: VFS: Mounted root (nfs filesystem) on device 0:13. Freeing unused kernel memory: 184k init INIT: version 2.86 booting Starting udevudevd version 124 started Remounting root file system... logger: mount: mount point /proc/bus/usb does not exist FAT: invalid media value (0x01) VFS: Can't find a valid FAT filesystem on dev xsa. [ cut here ] kernel BUG at include/linux/cred.h:206! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT LTT NESTING LEVEL : 0 Xilinx Virtex440 Modules linked in: nls_iso8859_1 NIP: c0031800 LR: c0031864 CTR: c0033e2c REGS: c0515d00 TRAP: 0700 Not tainted (2.6.29.6.xilinx-ml507.0908071454-ipsec) MSR: 00029000 EE,ME,CE CR: 24028028 XER: 0005 TASK = c04e74c0[0] 'swapper' THREAD: c0514000 GPR00: c0515db0 c04e74c0 cf9e0120 c00539b4 0002 c04f2224 GPR08: 02fd 0001 02fc c05255e8 44022024 d6c4 dce9ee1f bfefe53f GPR16: c0456690 c0511188 c05111a8 c0525624 0001 c0522ca0 c0514034 GPR24: c0511328 c0514034 c0514000 c05255e8 000a cf3e7920 ce89e050 ce89e050 NIP [c0031800] __put_task_struct+0x8c/0xf4 LR [c0031864] __put_task_struct+0xf0/0xf4 Call Trace: [c0515db0] [c0031864] __put_task_struct+0xf0/0xf4 (unreliable) [c0515dc0] [c0033ecc] delayed_put_task_struct+0xa0/0xbc [c0515de0] [c0067804] __rcu_process_callbacks+0x1e4/0x400 [c0515e10] [c0067a4c] rcu_process_callbacks+0x2c/0x4c [c0515e30] [c0038cb0] __do_softirq+0xfc/0x1e0 [c0515e80] [c0004124] do_softirq+0x5c/0x60 [c0515e90] [c0038b18] irq_exit+0x98/0xc4 [c0515ea0] [c000b2b4] timer_interrupt+0x104/0x1cc [c0515ec0] [c000e7d8] ret_from_except+0x0/0x18 [c0515f80] [c0007294] cpu_idle+0x58/0xf4 [c0515fa0] [c03db4dc] __got2_end+0x80/0x94 [c0515fc0] [c04b6734] start_kernel+0x25c/0x2b0 [c0515ff0] [c218] skpinv+0x1a8/0x1e4 Instruction dump: 0f09 7c001828 3000 7c00192d 40a2fff4 2f80 419e0078 807f01a4 8123 3809 7d290378 55290ffe 0f09 7c001828 3000 7c00192d Kernel panic - not syncing: Fatal exception in interrupt Rebooting in 180 seconds.. Attachment: kernel config your early comments are appreciated ! Regards Srikanth Krishnakar ** # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29.6 # Mon Aug 3 20:22:33 2009 # # CONFIG_PPC64 is not set # # Processor support # # CONFIG_6xx is not set # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set CONFIG_44x=y # CONFIG_E200 is not set CONFIG_PPC_FPU=y CONFIG_4xx=y CONFIG_BOOKE=y CONFIG_PTE_64BIT=y CONFIG_PHYS_64BIT=y CONFIG_PPC_MMU_NOHASH=y # CONFIG_PPC_MM_SLICES is not set CONFIG_NOT_COHERENT_CACHE=y CONFIG_PPC32=y CONFIG_WORD_SIZE=32 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_IRQ_PER_CPU=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y # CONFIG_ARCH_NO_VIRT_TO_BUS is not set CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_DEFAULT_UIMAGE is not set CONFIG_PPC_DCR_NATIVE=y CONFIG_PPC_DCR_MMIO=y CONFIG_PPC_DCR=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION=-ipsec # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=14 # CONFIG_HAVE_GET_CYCLES is not set CONFIG_HAVE_TRACE_CLOCK=y # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set # CONFIG_HAVE_UNSYNCHRONIZED_TSC is not set # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y CONFIG_RELAY=y CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_IPC_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_NET_NS is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED
PowerPC kernel linux-2.6.29.6 crashes at mm/slab.c for ipsec application
[ce837dd0] [c050e60c] 0xc050e60c [ce837e30] [c00a1d3c] kmem_cache_alloc+0x80/0xa0 [ce837e50] [c00534ec] prepare_creds+0x3c/0xcc [ce837e70] [c005382c] copy_creds+0xa0/0x12c [ce837e80] [c00307dc] copy_process+0x1c0/0xe20 [ce837ee0] [c00314b8] do_fork+0x7c/0x338 [ce837f20] [c00065b4] sys_clone+0x58/0x88 [ce837f40] [c000e164] ret_from_syscall+0x0/0x3c Instruction dump: 41a20008 4839c591 80010014 83e1000c 38210010 7c0803a6 4e800020 3d20c052 39292ca0 800900c0 7c34 5400d97e 0f00 2f80 41beff88 3801 BUG: scheduling while atomic: sshd/970/0x1002 Modules linked in: nls_iso8859_1 nfsd Call Trace: [ce837ac0] [c0006184] show_stack+0x40/0x15c (unreliable) [ce837af0] [c002bab4] __schedule_bug+0x68/0x6c [ce837b00] [c03d5138] schedule+0x2bc/0x36c [ce837b50] [c002bae0] __cond_resched+0x28/0x54 [ce837b60] [c03d5304] _cond_resched+0x50/0x58 [ce837b70] [c0034368] put_files_struct+0xe4/0xfc [ce837b90] [c0035e28] do_exit+0x144/0x6b8 [ce837be0] [c000c234] die+0x1b0/0x1b8 [ce837c10] [c000c554] _exception+0x1d4/0x2b4 [ce837d10] [c000e78c] ret_from_except_full+0x0/0x4c [ce837dd0] [c050e60c] 0xc050e60c [ce837e30] [c00a1d3c] kmem_cache_alloc+0x80/0xa0 [ce837e50] [c00534ec] prepare_creds+0x3c/0xcc [ce837e70] [c005382c] copy_creds+0xa0/0x12c [ce837e80] [c00307dc] copy_process+0x1c0/0xe20 [ce837ee0] [c00314b8] do_fork+0x7c/0x338 [ce837f20] [c00065b4] sys_clone+0x58/0x88 [ce837f40] [c000e164] ret_from_syscall+0x0/0x3c r...@inson:~# Any Clue or any bugs found in mm/slab.c for linux-2.6.29.6 while running IPSEC applications ? Thanks in Advance ! Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: PowerPC kernel linux-2.6.29.6 crashes at mm/slab.c for ipsec application
Yes, You are right. CONFIG_PREEMPT is enabled in the kernel config. Attached is the config. Thanks -Srikanth On Thu, Aug 6, 2009 at 7:56 PM, Josh Boyer jwbo...@linux.vnet.ibm.comwrote: On Thu, Aug 06, 2009 at 06:46:26PM +0530, srikanth krishnakar wrote: Hi all, Here is kernel bug for linux-2.6.29.6 for PowerPC (ppc440) target, while running ipsec application it is observed that kernel oops'es oftenly as show below : r...@powerpc:~# ./ipsec [ cut here ] kernel BUG at mm/slab.c:3002! Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT LTT NESTING LEVEL : 0 LTT? Any Clue or any bugs found in mm/slab.c for linux-2.6.29.6 while running IPSEC applications ? Do you have CONFIG_PREEMPT set? The oops output seems to think so. Also, seeing the LTT makes me wonder if you have added custom patches to your kernel? Do you have a simple testcase that could be run to recreate this? If so, could you provide it somewhere and perhaps your .config? josh -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29.6 # Mon Aug 3 20:22:33 2009 # # CONFIG_PPC64 is not set # # Processor support # # CONFIG_6xx is not set # CONFIG_PPC_85xx is not set # CONFIG_PPC_8xx is not set # CONFIG_40x is not set CONFIG_44x=y # CONFIG_E200 is not set CONFIG_PPC_FPU=y CONFIG_4xx=y CONFIG_BOOKE=y CONFIG_PTE_64BIT=y CONFIG_PHYS_64BIT=y CONFIG_PPC_MMU_NOHASH=y # CONFIG_PPC_MM_SLICES is not set CONFIG_NOT_COHERENT_CACHE=y CONFIG_PPC32=y CONFIG_WORD_SIZE=32 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_IRQ_PER_CPU=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_ILOG2_U32=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y # CONFIG_ARCH_NO_VIRT_TO_BUS is not set CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_OF=y CONFIG_PPC_UDBG_16550=y # CONFIG_GENERIC_TBSYNC is not set CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_DEFAULT_UIMAGE is not set CONFIG_PPC_DCR_NATIVE=y CONFIG_PPC_DCR_MMIO=y CONFIG_PPC_DCR=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION=-ipsec # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=14 # CONFIG_HAVE_GET_CYCLES is not set CONFIG_HAVE_TRACE_CLOCK=y # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set # CONFIG_HAVE_UNSYNCHRONIZED_TSC is not set # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y CONFIG_RELAY=y CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_IPC_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_NET_NS is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_COMPAT_BRK=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_MARKERS=y CONFIG_OPROFILE=m CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_KRETPROBES=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_LTT=y CONFIG_LTT_FILTER=m # CONFIG_HAVE_LTT_DUMP_TABLES is not set CONFIG_LTT_RELAY_ALLOC=y CONFIG_LTT_RELAY_LOCKLESS=y # CONFIG_LTT_RELAY_IRQOFF is not set # CONFIG_LTT_RELAY_LOCKED is not set CONFIG_LTT_SERIALIZE=m CONFIG_LTT_FAST_SERIALIZE=y CONFIG_LTT_TRACEPROBES=m CONFIG_LTT_TRACE_CONTROL=m CONFIG_LTT_TRACER=y CONFIG_LTT_ALIGNMENT=y CONFIG_LTT_CHECK_ARCH_EFFICIENT_UNALIGNED_ACCESS=y # CONFIG_LTT_DEBUG_EVENT_SIZE is not set CONFIG_LTT_USERSPACE_EVENT=m CONFIG_LTT_VMCORE=y CONFIG_LTT_KPROBES=y
Re: [LTP] msgctl10 fails on Powerpc Linux-2.6.29.6
On Thu, Jul 23, 2009 at 6:33 AM, Kumar Gala ga...@kernel.crashing.orgwrote:
On Jul 22, 2009, at 11:32 AM, srikanth krishnakar wrote:
On Wed, Jul 22, 2009 at 9:14 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
On Jul 22, 2009, at 10:38 AM, srikanth krishnakar wrote:
On Wed, Jul 22, 2009 at 8:52 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
I'm not seeing any BUG* in traps.c @ line 904.
On Jul 21, 2009, at 4:33 AM, srikanth krishnakar wrote:
The LTP test case msgctl10.c fails on linux-2.6.29.6 for PowerPC
architecture (ppc440)
msgctl101 B[ cut here ]
kernel BUG at arch/powerpc/kernel/traps.c:904!
Oops: Exception in kernel mode, sig: 5 [#9]
I'm not seeing any BUG* in traps.c @ line 904. Do you have some other
patches on top of 2.6.29.6?
- k
I have LTTng patches on top of linux-2.6.29.6.
Does it modify traps.c? Can you see what the code around line 904 looks
like and post that.
- k
896
897 #if defined(CONFIG_XILINX_VIRTEX_5_FXT) defined(CONFIG_PPC_FPU)
898 if (reason REASON_ILLEGAL) {
899 if (excep_state 1) {
900 excep_state++;
901 return;
902 }
903 /* should never get here */
904 BUG();
905 }
906 #endif
907
908 /* Try to emulate it if we should. */
Are you sure this is coming from the LTTng patches? Which actual patch
makes this change?
- k
Thanks kumar,
I've got the patch out which fixes the issues. But now.. seems there is some
generic issue in PPC440 targets, I am observing that
*remap_file_pages01* and *remap_file_pages02 *test cases from LTP are
failing since *Linux-2.6.24* kernel to *Linux-2.6.30*. If you can give some
pointers that would be greatly appreciated ! Or if you have results for this
on any PPC44x would be helpful.
Arch : PowerPC
Target : Xilinx PowerPC440 virtex5
I've tried to test the cause for this but found that kernel throws error
message of segmentation fault.
Thanks in Advance.
-Srikant
--
The Good You Do, The Best You GET
Regards
Srikanth Krishnakar
**
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [LTP] msgctl10 fails on Powerpc Linux-2.6.29.6
On Wed, Jul 22, 2009 at 8:52 PM, Kumar Gala ga...@kernel.crashing.orgwrote: I'm not seeing any BUG* in traps.c @ line 904. On Jul 21, 2009, at 4:33 AM, srikanth krishnakar wrote: The LTP test case msgctl10.c fails on linux-2.6.29.6 for PowerPC architecture (ppc440) msgctl101 B[ cut here ] kernel BUG at arch/powerpc/kernel/traps.c:904! Oops: Exception in kernel mode, sig: 5 [#9] I'm not seeing any BUG* in traps.c @ line 904. Do you have some other patches on top of 2.6.29.6? - k I have LTTng patches on top of linux-2.6.29.6. -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [LTP] msgctl10 fails on Powerpc Linux-2.6.29.6
On Wed, Jul 22, 2009 at 9:14 PM, Kumar Gala ga...@kernel.crashing.orgwrote:
On Jul 22, 2009, at 10:38 AM, srikanth krishnakar wrote:
On Wed, Jul 22, 2009 at 8:52 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
I'm not seeing any BUG* in traps.c @ line 904.
On Jul 21, 2009, at 4:33 AM, srikanth krishnakar wrote:
The LTP test case msgctl10.c fails on linux-2.6.29.6 for PowerPC
architecture (ppc440)
msgctl101 B[ cut here ]
kernel BUG at arch/powerpc/kernel/traps.c:904!
Oops: Exception in kernel mode, sig: 5 [#9]
I'm not seeing any BUG* in traps.c @ line 904. Do you have some other
patches on top of 2.6.29.6?
- k
I have LTTng patches on top of linux-2.6.29.6.
Does it modify traps.c? Can you see what the code around line 904 looks
like and post that.
- k
896
897 #if defined(CONFIG_XILINX_VIRTEX_5_FXT) defined(CONFIG_PPC_FPU)
898 if (reason REASON_ILLEGAL) {
899 if (excep_state 1) {
900 excep_state++;
901 return;
902 }
903 /* should never get here */
904 BUG();
905 }
906 #endif
907
908 /* Try to emulate it if we should. */
--
The Good You Do, The Best You GET
Regards
Srikanth Krishnakar
**
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
msgctl10 fails on Powerpc Linux-2.6.29.6
The LTP test case *msgctl10.c* fails on linux-2.6.29.6 for PowerPC architecture (ppc440) msgctl101 B[ cut here ] kernel BUG at arch/powerpc/kernel/traps.c:904! Oops: Exception in kernel mode, sig: 5 [#9] PREEMPT LTT NESTING LEVEL : 0 Virtex440 Modules linked in: NIP: c038178c LR: c0381640 CTR: c02650bc REGS: cafbbe70 TRAP: 0700 Tainted: G D (2.6.29.6) MSR: 00029000 EE,ME,CE CR: 48004224 XER: 2008 TASK = cafa17f0[6435] 'msgctl10' THREAD: cafba000 GPR00: 0001 cafbbf20 cafa17f0 ffda 0800 0001 0037 GPR08: cafa17f0 c04a 00021002 c0381594 28004222 1001f4bc bf93d950 100b GPR16: 0007 bf93d95c 100012a0 10005b84 0067 100174e8 10017500 100174f8 GPR24: 0001 103eaa50 0800 cafbbf50 NIP [c038178c] program_check_exception+0x1f8/0x5f4 LR [c0381640] program_check_exception+0xac/0x5f4 Call Trace: [cafbbf20] [c0381640] program_check_exception+0xac/0x5f4 (unreliable) [cafbbf40] [c000e78c] ret_from_except_full+0x0/0x4c Instruction dump: 7d808120 4bc8ac20 2f830001 41beff38 2f83fff2 419e0024 77c00804 4182004c 3d20c04a 8809207c 2f80 419e0080 0fe0 4800 80010024 3ca3 ---[ end trace fd0893c7d8cee1bd ]--- ROK : Unexpected signal 11 received. msgctl101 FAIL : in read # = 21245,key = 533a msgctl100 WARN : Verify error in child 13, *buf = f1, val = 6d, size = 3 msgctl101 BROK : Unexpected signal 11 received. msgctl101 BROK : Msgsnd error in child 14, key = d344 errno = 43 msgctl100 WARN : tst_rmdir(): rmobj(/tmp/msgNjyTEb) failed: lstat(/tmp/msgNjyTEb) failed; errno=2: No such file or directory msgctl100 WARN : tst_rmdir(): rmobj(/tmp/msgNjyTEb) failed: lstat(/tmp/msgNjyTEb) failed; errno=2: No such file or directory msgctl101 FAIL : in read # = 54260,key = d46d msgctl101 B[ cut here ] Any clue ? Thanks in Advance ! -- Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Soft Reset for PPC44x Virtex 5 hangs saying Restarting System
Hi all, Kernel : Linux-2.6.29 Arch: Powerpc (ppc44x) Target: Xilinx ML507 Virtex5 I have an issue in Reset System of Xilinx ML507 target board. I am using Compact Flash to boot the target ( using system ACE file to boot the target), during the process reset or reboot command on the target, I am not able to reboot the target completely, here is the snapshot: --- r...@ml507:~# reboot INIT: Sending processes the TERM signalWed Jul INIT: Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 1052) . Stopping Vixie-cron. Stopping network benchmark server: netserverstopped /usr/sbin/netserver (pid 1058) . Stopping syslogd/klogd: stopped syslogd (pid 1061) stopped klogd (pid 1063) done NOT deconfiguring network interfaces: / is an NFS mount Sending all processes the TERM signal... Sending all processes the KILL signal... hwclock: can't open '/dev/misc/rtc': No such file or directory Unmounting remote filesystems... Deactivating swap... /etc/rc6.d/S40umountfs: line 9: swapoff: not found Unmounting local filesystems... umount2: Device or resource busy umount: none busy - remounted read-only Rebooting... Restarting system. --- Target hangs here.. - The target again doesn't provide me the boot options as obtained when done hard reset : Welcome to the Xilinx Virtex-5 ML507 Evaluation Platform Bootloader Menu! Please choose a demo by typing in the number of the demo you want to use Or select a demo using the directional buttons (C,W,S,E,N) (Then press the center (C) button to start the selected demo) 1. Virtex-5 Slide Show 2. Web Server Demo 3. Simon Game 4. Board Diagnostics (XROM) 5. USB Demo 6. My own ACE file 7. Ring Tone Player Rebooting to System ACE Configuration Address 6... zImage starting: loaded at 0x0080 (sp: 0x00a44fb0) Allocating 0x4e9138 bytes for kernel ... gunzipping (0x - 0x0080e000:0x00a437cc)...done 0x4a1bcc bytes Any comments or suggestions are appreciated !! Thanks -Sriknt ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Soft Reset for PPC44x Virtex 5 hangs saying Restarting System
On Mon, Jul 13, 2009 at 8:32 PM, Grant Likely grant.lik...@secretlab.cawrote:
On Mon, Jul 13, 2009 at 1:16 AM, srikanth
krishnakarskrishna...@gmail.com wrote:
Hi all,
Kernel : Linux-2.6.29
Arch: Powerpc (ppc44x)
Target: Xilinx ML507 Virtex5
I have an issue in Reset System of Xilinx ML507 target board. I am
using
Compact Flash to boot the target ( using system ACE file to boot the
target), during the process reset or reboot command on the target, I am
not
able to reboot the target completely, here is the snapshot:
Where is your boot code located? In BRAM? or SDRAM?
It is located in BRAM.
If it is in
RAM, then it is likely that your boot code gets overwritten when the
Linux kernel boots and so soft resetting the processor will result in
a hung system (because it doesn't have any boot code to run).
-
The target again doesn't provide me the boot options as obtained when
done
hard reset :
What boot options are you referring to?
Boot options: console=ttyS0,9600 ip=bootp root=/dev/nfs rw
SystemACE boot configuration?
Yes. I have created SystemACE file using XMD to boot the target, I place
system.ace file in compact flash with rootfs NFS,
I see current ppc4xx_reset_system has been set to : DBCR_RST_SYSTEM so that
is system reset but leaves the FPGA still programmed, I tried writing
DBCR_RST_CORE to DBCR0 that leads to segmentation fault as ;
void ppc4xx_reset_system(char *cmd)
{
mtspr(SPRN_DBCR0, mfspr(SPRN_DBCR0) | DBCR0_RST_SYSTEM); Tried
using DBCR0_RST_CORE
while (1)
; /* Just in case the reset doesn't work */
}
--
r...@xilinx-ml507:~# reboot
INIT: Sending processes the TERM signal
INIT: Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid
105)
.
Stopping Vixie-cron.
Stopping network benchmark server: netserverstopped /usr/sbin/netserver (pid
10)
.
Stopping syslogd/klogd: stopped syslogd (pid 1060)
stopped klogd (pid 1062)
done
NOT deconfiguring network interfaces: / is an NFS mount
Sending all processes the TERM signal...
Sending all processes the KILL signal...
hwclock: can't open '/dev/misc/rtc': No such file or directory
Unmounting remote filesystems...
Deactivating swap...
/etc/rc6.d/S40umountfs: line 9: swapoff: not found
Unmounting local filesystems...
umount2: Device or resource busy
umount: none busy - remounted read-only
Rebooting... Restarting system.
Oops: Exception in kernel mode, sig: 11 [#1]
PREEMPT LTT NESTING LEVEL : 0
Xilinx Virtex440
Modules linked in: nls_iso8859_1 ipv6
NIP: fffc LR: c000d14c CTR: c0018b64
REGS: cf373d50 TRAP: 0700 Not tainted (2.6.29.6)
MSR: CR: 2228 XER: 2001
TASK = cf9acbf0[1101] 'reboot' THREAD: cf372000
GPR00: 5000 cf373e00 cf9acbf0 18ef c026493c
4000
GPR08: c04a5c8c c04a 3fff 18ef 2222 1001a5a0 8000
GPR16: 1000 0004 0001
0001
GPR24: 0123 0001 01234567 28121969
NIP [fffc] 0xfffc
LR [c000d14c] machine_restart+0x34/0x48
Call Trace:
[cf373e00] [c000d130] machine_restart+0x18/0x48 (unreliable)
[cf373e10] [c0046530] kernel_restart+0x34/0x5c
[cf373e20] [c0046684] sys_reboot+0x124/0x1a4
[cf373f40] [c000e164] ret_from_syscall+0x0/0x3c
Instruction dump:
---[ end trace 51d087d0d6d3d0e5 ]---
Segmentation fault
--
How can I reboot the system, while resetting the FPGA core completely ?
The current system ace driver doesn't have any support for either
setting the boot options or using the systemace to reboot the system
by reconfiguring the FPGA. It shouldn't be hard to do, it just hasn't
been written.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Thanks for you patience !
-Srikanth
--
The Good You Do, The Best You GET
Regards
Srikanth Krishnakar
**
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Soft Reset for PPC44x Virtex 5 hangs saying Restarting System
On Mon, Jul 13, 2009 at 9:31 PM, Grant Likely grant.lik...@secretlab.cawrote: On Mon, Jul 13, 2009 at 9:39 AM, srikanth krishnakarskrishna...@gmail.com wrote: On Mon, Jul 13, 2009 at 8:32 PM, Grant Likely grant.lik...@secretlab.ca wrote: On Mon, Jul 13, 2009 at 1:16 AM, srikanth krishnakarskrishna...@gmail.com wrote: Hi all, Kernel : Linux-2.6.29 Arch: Powerpc (ppc44x) Target: Xilinx ML507 Virtex5 I have an issue in Reset System of Xilinx ML507 target board. I am using Compact Flash to boot the target ( using system ACE file to boot the target), during the process reset or reboot command on the target, I am not able to reboot the target completely, here is the snapshot: Where is your boot code located? In BRAM? or SDRAM? It is located in BRAM. Then most likely the process of booting modifies the initial data in BRAM such that it will not be able to reboot the system. How can I reboot the system, while resetting the FPGA core completely ? To reset and reconfigure the FPGA, you need to modify the systemace driver to provide a system reset routine. See the systemace user manual for details on how to do this. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. Thank You very much. Will look into it. Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Info threads hangs in Linux-2.6.29 with KGDBOE
Hi All, *ISSUE *: *Info threads* hangs in KGDBOE Kernel : Linux-2.6.29 Bug found in Architectures: PowerPC (ppc32), x86 --- While trying to run kernel* Linux-2.6.29* on* PowerPC* Xilinx target with *KGDBOE *enabled. Further issues arise when I run *info threads* after connecting to the target. following is the error: (gdb) target remote udp:10.161.2.35:6443 warning: The remote protocol may be unreliable over UDP. Some events may be lost, rendering further debugging impossible. Remote debugging using udp:10.161.2.35:6443 kgdb_breakpoint () at kernel/kgdb.c:1803 1803arch_kgdb_breakpoint(); (gdb) info threads [New Thread -2] [New Thread 2] [New Thread 3] [New Thread 4] [New Thread 5] [New Thread 6] [New Thread 59] [New Thread 67] [New Thread 101] [New Thread 102] [New Thread 103] [New Thread 104] [New Thread 105] 14 Thread 105 (nfsiod) __switch_to (prev=value optimized out, new=0xcf89c100) at arch/powerpc/kernel/process.c:411 13 Thread 104 (aio/0) __switch_to (prev=value optimized out, new=0xcf82f4e0) at arch/powerpc/kernel/process.c:411 12 Thread 103 (kswapd0) __switch_to (prev=value optimized out, new=0xcf82f4e0) at arch/powerpc/kernel/process.c:411 11 Thread 102 (pdflush) __switch_to (prev=value optimized out, new=0xcf82e880) at arch/powerpc/kernel/process.c:411 10 Thread 101 (pdflush) Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Finally kernel dies, after these error messages. This issue is not found till Linux-2.6.28.10 kernel version, KGDBOE works fine in x86 PowerPC. Now the bug is seen in x86 (32bit) and PowerPC from kernel version Linux-2.6.29 Hope this should not be raw_smp_processor_id issue ! The CPU ID returned in both arch's is 0. Which patch in netpoll* or any net device has caused this issue. One more thing to notice in x86 or PowerPC the kernel dies exactly after reply of four threads/packets. Thanks, Srikanth Krishnakar ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Initialize DBCR0 for PPC440 targets
Hi John, I am not finding any conclusion of the plan to add DBCR0 initialization code to head_44x.S after this discussion : http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html#a23049044 Can you please comment ? Thanks, -Srikanth Krishnakar On Mon, May 25, 2009 at 12:09 PM, Grant Likely grant.lik...@secretlab.ca wrote: On Mon, May 25, 2009 at 12:30 AM, srikanth krishnakar skrishna...@gmail.com wrote: Hello Grant, Is there any conclusion of the below discussion: http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html Xilinx target (virtex5) hangs (while running GDBServer KGDB) without the DBCR0 initialization. Can you please comment on this ? IIRC, John Linn was hacking on a patch. Search the mailing list archives for DBCR0. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Initialize DBCR0 for PPC440 targets
Hello Grant, Is there any conclusion of the below discussion: http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html Xilinx target (virtex5) hangs (while running GDBServer KGDB) without the DBCR0 initialization. Can you please comment on this ? Thanks, -Srikanth On Wed, May 20, 2009 at 11:20 AM, srikanth krishnakar skrishna...@gmail.com wrote: Hi David, I am not sure how the IDM behaves on few of PPC440 targets which don't have boot loaders. I have a reference for your question: http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html Without this fix (given patch) I am facing problems with GDB, and further target hangs while running gdbserver ! Thanks, Srikanth On Wed, May 20, 2009 at 5:23 AM, David Gibson da...@gibson.dropbear.id.au wrote: On Tue, May 19, 2009 at 06:38:53PM +0530, srikanth krishnakar wrote: Hi, kernel- 2.6.29 Debug technique: KGDB The PowerPC kernel does not initialize the PPC440 DBCR0 register. This prevents the use of software breakpoints in case of internal debug mode. Looking into head_fsl_booke.S for initialization of DBCR0 is used by boot-loaders. It seems head_44x.S lacks this step of DBCR0 register initialization. So fixing this with initializing the DBCR0 register as shown below : Subject: [PATCH] powerpc: 44x: Initialize DBCR0 for targets not having bootloader The kernel does not initialize the PPC440 DBCR0 register. This prevents (among other things) the use of software breakpoints with GDB. The boot loaders probably do initialize this but few targets run without a boot loader Um.. how does this prevent the use of software breakpoints with gdb? The trap instructions still work with IDM==0. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Initialize DBCR0 for PPC440 targets
Hi David, Just to correct the statements : How the DBCR0 is initialized on targets that don't use boot loaders ? -Srikant On Wed, May 20, 2009 at 11:30 AM, David Gibson da...@gibson.dropbear.id.au wrote: On Wed, May 20, 2009 at 11:20:46AM +0530, srikanth krishnakar wrote: Hi David, I am not sure how the IDM behaves on few of PPC440 targets which don't have boot loaders. I have a reference for your question: http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html Without this fix (given patch) I am facing problems with GDB, and further target hangs while running gdbserver ! That doesn't answer my question. It's not enough to say this fixes a problem you need to explain *how* it fixes the problem. And I don't see why IDM would have any effect on *software* breakpoints. On Wed, May 20, 2009 at 5:23 AM, David Gibson da...@gibson.dropbear.id.au wrote: On Tue, May 19, 2009 at 06:38:53PM +0530, srikanth krishnakar wrote: Hi, kernel- 2.6.29 Debug technique: KGDB The PowerPC kernel does not initialize the PPC440 DBCR0 register. This prevents the use of software breakpoints in case of internal debug mode. Looking into head_fsl_booke.S for initialization of DBCR0 is used by boot-loaders. It seems head_44x.S lacks this step of DBCR0 register initialization. So fixing this with initializing the DBCR0 register as shown below : Subject: [PATCH] powerpc: 44x: Initialize DBCR0 for targets not having bootloader The kernel does not initialize the PPC440 DBCR0 register. This prevents (among other things) the use of software breakpoints with GDB. The boot loaders probably do initialize this but few targets run without a boot loader Um.. how does this prevent the use of software breakpoints with gdb? The trap instructions still work with IDM==0. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Initialize DBCR0 for PPC440 targets
Hi, kernel- 2.6.29 Debug technique: KGDB The PowerPC kernel does not initialize the PPC440 DBCR0 register. This prevents the use of software breakpoints in case of internal debug mode. Looking into head_fsl_booke.S for initialization of DBCR0 is used by boot-loaders. It seems head_44x.S lacks this step of DBCR0 register initialization. So fixing this with initializing the DBCR0 register as shown below : Subject: [PATCH] powerpc: 44x: Initialize DBCR0 for targets not having bootloader The kernel does not initialize the PPC440 DBCR0 register. This prevents (among other things) the use of software breakpoints with GDB. The boot loaders probably do initialize this but few targets run without a boot loader --- arch/powerpc/kernel/head_44x.S | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/arch/powerpc/kernel/head_44x.S b/arch/powerpc/kernel/head_44x.S index a4a890a..b413bc4 100644 --- a/arch/powerpc/kernel/head_44x.S +++ b/arch/powerpc/kernel/head_44x.S @@ -240,6 +240,18 @@ skpinv:addir4,r4,1 /* Increment */ lis r4,interrupt_b...@h /* IVPR only uses the high 16-bits */ mtspr SPRN_IVPR,r4 +#if !defined(CONFIG_BDI_SWITCH) +/* + * The Abatron BDI JTAG debugger does not tolerate others + * mucking with the debug registers. + */ +lis r2,dbcr0_...@h +mtspr SPRN_DBCR0,r2 +isync +/* clear any residual debug events */ +li r2,-1 +mtspr SPRN_DBSR,r2 +#endif /* * This is where the main kernel code starts. */ Any suggestions or comments on this ? Thanks, -Srikant ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Initialize DBCR0 for PPC440 targets
Hi David, I am not sure how the IDM behaves on few of PPC440 targets which don't have boot loaders. I have a reference for your question: http://www.nabble.com/Question-about-DBCR0-initialization-for-440-td23049044.html Without this fix (given patch) I am facing problems with GDB, and further target hangs while running gdbserver ! Thanks, Srikanth On Wed, May 20, 2009 at 5:23 AM, David Gibson da...@gibson.dropbear.id.au wrote: On Tue, May 19, 2009 at 06:38:53PM +0530, srikanth krishnakar wrote: Hi, kernel- 2.6.29 Debug technique: KGDB The PowerPC kernel does not initialize the PPC440 DBCR0 register. This prevents the use of software breakpoints in case of internal debug mode. Looking into head_fsl_booke.S for initialization of DBCR0 is used by boot-loaders. It seems head_44x.S lacks this step of DBCR0 register initialization. So fixing this with initializing the DBCR0 register as shown below : Subject: [PATCH] powerpc: 44x: Initialize DBCR0 for targets not having bootloader The kernel does not initialize the PPC440 DBCR0 register. This prevents (among other things) the use of software breakpoints with GDB. The boot loaders probably do initialize this but few targets run without a boot loader Um.. how does this prevent the use of software breakpoints with gdb? The trap instructions still work with IDM==0. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: KGDBOC testing on linux-2.6.30-rc4
Hi all,
Target : PowerPC, Virtex-440 Generic
Serial port : Xilinx 16550 Uart ( depends on OF_PLATFORM)
Further investigation of KGDBOC on PowerPC shows that kgdboc hangs at :
In file : arch/powerpc/include/asm/kgdb.h
*static inline void* arch_kgdb_breakpoint(*void*)
{
*asm*(*.long 0x7d821008*); /* *twge r2, r2 **/ *
KGDBOC Hangs here* * ---*
-
Debug Log:
r...@10.1.2.55:~# echo g
/proc/sysrq-trigger
SysRq :
GDB
1sysrq_handle_gdb
Entering KGDB
1-1---kgdb_breakpoint
1-2---kgdb_breakpoint
1-3---kgdb_breakpoint
1-1---arch_kgdb_breakpoint
-
Any comments or suggestions
-Srikanth
--
On Mon, May 4, 2009 at 8:12 PM, Bruce Ashfield bruce.ashfi...@gmail.comwrote:
On Mon, May 4, 2009 at 9:13 AM, srikanth krishnakar
skrishna...@gmail.com wrote:
Hi all,
I need help in kgdboc testing on PowerPC target.
Have you tried contacting the maintainer ? (I noticed that Jason
wasn't cc'd), just in case it isn't simply a use case problem and
might be related to KGDB internals.
KGDB
P: Jason Wessel
M: jason.wes...@windriver.com
I've tested KGDBOC up to the 2.6.29 kernel and it worked fine
on a series of 85xx boards. I haven't had a chance on 2.6.30-rcX
yet, so something may have changed.
Linux Kernel: 2.6.30-rc4
KGDB method : KGDBOC
Arch: PowerPC
Note: Attached is the kernel config used.
Has anyone tested KGDBOC for Serial 8250, and the serial port has
dependency
on OF_PLATFORM driver ?
Here are the kernel config options:
Device Drivers ---
Character devices ---
Serial drivers ---
* 8250/16550 and
compatible serial support
[*] Console on
8250/16550 and compatible serial port
(4) Number of
8250/16550 serial ports to register at runtime
[ ] Extended
8250/16550
serial driver options
*** Non-8250 serial
port support ***
* Xilinx uartlite
serial port support
[*] Support for
console on Xilinx uartlite serial port
Digi
International
NEO PCI Support
* Serial port on
Open
Firmware platform bus
NWP serial port
driver
Kernel hacking ---
-*- Magic SysRq key
[*] Kernel debugging
[*] KGDB: kernel debugging with remote gdb
---
--- KGDB: kernel debugging with remote
gdb
* KGDB: use kgdb over the serial console
--
In the process :
On the target side :
...
Serial: 8250/16550 driver, 4 ports, IRQ
sharing
disabled
83e0.serial: ttyS0 at MMIO 0x83e01003
(irq
= 16) is a
16550A
console [ttyS0]
enabled
kgdb: Registered I/O driver kgdboc.
.
r...@10.161.2.35:~# echo g
/proc/sysrq-trigger
SysRq : GDB
Entering KGDB
On host side :
[r...@srikant linux-2.6]#
powerpc-linux-gnu-gdb
vmlinux-puru
GNU gdb G++ 4.3-150) 6.8.50.20081022-cvs
Copyright (C) 2008 Free Software Foundation,
Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change
and
redistribute it.
There is NO WARRANTY, to the extent permitted
by
law. Type show copying
and show warranty for details.
This GDB was configured as
--host=i686-pc-linux-gnu --target=powerpc-linux-gnu.
For bug reporting instructions, please see:
(gdb) set remotebaud 9600
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Ignoring packet error, continuing...
warning: unrecognized item timeout in
qSupported
Re: [Kgdb-bugreport] KGDBOC testing on linux-2.6.30-rc4
On Tue, May 5, 2009 at 5:28 PM, Jason Wessel jason.wes...@windriver.comwrote:
srikanth krishnakar wrote:
Hi all,
Target : PowerPC, Virtex-440 Generic
Serial port : Xilinx 16550 Uart ( depends on OF_PLATFORM)
Further investigation of KGDBOC on PowerPC shows that kgdboc hangs at :
In file : arch/powerpc/include/asm/kgdb.h
*static inline void* arch_kgdb_breakpoint(*void*)
{
*asm*(*.long 0x7d821008*); /* *twge r2, r2 **/ *
KGDBOC Hangs here* * ---*
-
Debug Log:
r...@10.1.2.55:~# echo g
/proc/sysrq-trigger
SysRq :
GDB
1sysrq_handle_gdb
Entering KGDB
1-1---kgdb_breakpoint
1-2---kgdb_breakpoint
1-3---kgdb_breakpoint
1-1---arch_kgdb_breakpoint
-
Any comments or suggestions
I had used the 2.6.30-rc3 kernel with the PowerPC 604 system I have and
it was working fine, but the 4xx archs are a bit different.
What happens next after you execute the inline assembly is that an
exception occurs, and that is the point that the kgdb entry will
actually execute. IE:
arch/powerpc/kernel/traps.c
program_check_exception()
From there kgdb should be entered and the I/O driver gets activated.
You could put another printk in kgdb_handle_exception() in kernel/kgdb.c
to make sure it actually gets there.
Generally when the system hangs hard on an initial entry to kgdb it
means there is a problem with the I/O polling driver or there is
something else eating the kgdb exception and the kgdb exception handler
was never fired in the first place.
Jason.
Hi Jason,
Re attempted with inserting a printk in kernel/kgdb.c
kgdb_handle_exception() function but seems the kgdb exception has never
occurred !!
--
Debug Log:
r...@10.1.2.55:~# echo g /proc/sysrq-trigger
SysRq : GDB
1sysrq_handle_gdb
Entering KGDB
1-1---kgdb_breakpoint
1-2---kgdb_breakpoint
1-3---kgdb_breakpoint
1-1---arch_kgdb_breakpoint
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Ignoring packet error, continuing...
warning: unrecognized item timeout in qSupported response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
---
Inserted printk's in kernel kgdb.c :
int
kgdb_handle_exception(int evector, int signo, int ecode, struct pt_regs
*regs)
{
printk(1%s\n,__FUNCTION__);
if (kgdb_reenter_check(ks)) {
-
*Does the PowerPC uses PowerPC64 hooks ??*
as seen below from arch/powerpc/kernel/kgdb.c
/* KGDB functions to use existing PowerPC64 hooks. */
static int kgdb_debugger(struct pt_regs *regs)
{
printk(1%s\n,__FUNCTION__);
return *kgdb_handle_exception*(0, computeSignal(TRAP(regs)), 0,
regs);
---
Thanks For your co-operation, patience and help.
Regards
Srikanth
**
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
KGDB8250 on PowerPC-440 does not hit KGDB breakpoint
Hi all, I am using KGDB on powerpc-440. This is tested on* Linux-2.6.27*, the following arguments to KGDB showing init_delay of 8250 as shown below: Target Side : - Linux/PowerPC load: console=ttyS0 ip=bootp root=/dev/nfs rw kgdb8250=ttyS0,9600 kgdbwait Finalizing device tree... flat tree at 0x5ad300 *kgdb8250: ttyS0 init delayed, use io/mmio/mbase syntax for early init. * . . ... .. .. ... .. console [ttyS0] enabled kgdb: Registered I/O driver kgdb8250. Stops here - --- Host Side: (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 0xc01a760c in mem_serial_in (p=0xc036e050, offset=value optimized out) at /opt/XILINX-MVL6/SUNDAY-March-28/linux-2.6.29/arch/powerpc/include/asm/io.h:153 153 DEF_MMIO_IN_BE(in_8, 8, lbz); (gdb) info threads 14 Thread 109 (nfsiod) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 13 Thread 108 (aio/0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 12 Thread 107 (kswapd0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 11 Thread 106 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 10 Thread 105 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 But when I say Continue - Got the Error as below (gdb) c Continuing. *warning: Remote failure reply: E22* Can anybody correct me, where I am going wrong. I am not able to hit KGDB breakpoint. ? -- Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
KGDB8250 doesn't hit KGDB breakpoint in PowerPC-440
Hi all, I am using KGDB on powerpc-440. This is tested on* Linux-2.6.27*, the following arguments to KGDB showing init_delay of 8250 as shown below: Target Side : - Linux/PowerPC load: console=ttyS0 ip=bootp root=/dev/nfs rw kgdb8250=ttyS0,9600 kgdbwait Finalizing device tree... flat tree at 0x5ad300 *kgdb8250: ttyS0 init delayed, use io/mmio/mbase syntax for early init. * . . ... .. .. ... .. console [ttyS0] enabled kgdb: Registered I/O driver kgdb8250. Stops here - --- Host Side: (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 0xc01a760c in mem_serial_in (p=0xc036e050, offset=value optimized out) at /opt/linux-2.6.29/arch/powerpc/include/asm/io.h:153 153 DEF_MMIO_IN_BE(in_8, 8, lbz); (gdb) info threads 14 Thread 109 (nfsiod) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 13 Thread 108 (aio/0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 12 Thread 107 (kswapd0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 11 Thread 106 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 10 Thread 105 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 But when I say Continue - Got the Error as below (gdb) c Continuing. *warning: Remote failure reply: E22* Can anybody correct me, where I am going wrong. I am not able to hit KGDB breakpoint. ? -- Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: KGDB8250 doesn't hit KGDB breakpoint in PowerPC-440
Hi, The simple config is deprecated , when the MMIO support was added to the KGDB 8250 driver. I have to use the syntax: kgdb8250=io or mmio,address,baud rate,irq Thanks Srikanth On Sat, Mar 28, 2009 at 8:40 PM, srikanth krishnakar skrishna...@gmail.comwrote: Hi all, I am using KGDB on powerpc-440. This is tested on* Linux-2.6.27*, the following arguments to KGDB showing init_delay of 8250 as shown below: Target Side : - Linux/PowerPC load: console=ttyS0 ip=bootp root=/dev/nfs rw kgdb8250=ttyS0,9600 kgdbwait Finalizing device tree... flat tree at 0x5ad300 *kgdb8250: ttyS0 init delayed, use io/mmio/mbase syntax for early init. * . . ... .. .. ... .. console [ttyS0] enabled kgdb: Registered I/O driver kgdb8250. Stops here - --- Host Side: (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 0xc01a760c in mem_serial_in (p=0xc036e050, offset=value optimized out) at /opt/linux-2.6.29/arch/powerpc/include/asm/io.h:153 153 DEF_MMIO_IN_BE(in_8, 8, lbz); (gdb) info threads 14 Thread 109 (nfsiod) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 13 Thread 108 (aio/0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 12 Thread 107 (kswapd0) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 11 Thread 106 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 10 Thread 105 (pdflush) __switch_to (prev=value optimized out, new=0xcf8227f0) at arch/powerpc/kernel/process.c:412 But when I say Continue - Got the Error as below (gdb) c Continuing. *warning: Remote failure reply: E22* Can anybody correct me, where I am going wrong. I am not able to hit KGDB breakpoint. ? -- Regards Srikanth Krishnakar ** -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compilation of PREEMPT_RT on PowerPC PPC440 Linux-2.6.29-rc7
Hi all, Just managed to compile PREEMPT_RT on Linux-2.6.29-rc7 PowerPC, I used following patches from broken package of RT (Patch-2.6.26.8-rt16-broken-out.tar.gz) , Need to investigate further with respect to HRT, patches/patch-2.6.29-rc7 patches/patch-2.6.29-rc7-rt1.patch patches/percpu-locked-powerpc-fixups.patch patches/powerpc-02-make-the-irq-reverse-mapping-radix-tree-lockless.patch patches/powerpc-ftrace-stop-on-oops.patch patches/powerpc-match-__rw_yield-function-declaration-to-prototype.patch patches/ppc32-latency-compile-hack-fixes.patch patches/ppc32_notrace_init_functions.patch patches/ppc64-fix-preempt-unsafe-paths-accessing-per_cpu-variables.patch patches/ppc-gtod-notrace-fix.patch patches/ppc-hacks-to-allow-rt-to-run-kernbench.patch patches/ppc-make-tlb-batch-64-only.patch patches/ppc-remove-duplicate-save-stack-trace.patch patches/ppc-tlbflush-preempt.patch patches/preempt-irqs-ppc-ack-irq-fixups.patch patches/preempt-irqs-ppc-fix-b5.patch patches/preempt-irqs-ppc-fix-more-fasteoi.patch patches/preempt-realtime-powerpc-add-raw-relax-macros.patch patches/preempt-realtime-powerpc-b2.patch patches/preempt-realtime-powerpc-b3.patch patches/preempt-realtime-powerpc-b4.patch patches/preempt-realtime-powerpc-celleb-raw-spinlocks.patch patches/preempt-realtime-powerpc.patch patches/preempt-realtime-powerpc-tlb-batching.patch patches/preempt-realtime-powerpc-update.patch patches/preempt-irqs-ppc-fix-b6.patch patches/preempt-irqs-ppc.patch patches/preempt-irqs-ppc-preempt-schedule-irq-entry-fix.patch patches/rt-mutex-ppc-fix-a5.patch patches/rt-mutex-ppc.patch Please reply back, If anybody working on this !!! Or if anything is missing from this pls. let me know. Regards Srikanth ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Compilation of PREEMPT_RT on PowerPC (ppc440)
Hi all,
The latest RT patch patch-2.6.29-rc6-rt3 is throwing following compilation
errors for POWERPC linux kernel 2.6.29-rc6 :-
As I used plain vanilla kernel i.e - Linux-2.6.28 + patch-2.6.29-rc6 +
patch-2.6.29-rc6-rt3
While compiling for ppc440...
[r...@srikanth linux-2.6.29-rc6]# make ARCH=powerpc CROSS_COMPILE=ppc_440-
zImage
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm - include/asm-powerpc
CC kernel/bounds.s
GEN include/linux/bounds.h
CC arch/powerpc/kernel/asm-offsets.s
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/opt/mlg-rt-test/linux-2.6.29-rc6/arch/powerpc/include/asm/rwsem.h:24:
error: redefinition of ‘struct rw_semaphore’
In file included from
include/linux/rwsem.h:37,
from
include/linux/mm_types.h:11,
from
include/linux/sched.h:61,
from
arch/powerpc/kernel/asm-offsets.c:17:
/opt/mlg-rt-test/linux-2.6.29-rc6/arch/powerpc/include/asm/rwsem.h:46:1:
warning: __RWSEM_INITIALIZER redefined
In file included from
include/linux/spinlock.h:118,
from
include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:191:1: warning: this is the location of the previous
definition
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/opt/mlg-rt-test/linux-2.6.29-rc6/arch/powerpc/include/asm/rwsem.h:50:1:
warning: DECLARE_RWSEM redefined
In file included from include/linux/spinlock.h:118,
from include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:195:1: warning: this is the location of the previous
definition
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/opt/mlg-rt-test/linux-2.6.29-rc6/arch/powerpc/include/asm/rwsem.h:61:1:
warning: init_rwsem redefined
In file included from include/linux/spinlock.h:118,
from include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:232:1: warning: this is the location of the previous
definition
/opt/mlg-rt-test/linux-2.6.29-rc6/arch/powerpc/include/asm/rwsem.h:167:
error: expected identifier or ‘(’ before ‘{’ token
make[1]: *** [arch/powerpc/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
[r...@srikanth linux-2.6.29-rc6]#
Has anybody come across this ? If any fixes brought up for build of RT on
PowerPC, pls reply back.
Regards
Srikant
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
KGDB over serial on xilinx virtex-5 (ppc440)
Hi all, Has anybody tested KGDBOC in linux-2.6.28 for Xilinx Virtex-5 PowerPC target boards.. I just see that KGDB waits for remote connection from GDB host, but unfortunately Command line arguments were : console=ttyS0 ip=bootp root=/dev/nfs rw kgdboc=ttyS0 kgdbwait The test is been done on xilinx virtex-5 ppc440 target Target side: Serial: 8250/16550 driver4 ports, IRQ sharing disabled 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 16) is a 16550A console [ttyS0] enabled kgdb: Registered I/O driver kgdboc. kgdb: Waiting for connection from remote gdb... -- Host side -- (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Sending packet: $qSupported#37...Sending packet: $qSupported#37...Sending packet: $qSupported#37...Sending packet: $qSupported#37...Timed out. Timed out. Timed out . . -- Is anything else need to be implemented for ppc44x for KGDB to work ? -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
KGDB over serial on xilinx virtex-5 (ppc440)
Hi all, Has anybody tested KGDBOC in linux-2.6.28 for Xilinx Virtex-5 PowerPC target boards.. I just see that KGDB waits for remote connection from GDB host, but unfortunately Command line arguments were : console=ttyS0 ip=bootp root=/dev/nfs rw kgdboc=ttyS0 kgdbwait The test is been done on xilinx virtex-5 ppc440 target Target side: Serial: 8250/16550 driver4 ports, IRQ sharing disabled 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 16) is a 16550A console [ttyS0] enabled kgdb: Registered I/O driver kgdboc. kgdb: Waiting for connection from remote gdb... -- Host side -- (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Sending packet: $qSupported#37...Sending packet: $qSupported#37...Sending packet: $qSupported#37...Sending packet: $qSupported#37...Timed out. Timed out. Timed out . . -- Is anything else need to be implemented for ppc44x for KGDB to work ? -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
unsubscribe me
unsubscribe me plz. -- The Good You Do, The Best You GET Regards Srikanth Krishnakar ** ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
