* KEXEC on ARM cortex-a15 @ 2012-11-19 14:27 Naresh Bhat 2012-11-19 14:44 ` Russell King - ARM Linux 0 siblings, 1 reply; 13+ messages in thread From: Naresh Bhat @ 2012-11-19 14:27 UTC (permalink / raw) To: linux-arm-kernel Hi All, I am trying to test KEXEC feature on Cortex-a15 architecture. I am using Kernel.org v3.4 kernel, and a u-boot boot loader on Daughterboard Site 1: V2P-CA15_A7 Cortex A15 My question is do I need to pass any ATAG related information from u-boot to Kernel ?? If so what should I pass ?? Please, help me to overcome from below error message. Error Message: I can see the below question on dmesg "No ATAGs ?" ........... ............... CPU1: Unknown IPI message 0x1 Brought up 2 CPUs SMP: Total of 2 processors activated (3981.31 BogoMIPS). NET: Registered protocol family 16 No ATAGs? hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. hw-breakpoint: maximum watchpoint size is 8 bytes. Serial: AMBA PL011 UART driver .......... ............... root at arm-cortex-a15:~#kexec -f /boot/uImage --command-line="root=/dev/nfs rw ip=dhcp mmci.fmax=6000000 -serial stdio console=ttyAMA0" Cannot open /proc/atags: No such file orStarting new kernel directory Bye! Uncompressing Linux... -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-19 14:27 KEXEC on ARM cortex-a15 Naresh Bhat @ 2012-11-19 14:44 ` Russell King - ARM Linux 2012-11-19 15:13 ` Will Deacon 0 siblings, 1 reply; 13+ messages in thread From: Russell King - ARM Linux @ 2012-11-19 14:44 UTC (permalink / raw) To: linux-arm-kernel On Mon, Nov 19, 2012 at 07:57:10PM +0530, Naresh Bhat wrote: > I can see the below question on dmesg "No ATAGs ?" > ........... > ............... > CPU1: Unknown IPI message 0x1 > Brought up 2 CPUs > SMP: Total of 2 processors activated (3981.31 BogoMIPS). > NET: Registered protocol family 16 > No ATAGs? That is the procfs initialization of ATAGs producing that message. If you're not booting with ATAGs but instead using DT, then you will get this message, and it's harmless... in which case kexec should be passing the DT blob to the next kernel. If it isn't, then its a kexec bug. ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-19 14:44 ` Russell King - ARM Linux @ 2012-11-19 15:13 ` Will Deacon 2012-11-19 15:38 ` Naresh Bhat 0 siblings, 1 reply; 13+ messages in thread From: Will Deacon @ 2012-11-19 15:13 UTC (permalink / raw) To: linux-arm-kernel On Mon, Nov 19, 2012 at 02:44:17PM +0000, Russell King - ARM Linux wrote: > On Mon, Nov 19, 2012 at 07:57:10PM +0530, Naresh Bhat wrote: > > I can see the below question on dmesg "No ATAGs ?" > > ........... > > ............... > > CPU1: Unknown IPI message 0x1 > > Brought up 2 CPUs > > SMP: Total of 2 processors activated (3981.31 BogoMIPS). > > NET: Registered protocol family 16 > > No ATAGs? > > That is the procfs initialization of ATAGs producing that message. If > you're not booting with ATAGs but instead using DT, then you will get > this message, and it's harmless... in which case kexec should be passing > the DT blob to the next kernel. > > If it isn't, then its a kexec bug. Naresh, please try using a bleeding-edge copy of kexec tools. Support for device-tree on ARM was only added there in the last month or so. Will ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-19 15:13 ` Will Deacon @ 2012-11-19 15:38 ` Naresh Bhat 2012-11-20 15:02 ` Naresh Bhat 0 siblings, 1 reply; 13+ messages in thread From: Naresh Bhat @ 2012-11-19 15:38 UTC (permalink / raw) To: linux-arm-kernel Hi Will Deacon, Thank you very much. I appreciate your help. Yes, it looks like it is added on Sep 7th commit f0839230276d32a67b5a4a65e199c1937adb3643 Author: Matthew Leach <matthew.leach@arm.com> Date: Fri Sep 7 10:11:26 2012 +0100 ARM: Add device tree support to the ARM platform To allow newer ARM platforms to use kexec, pass device tree information to the kernel during boot. By default the dtb is found from /proc/device-tree. A user can specify a dtb file or use legacy ATAGs ............ ..................... I will test will latest tools tomorrow. Regards -Naresh Bhat On Mon, Nov 19, 2012 at 8:43 PM, Will Deacon <will.deacon@arm.com> wrote: > On Mon, Nov 19, 2012 at 02:44:17PM +0000, Russell King - ARM Linux wrote: >> On Mon, Nov 19, 2012 at 07:57:10PM +0530, Naresh Bhat wrote: >> > I can see the below question on dmesg "No ATAGs ?" >> > ........... >> > ............... >> > CPU1: Unknown IPI message 0x1 >> > Brought up 2 CPUs >> > SMP: Total of 2 processors activated (3981.31 BogoMIPS). >> > NET: Registered protocol family 16 >> > No ATAGs? >> >> That is the procfs initialization of ATAGs producing that message. If >> you're not booting with ATAGs but instead using DT, then you will get >> this message, and it's harmless... in which case kexec should be passing >> the DT blob to the next kernel. >> >> If it isn't, then its a kexec bug. > > Naresh, please try using a bleeding-edge copy of kexec tools. Support > for device-tree on ARM was only added there in the last month or so. > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-19 15:38 ` Naresh Bhat @ 2012-11-20 15:02 ` Naresh Bhat 2012-11-20 16:02 ` Will Deacon 0 siblings, 1 reply; 13+ messages in thread From: Naresh Bhat @ 2012-11-20 15:02 UTC (permalink / raw) To: linux-arm-kernel Hi All, I downloaded, compiled and installed bleeding edge GIT repository http://horms.net/projects/kexec/ on my Cortex-a15 target. After execution of below command the target hangs. bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="root=/dev/nfs rw ip=dhcp -serial stdio console=ttyAMA0" Starting new kernel Bye! Uncompressing Linux... Any idea why it is happening ? i appreciate your help/any comments. My kernel version is v3.4 from kernel.org vexpress.dtb - Is generated from vexpress-v2p-ca15_a7.dts Thanks and Regards -Naresh Bhat On Mon, Nov 19, 2012 at 9:08 PM, Naresh Bhat <nareshgbhat@gmail.com> wrote: > Hi Will Deacon, > > Thank you very much. I appreciate your help. > > Yes, it looks like it is added on Sep 7th > > commit f0839230276d32a67b5a4a65e199c1937adb3643 > Author: Matthew Leach <matthew.leach@arm.com> > Date: Fri Sep 7 10:11:26 2012 +0100 > > ARM: Add device tree support to the ARM platform > > To allow newer ARM platforms to use kexec, pass device tree > information to the kernel during boot. > > By default the dtb is found from /proc/device-tree. A user can specify > a dtb file or use legacy ATAGs > ............ > ..................... > > I will test will latest tools tomorrow. > > Regards > -Naresh Bhat > > On Mon, Nov 19, 2012 at 8:43 PM, Will Deacon <will.deacon@arm.com> wrote: >> On Mon, Nov 19, 2012 at 02:44:17PM +0000, Russell King - ARM Linux wrote: >>> On Mon, Nov 19, 2012 at 07:57:10PM +0530, Naresh Bhat wrote: >>> > I can see the below question on dmesg "No ATAGs ?" >>> > ........... >>> > ............... >>> > CPU1: Unknown IPI message 0x1 >>> > Brought up 2 CPUs >>> > SMP: Total of 2 processors activated (3981.31 BogoMIPS). >>> > NET: Registered protocol family 16 >>> > No ATAGs? >>> >>> That is the procfs initialization of ATAGs producing that message. If >>> you're not booting with ATAGs but instead using DT, then you will get >>> this message, and it's harmless... in which case kexec should be passing >>> the DT blob to the next kernel. >>> >>> If it isn't, then its a kexec bug. >> >> Naresh, please try using a bleeding-edge copy of kexec tools. Support >> for device-tree on ARM was only added there in the last month or so. >> >> Will > > > > -- > "For things to change, we must change" > -Naresh Bhat -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-20 15:02 ` Naresh Bhat @ 2012-11-20 16:02 ` Will Deacon 2012-11-20 17:14 ` Naresh Bhat 2012-11-21 8:21 ` Naresh Bhat 0 siblings, 2 replies; 13+ messages in thread From: Will Deacon @ 2012-11-20 16:02 UTC (permalink / raw) To: linux-arm-kernel On Tue, Nov 20, 2012 at 03:02:17PM +0000, Naresh Bhat wrote: > Hi All, > > I downloaded, compiled and installed bleeding edge GIT repository > http://horms.net/projects/kexec/ on my Cortex-a15 target. > After execution of below command the target hangs. > > bash-4.2# kexec -f uImage --dtb=vexpress.dtb > --command-line="root=/dev/nfs rw ip=dhcp -serial stdio > console=ttyAMA0" > Starting new kernel > Bye! > Uncompressing Linux... > > Any idea why it is happening ? > > i appreciate your help/any comments. > > My kernel version is v3.4 from kernel.org > vexpress.dtb - Is generated from vexpress-v2p-ca15_a7.dts Your platform probably doesn't park the secondary CPUs correctly. Try booting the kexec host kernel with 'nosmp' on the command line. Will ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-20 16:02 ` Will Deacon @ 2012-11-20 17:14 ` Naresh Bhat 2012-11-21 8:21 ` Naresh Bhat 1 sibling, 0 replies; 13+ messages in thread From: Naresh Bhat @ 2012-11-20 17:14 UTC (permalink / raw) To: linux-arm-kernel Hi Will Deacon, > Your platform probably doesn't park the secondary CPUs correctly. Try > booting the kexec host kernel with 'nosmp' on the command line. Do you mean I need to boot the STEP1: Daughterboard Site 1: V2P-CA15_A7 Cortex A15 I should boot with "nosmp" in command line STEP2: run the kexec on the above booted target ? --Thanks and Regards "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-20 16:02 ` Will Deacon 2012-11-20 17:14 ` Naresh Bhat @ 2012-11-21 8:21 ` Naresh Bhat 2012-11-21 10:22 ` Will Deacon 1 sibling, 1 reply; 13+ messages in thread From: Naresh Bhat @ 2012-11-21 8:21 UTC (permalink / raw) To: linux-arm-kernel Hi Will, I have disabled the SMP on host kernel. But still I am facing the issue as below bash-4.2# ls uImage vexpress.dtb bash-4.2# bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" Starting new kernel Bye! Uncompressing Linux... I am not able to see anything after "Uncompressing Linux...". I have tested with different kernel versions after disabling the SMP feature, I have also tested with the /dev/tty devices as command line parameter. But no luck. I have the following questions: 1. Probably is it doing something and nothing printed on console ?? 2. Is it a problem with DTB file or console issue ?? Any idea's will be helpful. I really appreciate your help to overcome from above issue. Kernel bootup logs: ============= Starting kernel ... Booting Linux on physical CPU 0 Initializing cgroup subsys cpuset Linux version 3.7.0-rc6+ (nareshbhat at Lenovo) (gcc version 4.7.0) #2 Thu Nov 22 13:28:13 IST 2012 CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine: ARM-Versatile Express, model: V2P-CA15_CA7 Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096 Kernel command line: root=/dev/nfs rw ip=dhcp nfsroot=<Host-IP>:/mnt/sda3/nfs/cortexa15/core-image -serial stdio console=ttyAMA0 init=/bi n/bash PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1024MB = 1024MB total Memory: 1034848k/1034848k available, 13728k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xc0800000 - 0xff000000 (1000 MB) lowmem : 0x80000000 - 0xc0000000 (1024 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x8041ea04 (4187 kB) .init : 0x8041f000 - 0x80445b24 ( 155 kB) .data : 0x80446000 - 0x8046cb80 ( 155 kB) .bss : 0x8046cba4 - 0x8048cae8 ( 128 kB) SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:16 nr_irqs:16 16 sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms Console: colour dummy device 80x30 Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Setting up static identity map for 0x80312a00 - 0x80312a58 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations No ATAGs? hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. hw-breakpoint: maximum watchpoint size is 8 bytes. Serial: AMBA PL011 UART driver 1c090000.uart: ttyAMA0 at MMIO 0x1c090000 (irq = 37) is a PL011 rev2 console [ttyAMA0] enabled 1c0a0000.uart: ttyAMA1 at MMIO 0x1c0a0000 (irq = 38) is a PL011 rev2 1c0b0000.uart: ttyAMA2 at MMIO 0x1c0b0000 (irq = 39) is a PL011 rev2 1c0c0000.uart: ttyAMA3 at MMIO 0x1c0c0000 (irq = 40) is a PL011 rev2 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Advanced Linux Sound Architecture Driver Initialized. Switching to clocksource v2m-timer1 NET: Registered protocol family 2 TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP: reno registered UDP hash table entries: 512 (order: 1, 8192 bytes) UDP-Lite hash table entries: 512 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available jffs2: version 2.2. (NAND) ? 2001-2006 Red Hat, Inc. msgmni has been set to 2021 io scheduler noop registered (default) clcd-pl11x: probe of 1c1f0000.clcd failed with error -22 smsc911x: Driver version 2008-10-21 libphy: smsc911x-mdio: probed smsc911x 1a000000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1a000000.etherne:01, irq=-1) smsc911x 1a000000.ethernet eth0: MAC Address: <MAC> nxp-isp1760 1b000000.usb: NXP ISP1760 USB Host Controller nxp-isp1760 1b000000.usb: new USB bus registered, assigned bus number 1 nxp-isp1760 1b000000.usb: bus width: 32, oc: digital nxp-isp1760 1b000000.usb: irq 48, io mem 0x1b000000 nxp-isp1760 1b000000.usb: USB ISP 1761 HW rev. 1 started usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: NXP ISP1760 USB Host Controller usb usb1: Manufacturer: Linux 3.7.0-rc6+ isp1760-hcd usb usb1: SerialNumber: 1b000000.usb hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mousedev: PS/2 mouse device common for all mice rtc-pl031 1c170000.rtc: rtc core: registered pl031 as rtc0 /motherboard/iofpga at 3,00000000/mmci at 050000 has no 'max-frequency' property mmci-pl18x mb:mmci: mmc0: PL180 manf 41 rev0 at 0x1c050000 irq 41,42 (pio) usbcore: registered new interface driver usbhid usbhid: USB HID core driver aaci-pl041 1c040000.aaci: ARM AC'97 Interface PL041 rev0 at 0x1c040000, irq 43 aaci-pl041 1c040000.aaci: FIFO 512 entries oprofile: using timer interrupt. TCP: cubic registered NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 rtc-pl031 1c170000.rtc: setting system clock to 2012-11-22 08:00:36 UTC (1353571236) smsc911x 1a000000.ethernet eth0: SMSC911x/921x identified at 0xc08c0000, IRQ: 47 nxp-isp1760 1b000000.usb: port 1 high speed IP-Config: Complete: ALSA device list: #0: ARM AC'97 Interface PL041 rev0 at 0x1c040000, irq 43 usb 1-1: new high-speed USB device number 2 using nxp-isp1760 nxp-isp1760 1b000000.usb: port 1 high speed usb 1-1: New USB device found, idVendor=0471, idProduct=3526 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1: Product: ISP1520 usb 1-1: Manufacturer: Philips Semiconductors hub 1-1:1.0: USB hub found hub 1-1:1.0: 3 ports detected atkbd serio0: keyboard reset failed on 1c060000.kmi atkbd serio1: keyboard reset failed on 1c070000.kmi VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 152K bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell bash-4.2# Thanks and Regards -Naresh Bhat On Tue, Nov 20, 2012 at 9:32 PM, Will Deacon <will.deacon@arm.com> wrote: > On Tue, Nov 20, 2012 at 03:02:17PM +0000, Naresh Bhat wrote: >> Hi All, >> >> I downloaded, compiled and installed bleeding edge GIT repository >> http://horms.net/projects/kexec/ on my Cortex-a15 target. >> After execution of below command the target hangs. >> >> bash-4.2# kexec -f uImage --dtb=vexpress.dtb >> --command-line="root=/dev/nfs rw ip=dhcp -serial stdio >> console=ttyAMA0" >> Starting new kernel >> Bye! >> Uncompressing Linux... >> >> Any idea why it is happening ? >> >> i appreciate your help/any comments. >> >> My kernel version is v3.4 from kernel.org >> vexpress.dtb - Is generated from vexpress-v2p-ca15_a7.dts > > Your platform probably doesn't park the secondary CPUs correctly. Try > booting the kexec host kernel with 'nosmp' on the command line. > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-21 8:21 ` Naresh Bhat @ 2012-11-21 10:22 ` Will Deacon 2012-11-21 11:20 ` Naresh Bhat ` (3 more replies) 0 siblings, 4 replies; 13+ messages in thread From: Will Deacon @ 2012-11-21 10:22 UTC (permalink / raw) To: linux-arm-kernel On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote: > Hi Will, > > I have disabled the SMP on host kernel. But still I am facing the > issue as below > > bash-4.2# ls > uImage vexpress.dtb > bash-4.2# > bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" Can you try using a zImage instead and also specifying the console as ttyAMA0, as it looks like you're using a vexpress? > Starting new kernel > Bye! > Uncompressing Linux... This isn't really very helpful -- some more debugging on your part would be appreciated to get an insight as to what's going wrong. You could either use JTAG or put some early prints in the decompressor to work out where it goes awry. Useful things to know would be: the state of the CPU when the new kernel image is entered (if you have JTAG, you could also look at the dtb in memory to see that it looks sane) and also at which point in the decompressor it goes wrong / takes an abort (usually it's when we enable the MMU). Will ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-21 10:22 ` Will Deacon @ 2012-11-21 11:20 ` Naresh Bhat 2012-11-21 18:47 ` Naresh Bhat ` (2 subsequent siblings) 3 siblings, 0 replies; 13+ messages in thread From: Naresh Bhat @ 2012-11-21 11:20 UTC (permalink / raw) To: linux-arm-kernel Hi Will, Thank you very much. Yes, I am using Versatile express target at Daughterboard Site 1: V2P-CA15_A7 Cortex A15 1. I do not have the JTAG. I will definitely try to order and get one. 2. I have tried with the following command line options root at arm-cortex-a15:~# kexec -f zImage --dtb=vexpress.dtb --append="root=/dev/nfs rw ip=dhcp nfsroot=<Host-IP>:/mnt/sda3/nfs/cortexa15/core-image console=ttyAMA0,38400n8 nosmp" Starting new kernel Bye! Uncompressing Linux... I will try to put some more printk and get more debug information. vexpress.dtb is generated from vexpress-v2p-ca15_a7.dts file. 1. Is it possible to print the state of the CPU when the new kernel image is entered (using printk) ? 2. Is it possible to use ATAGs for kexec feature as a temporary solution on V2P-CA15_A7 Cortex A15 target ? Thanks and Regards -Naresh Bhat On Wed, Nov 21, 2012 at 3:52 PM, Will Deacon <will.deacon@arm.com> wrote: > On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote: >> Hi Will, >> >> I have disabled the SMP on host kernel. But still I am facing the >> issue as below >> >> bash-4.2# ls >> uImage vexpress.dtb >> bash-4.2# >> bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" > > Can you try using a zImage instead and also specifying the console as > ttyAMA0, as it looks like you're using a vexpress? > >> Starting new kernel >> Bye! >> Uncompressing Linux... > > This isn't really very helpful -- some more debugging on your part would be > appreciated to get an insight as to what's going wrong. You could either use > JTAG or put some early prints in the decompressor to work out where it goes > awry. > > Useful things to know would be: the state of the CPU when the new kernel > image is entered (if you have JTAG, you could also look at the dtb in memory > to see that it looks sane) and also at which point in the decompressor it > goes wrong / takes an abort (usually it's when we enable the MMU). > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-21 10:22 ` Will Deacon 2012-11-21 11:20 ` Naresh Bhat @ 2012-11-21 18:47 ` Naresh Bhat 2012-12-17 13:11 ` Naresh Bhat 2013-01-10 12:12 ` Naresh Bhat 3 siblings, 0 replies; 13+ messages in thread From: Naresh Bhat @ 2012-11-21 18:47 UTC (permalink / raw) To: linux-arm-kernel Hi, Can somebody suggest me which JTAG I should purchase for V2P-CA15_A7 Cortex A15 target ? I would be great if you provide me a web link. I will appreciate your help. Thanks and Regards -Naresh Bhat On Wed, Nov 21, 2012 at 3:52 PM, Will Deacon <will.deacon@arm.com> wrote: > On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote: >> Hi Will, >> >> I have disabled the SMP on host kernel. But still I am facing the >> issue as below >> >> bash-4.2# ls >> uImage vexpress.dtb >> bash-4.2# >> bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" > > Can you try using a zImage instead and also specifying the console as > ttyAMA0, as it looks like you're using a vexpress? > >> Starting new kernel >> Bye! >> Uncompressing Linux... > > This isn't really very helpful -- some more debugging on your part would be > appreciated to get an insight as to what's going wrong. You could either use > JTAG or put some early prints in the decompressor to work out where it goes > awry. > > Useful things to know would be: the state of the CPU when the new kernel > image is entered (if you have JTAG, you could also look at the dtb in memory > to see that it looks sane) and also at which point in the decompressor it > goes wrong / takes an abort (usually it's when we enable the MMU). > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-21 10:22 ` Will Deacon 2012-11-21 11:20 ` Naresh Bhat 2012-11-21 18:47 ` Naresh Bhat @ 2012-12-17 13:11 ` Naresh Bhat 2013-01-10 12:12 ` Naresh Bhat 3 siblings, 0 replies; 13+ messages in thread From: Naresh Bhat @ 2012-12-17 13:11 UTC (permalink / raw) To: linux-arm-kernel Hi Will Deacon, Can you please point me to a GIT repository from where I can pull the "MMU disabling code and kexec fixes" ? I appreciate your help. Thanks and Regards -Naresh Bhat On Wed, Nov 21, 2012 at 3:52 PM, Will Deacon <will.deacon@arm.com> wrote: > On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote: >> Hi Will, >> >> I have disabled the SMP on host kernel. But still I am facing the >> issue as below >> >> bash-4.2# ls >> uImage vexpress.dtb >> bash-4.2# >> bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" > > Can you try using a zImage instead and also specifying the console as > ttyAMA0, as it looks like you're using a vexpress? > >> Starting new kernel >> Bye! >> Uncompressing Linux... > > This isn't really very helpful -- some more debugging on your part would be > appreciated to get an insight as to what's going wrong. You could either use > JTAG or put some early prints in the decompressor to work out where it goes > awry. > > Useful things to know would be: the state of the CPU when the new kernel > image is entered (if you have JTAG, you could also look at the dtb in memory > to see that it looks sane) and also at which point in the decompressor it > goes wrong / takes an abort (usually it's when we enable the MMU). > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
* KEXEC on ARM cortex-a15 2012-11-21 10:22 ` Will Deacon ` (2 preceding siblings ...) 2012-12-17 13:11 ` Naresh Bhat @ 2013-01-10 12:12 ` Naresh Bhat 3 siblings, 0 replies; 13+ messages in thread From: Naresh Bhat @ 2013-01-10 12:12 UTC (permalink / raw) To: linux-arm-kernel Hi Will Deacon, The KEXEC feature is working fine on ARM cortex-a15 versatile express target. I have used bleeding edge kexec-tools and v3.8-rc2 kernel. Thank you very much for all the support and help. Regards -Naresh Bhat On Wed, Nov 21, 2012 at 3:52 PM, Will Deacon <will.deacon@arm.com> wrote: > On Wed, Nov 21, 2012 at 08:21:21AM +0000, Naresh Bhat wrote: >> Hi Will, >> >> I have disabled the SMP on host kernel. But still I am facing the >> issue as below >> >> bash-4.2# ls >> uImage vexpress.dtb >> bash-4.2# >> bash-4.2# kexec -f uImage --dtb=vexpress.dtb --command-line="console=ttyS0" > > Can you try using a zImage instead and also specifying the console as > ttyAMA0, as it looks like you're using a vexpress? > >> Starting new kernel >> Bye! >> Uncompressing Linux... > > This isn't really very helpful -- some more debugging on your part would be > appreciated to get an insight as to what's going wrong. You could either use > JTAG or put some early prints in the decompressor to work out where it goes > awry. > > Useful things to know would be: the state of the CPU when the new kernel > image is entered (if you have JTAG, you could also look at the dtb in memory > to see that it looks sane) and also at which point in the decompressor it > goes wrong / takes an abort (usually it's when we enable the MMU). > > Will -- "For things to change, we must change" -Naresh Bhat ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2013-01-10 12:12 UTC | newest] Thread overview: 13+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-11-19 14:27 KEXEC on ARM cortex-a15 Naresh Bhat 2012-11-19 14:44 ` Russell King - ARM Linux 2012-11-19 15:13 ` Will Deacon 2012-11-19 15:38 ` Naresh Bhat 2012-11-20 15:02 ` Naresh Bhat 2012-11-20 16:02 ` Will Deacon 2012-11-20 17:14 ` Naresh Bhat 2012-11-21 8:21 ` Naresh Bhat 2012-11-21 10:22 ` Will Deacon 2012-11-21 11:20 ` Naresh Bhat 2012-11-21 18:47 ` Naresh Bhat 2012-12-17 13:11 ` Naresh Bhat 2013-01-10 12:12 ` Naresh Bhat
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).