Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood schrieb: Andre Schwarz wrote: Scott Wood schrieb: Andre Schwarz wrote: -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] It looks like you have some memory corruption between here... clocksource: timebase mult[3c1] shift[22] registered !! -> check_legacy_serial_console() can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] ! !!! ...and here. -Scott Scott, are you talking about a possible hardware problem or misbehaving code ? Either. The same OF call is done in both places with the same argument, but is getting different results. Does it look like something gets overwritten during initrd extraction/movement ? Don't know. The system has 512MB RAM which means that we need 2 BAT regs to map the memory. I've found comments in Freescale u-boot header files that currently a max of 256MB is supported. I never understood why ? Could this problem be related to this ? Kim's probably be the best one to answer u-boot questions. -Scott Scott + Kim, as mentioned before I have re-built u-boot with the following modifications : - Reduce Memsize from 512 to 256MB - Skipped 2nd BAT setup dtb looks the same but memory size set to 256MB. System boots fine - this is weird ! I'm not really familiar with the powerpc tree of the kernel and far out of sync with the current development. Could you have a look at this ? Any ideas right now ? Thanks, Andre ## Booting kernel from Legacy Image at ff81 ... Image Name: 2.6.25 mvBL-M7 MPC8343 #12 Image Type: PowerPC Linux Kernel Image (uncompressed) Data Size:2494236 Bytes = 2.4 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK ## Flattened Device Tree blob at Booting using the fdt blob at 0x60 ## Loading init Ramdisk from Legacy Image at 0100 ... Image Name: mvBC-1G uInitrd #1.1.03 Image Type: PowerPC Linux RAMDisk Image (uncompressed) Data Size:2654208 Bytes = 2.5 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 0fcb7000, end 0ff3f000 ... OK -> early_init_devtree(c060) search "chosen", depth: 0, uname: search "chosen", depth: 1, uname: chosen Looking for initrd properties... <3>initrd_start=0xcfcb7000 initrd_end=0xcff3f000 Command line is: root=/dev/ram ro rootfstype=squashfs dt_root_size_cells = 1 dt_root_addr_cells = 1 memory scan node memory, reg size 8, data: 0 1000 2 1, - 0 , 1000 reserving: fcb7000 -> 288001 Phys. mem: 1000 -> move_device_tree <- move_device_tree Scanning CPUs ... boot cpu: logical 0 physical 0 <- early_init_devtree() Using mvBlueLYNX-M7 machine description Linux version 2.6.25-rc8-01197-g1de15bb-dirty ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #12 PREEMPT Wed Apr 9 14:40:48 CEST 2008 -> unflatten_device_tree() size is 192c, allocating... unflattening cfffe6d0... fixed up name for -> fixed up name for chosen -> chosen fixed up name for [EMAIL PROTECTED] -> wdt fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> pic fixed up name for [EMAIL PROTECTED] -> ppcboot_env fixed up name for [EMAIL PROTECTED] -> ppcboot_env_red fixed up name for [EMAIL PROTECTED] -> u-boot_autoscript fixed up name for [EMAIL PROTECTED] -> u-boot_autoscript_red fixed up name for [EMAIL PROTECTED] -> dtb fixed up name for [EMAIL PROTECTED] -> dtb_red fixed up name for [EMAIL PROTECTED] -> kernel fixed up name for [EMAIL PROTECTED] -> rfs fixed up name for [EMAIL PROTECTED] -> u-boot fixed up name for [EMAIL PROTECTED] -> fpga <- unflatten_device_tree() Found initrd at 0xcfcb7000:0xcff3f000 -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] legacy_serial_console = 0 default console speed = 115740 <- find_legacy_serial_port() console [udbg0] enabled setup_arch: bootmem mvblm7_setup_arch() Adding PCI host bridge /[EMAIL PROTECTED] Found MPC83xx PCI host bridge at 0xe0008500. Firmware bus number: 0->0 ->Hose at 0xc0281000, cfg_addr=0xfdffd300,cfg_data=0xfdffd304 PCI host bridge /[EMAIL PROTECTED] (primary) ranges: MEM 0x9000..0x9fff -> 0x9000 MEM 0x8000..0x8fff -> 0x8000 Prefetch IO 0xe200..0xe20f -> 0x arch: exit Zone PFN ranges: DMA 0 ->65536 Normal 65536 ->65536 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 ->65536 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 6
Re: MPC8343 - "unable to handle paging request @ 0"
Andre Schwarz wrote: Scott Wood schrieb: Andre Schwarz wrote: -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] It looks like you have some memory corruption between here... clocksource: timebase mult[3c1] shift[22] registered !! -> check_legacy_serial_console() can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] ! !!! ...and here. -Scott Scott, are you talking about a possible hardware problem or misbehaving code ? Either. The same OF call is done in both places with the same argument, but is getting different results. Does it look like something gets overwritten during initrd extraction/movement ? Don't know. The system has 512MB RAM which means that we need 2 BAT regs to map the memory. I've found comments in Freescale u-boot header files that currently a max of 256MB is supported. I never understood why ? Could this problem be related to this ? Kim's probably be the best one to answer u-boot questions. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood schrieb: Andre Schwarz wrote: -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] It looks like you have some memory corruption between here... clocksource: timebase mult[3c1] shift[22] registered !! -> check_legacy_serial_console() can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] ! !!! ...and here. -Scott Scott, are you talking about a possible hardware problem or misbehaving code ? Does it look like something gets overwritten during initrd extraction/movement ? The system has 512MB RAM which means that we need 2 BAT regs to map the memory. I've found comments in Freescale u-boot header files that currently a max of 256MB is supported. I never understood why ? Could this problem be related to this ? Do I need to supply reserved memory regions ? I thought u-boot is doing so for initrd and the kernel don't need it ... I'll rebuild u-boot with 256MB memory size and do an extra run with memory test - just to make sure. Any hints where to look else ? regards, Andre MATRIX VISION GmbH, Talstra�e 16, DE-71570 Oppenweiler - Registergericht: Amtsgericht Stuttgart, HRB 271090 Gesch�ftsf�hrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
Andre Schwarz wrote: -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] It looks like you have some memory corruption between here... clocksource: timebase mult[3c1] shift[22] registered !! -> check_legacy_serial_console() can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] ! !!! ...and here. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood schrieb: On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote: after building a debug kernel and attaching the bdi2000 it looks like the crash occurs during "console_init()" ... Does your device tree have a /chosen node after u-boot is done with it? find_legacy_serial_ports() can crash otherwise (we really should fix that). Since we're using a dtb I omit the "console=..." argument for the kernel. Is this correct ? It's OK if you have /chosen/linux,stdout-path. If "console=/dev/ttyS0,115200N8" argument is given the serial console stops working after console_init On other PowerPC system I could see something like this during boot : -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] legacy_serial_console = 1 default console speed = 115340 <- find_legacy_serial_port() Should I see this message also ? Only if you enable debug messages in legacy_serial.c. Have I misconfigured anything ? One thing that sticks out from the above is that you ask for ttyS0, but the stdout you list from the other system corresponds to ttyS1. Is this just a difference between the two systems? -Scott Scott, I've added kallsyms and the #debug in legacy_serial. Obviously there's missing something -> see error "can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] !" below. Can you help here ? Thanks, Andre ## Booting kernel from Legacy Image at ff81 ... Image Name: 2.6.25 mvBL-M7 MPC8343 #12 Image Type: PowerPC Linux Kernel Image (uncompressed) Data Size:2494236 Bytes = 2.4 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK ## Flattened Device Tree blob at Booting using the fdt blob at 0x60 ## Loading init Ramdisk from Legacy Image at 0100 ... Image Name: mvBC-1G uInitrd #1.1.03 Image Type: PowerPC Linux RAMDisk Image (uncompressed) Data Size:2654208 Bytes = 2.5 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 1fcb7000, end 1ff3f000 ... OK -> early_init_devtree(c060) search "chosen", depth: 0, uname: search "chosen", depth: 1, uname: chosen Looking for initrd properties... <3>initrd_start=0xdfcb7000 initrd_end=0xdff3f000 Command line is: root=/dev/ram ro rootfstype=squashfs dt_root_size_cells = 1 dt_root_addr_cells = 1 memory scan node memory, reg size 8, data: 0 2000 2 1, - 0 , 2000 reserving: 1fcb7000 -> 288001 Phys. mem: 2000 -> move_device_tree <- move_device_tree Scanning CPUs ... boot cpu: logical 0 physical 0 <- early_init_devtree() Using mvBlueLYNX-M7 machine description Linux version 2.6.25-rc8-01197-g1de15bb-dirty ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #12 PREEMPT Wed Apr 9 14:40:48 CEST 2008 -> unflatten_device_tree() size is 192c, allocating... unflattening dfffe6d0... fixed up name for -> fixed up name for chosen -> chosen fixed up name for [EMAIL PROTECTED] -> wdt fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> pic fixed up name for [EMAIL PROTECTED] -> ppcboot_env fixed up name for [EMAIL PROTECTED] -> ppcboot_env_red fixed up name for [EMAIL PROTECTED] -> u-boot_autoscript fixed up name for [EMAIL PROTECTED] -> u-boot_autoscript_red fixed up name for [EMAIL PROTECTED] -> dtb fixed up name for [EMAIL PROTECTED] -> dtb_red fixed up name for [EMAIL PROTECTED] -> kernel fixed up name for [EMAIL PROTECTED] -> rfs fixed up name for [EMAIL PROTECTED] -> u-boot fixed up name for [EMAIL PROTECTED] -> fpga <- unflatten_device_tree() Found initrd at 0xdfcb7000:0xdff3f000 -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] legacy_serial_console = 0 default console speed = 115740 <- find_legacy_serial_port() console [udbg0] enabled setup_arch: bootmem mvblm7_setup_arch() arch: exit Zone PFN ranges: DMA 0 -> 131072 Normal 131072 -> 131072 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 -> 131072 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: root=/dev/ram ro rootfstype=squashfs PID hash table entries: 2048 (order: 11, 8192 bytes) clocksource: timebase mult[3c1] shift[22] registered !! -> check_legacy_serial_console() can't find stdout package /[EMAIL PROTECTED]/[EMAIL PROTECTED] ! !!! Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 514048k/524288k available (2328k kernel code, 9676k res
Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood wrote: On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote: after building a debug kernel and attaching the bdi2000 it looks like the crash occurs during "console_init()" ... Does your device tree have a /chosen node after u-boot is done with it? find_legacy_serial_ports() can crash otherwise (we really should fix that). latest u-boot does add the chosen node. As far as I know it's for initrd setup ... don't know if it's complete. Since we're using a dtb I omit the "console=..." argument for the kernel. Is this correct ? It's OK if you have /chosen/linux,stdout-path. that sounds promising ! Haven't seen this and will have a closer look. If "console=/dev/ttyS0,115200N8" argument is given the serial console stops working after console_init On other PowerPC system I could see something like this during boot : -> find_legacy_serial_port() stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] legacy_serial_console = 1 default console speed = 115340 <- find_legacy_serial_port() Should I see this message also ? Only if you enable debug messages in legacy_serial.c. ok. Have I misconfigured anything ? One thing that sticks out from the above is that you ask for ttyS0, but the stdout you list from the other system corresponds to ttyS1. Is this just a difference between the two systems? Yes - the log from the MPC8568 is a copy&paste from another posting. It's not my system. I want ttyS0. -Scott I appreciate your help ! Thanks, André MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler - Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote: > after building a debug kernel and attaching the bdi2000 it looks like > the crash occurs during "console_init()" ... Does your device tree have a /chosen node after u-boot is done with it? find_legacy_serial_ports() can crash otherwise (we really should fix that). > Since we're using a dtb I omit the "console=..." argument for the > kernel. Is this correct ? It's OK if you have /chosen/linux,stdout-path. > If "console=/dev/ttyS0,115200N8" argument is given the serial console > stops working after console_init > > > On other PowerPC system I could see something like this during boot : > > -> find_legacy_serial_port() > stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED] > legacy_serial_console = 1 > default console speed = 115340 > <- find_legacy_serial_port() > > > Should I see this message also ? Only if you enable debug messages in legacy_serial.c. > Have I misconfigured anything ? One thing that sticks out from the above is that you ask for ttyS0, but the stdout you list from the other system corresponds to ttyS1. Is this just a difference between the two systems? -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
On Tue, Apr 08, 2008 at 10:51:18AM +0200, Andre Schwarz wrote: > Call Trace: > [c01f9ef0] [c001c190] (unreliable) > [c01f9f10] [c0140c84] > [c01f9f20] [c0140ccc] > [c01f9f40] [c014145c] > [c01f9f60] [c0014014] > [c01f9fa0] [c01d1a40] > [c01f9fb0] [c01ce64c] > [c01f9fc0] [c01c55ac] > [c01f9ff0] [3438] Please turn kallsyms on, which will produce an annotated call trace. Not all these addresses were in the System.map fragment. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood schrieb:
On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote:
Kernel starts and crashes with "unable to handle kernel paging request @
".
After turning debug on in some files I can see that the initrd memory
gets reserved and the dtb is parsed correctly.
PCI memory/io spaces are set up fine.
At first I thought this is a problem with the device tree since the call
trace always points to "of_"-functions and "strcmp".
Could you provide this call trace?
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Scott,
after building a debug kernel and attaching the bdi2000 it looks like
the crash occurs during "console_init()" ...
Since we're using a dtb I omit the "console=..." argument for the
kernel. Is this correct ?
If "console=/dev/ttyS0,115200N8" argument is given the serial console
stops working after console_init
On other PowerPC system I could see something like this during boot :
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
legacy_serial_console = 1
default console speed = 115340
<- find_legacy_serial_port()
Should I see this message also ?
Have I misconfigured anything ?
u-boot prints the following dtb :
...
aliases {
name = "aliases";
ethernet0 = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
ethernet1 = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
serial0 = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
serial1 = "/[EMAIL PROTECTED]/[EMAIL PROTECTED]";
pci0 = "/[EMAIL PROTECTED]";
};
cpus {
name = "cpus";
#address-cells = <0x0001>;
#size-cells = <0x>;
PowerPC,[EMAIL PROTECTED] {
name = "PowerPC,8343";
device_type = "cpu";
reg = <0x>;
d-cache-line-size = <0x0020>;
i-cache-line-size = <0x0020>;
d-cache-size = <0x8000>;
i-cache-size = <0x8000>;
timebase-frequency = <0x03f940aa>;
bus-frequency = <0x0fe502a8>;
clock-frequency = <0x17d783fc>;
};
};
memory {
name = "memory";
device_type = "memory";
reg = <0x 0x2000>;
};
[EMAIL PROTECTED] {
name = "soc8343";
#address-cells = <0x0001>;
#size-cells = <0x0001>;
device_type = "soc";
compatible = "soc";
ranges = [00 00 00 00 e0 00 00 00 00 10 00 00];
reg = <0xe000 0x0200>;
bus-frequency = <0x0fe502a8>;
[EMAIL PROTECTED] {
device_type = "watchdog";
compatible = "mpc83xx_wdt";
reg = <0x0200 0x0100>;
};
[EMAIL PROTECTED] {
name = "i2c";
#address-cells = <0x0001>;
#size-cells = <0x>;
cell-index = <0x>;
compatible = "fsl-i2c";
reg = <0x3000 0x0100>;
interrupts = <0x000e 0x0008>;
interrupt-parent = <0x0001>;
dfsrr;
};
[EMAIL PROTECTED] {
name = "i2c";
#address-cells = <0x0001>;
#size-cells = <0x>;
cell-index = <0x0001>;
compatible = "fsl-i2c";
reg = <0x3100 0x0100>;
interrupts = <0x000f 0x0008>;
interrupt-parent = <0x0001>;
dfsrr;
};
[EMAIL PROTECTED] {
name = "spi";
cell-index = <0x>;
compatible = "fsl,spi";
reg = <0x7000 0x1000>;
interrupts = <0x0010 0x0008>;
interrupt-parent = <0x0001>;
mode = "cpu";
};
[EMAIL PROTECTED] {
name = "usb";
compatible = "fsl-usb2-mph";
reg = <0x00022000 0x1000>;
#address-cells = <0x0001>;
#size-cells = <0x>;
interrupt-parent = <0x0001>;
interrupts = <0x0027 0x0008>;
phy_type = "ulpi";
po
[Fwd: Re: MPC8343 - "unable to handle paging request @ 0"]
sorry - forgot Kim + List Original-Nachricht Betreff:Re: MPC8343 - "unable to handle paging request @ 0" Datum: Tue, 08 Apr 2008 13:29:20 +0200 Von:Andre Schwarz <[EMAIL PROTECTED]> An: Scott Wood <[EMAIL PROTECTED]> Referenzen: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Scott Wood schrieb: On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote: Kernel starts and crashes with "unable to handle kernel paging request @ ". After turning debug on in some files I can see that the initrd memory gets reserved and the dtb is parsed correctly. PCI memory/io spaces are set up fine. At first I thought this is a problem with the device tree since the call trace always points to "of_"-functions and "strcmp". Could you provide this call trace? -Scott Scott, after removing "mpc834x_usb_cfg()" from my "mvblm7_setup_arch()" the crash is delayed ... regards, Andre System-map : c0012098 T strcpy c00120b4 T strncpy c00120f4 T strcat c0012120 T strcmp c0012144 T strlen ... c00ecd08 T of_find_property c00ecda4 T of_get_property c00ecdd8 T of_n_size_cells console [udbg0] enabled setup_arch: bootmem mvblm7_setup_arch() arch: exit Zone PFN ranges: DMA 0 -> 131072 Normal 131072 -> 131072 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 -> 131072 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: root=/dev/ram ro rootfstype=squashfs PID hash table entries: 2048 (order: 11, 8192 bytes) clocksource: timebase mult[3c1] shift[22] registered Unable to handle kernel paging request for data at address 0x Faulting instruction address: 0xc0012128 Oops: Kernel access of bad area, sig: 11 [#1] mvBlueLYNX-M7 Modules linked in: NIP: c0012128 LR: c00ecd44 CTR: 0007 REGS: c0193ec0 TRAP: 0300 Not tainted (2.6.25-rc8-01197-g1de15bb-dirty) MSR: 9032 CR: 48002048 XER: DAR: , DSISR: 2000 TASK = c0182510[0] 'swapper' THREAD: c0192000 GPR00: c00ecdb4 c0193f70 c0182510 c01401c7 c017a808 c00db350 GPR08: c018 000a2c20 c017d3f4 4842 dfd7 1fffd000 GPR16: dfd7 dfd7 1fff8974 1ff426f8 0004 00288000 GPR24: c0198fa0 c019 c019 c01401c8 dfa8 Call Trace: [c0193f70] [] (unreliable) [c0193f90] [c00ecdb4] [c0193fa0] [c016df50] [c0193fb0] [c017705c] [c0193fc0] [c01646b4] [c0193ff0] [3438] Instruction dump: 3884 8c050001 2c00 4082fff8 38a5 8c040001 2c00 9c050001 4082fff4 4e800020 38a3 3884 <8c650001> 2c83 8c040001 7c601851 ---[ end trace 8640abe69a316dee ]--- Kernel panic - not syncing: Attempted to kill the idle task! Rebooting in 180 seconds.. MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler - Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: MPC8343 - "unable to handle paging request @ 0"
Scott Wood schrieb: On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote: Kernel starts and crashes with "unable to handle kernel paging request @ ". After turning debug on in some files I can see that the initrd memory gets reserved and the dtb is parsed correctly. PCI memory/io spaces are set up fine. At first I thought this is a problem with the device tree since the call trace always points to "of_"-functions and "strcmp". Could you provide this call trace? -Scott Scott, thanks for your reply. please find below the output after the bootm command in u-boot. My System.map : ... c00126b8 T strcpy c00126d4 T strncpy c0012714 T strcat c0012740 T strcmp c0012764 T strlen c001277c T memcmp ... c0140bc4 T of_find_property c0140c74 T of_get_property c0140ca8 T of_device_is_compatible c0140d48 T of_match_node c0140e68 T of_find_matching_node c0140f20 T of_n_size_cells c0140f9c T of_n_addr_cells Log: # Booting kernel from Legacy Image at ff81 ... Image Name: 2.6.25 mvBL-M7 MPC8343 #1 Image Type: PowerPC Linux Kernel Image (uncompressed) Data Size:2084636 Bytes = 2 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Kernel Image ... OK OK ## Flattened Device Tree blob at Booting using the fdt blob at 0x60 ## Loading init Ramdisk from Legacy Image at 0100 ... Image Name: mvBC-1G uInitrd #1.1.03 Image Type: PowerPC Linux RAMDisk Image (uncompressed) Data Size:2654208 Bytes = 2.5 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 1fcb7000, end 1ff3f000 ... OK -> early_init_devtree(c060) search "chosen", depth: 0, uname: search "chosen", depth: 1, uname: chosen Looking for initrd properties... <3>initrd_start=0xdfcb7000 initrd_end=0xdff3f000 Command line is: root=/dev/ram ro rootfstype=squashfs dt_root_size_cells = 1 dt_root_addr_cells = 1 memory scan node memory, reg size 8, data: 0 2000 2 1, - 0 , 2000 reserving: 1fcb7000 -> 288001 Phys. mem: 2000 -> move_device_tree <- move_device_tree Scanning CPUs ... boot cpu: logical 0 physical 0 <- early_init_devtree() Using mvBlueLYNX-M7 machine description Linux version 2.6.25-rc8-01197-g1de15bb-dirty ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #1 PREEMPT Tue Apr 8 10:40:51 CEST 2008 -> unflatten_device_tree() size is 1840, allocating... unflattening dfffe7bc... fixed up name for -> fixed up name for chosen -> chosen fixed up name for aliases -> aliases fixed up name for cpus -> cpus fixed up name for PowerPC,[EMAIL PROTECTED] -> PowerPC,8343 fixed up name for memory -> memory fixed up name for [EMAIL PROTECTED] -> soc8343 fixed up name for [EMAIL PROTECTED] -> wdt fixed up name for [EMAIL PROTECTED] -> i2c fixed up name for [EMAIL PROTECTED] -> rtc fixed up name for [EMAIL PROTECTED] -> i2c fixed up name for [EMAIL PROTECTED] -> spi fixed up name for [EMAIL PROTECTED] -> usb fixed up name for [EMAIL PROTECTED] -> mdio fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet-phy fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> ethernet fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> serial fixed up name for [EMAIL PROTECTED] -> pic fixed up name for [EMAIL PROTECTED] -> localbus fixed up name for [EMAIL PROTECTED],0 -> flash <- unflatten_device_tree() Found initrd at 0xdfcb7000:0xdff3f000 console [udbg0] enabled setup_arch: bootmem mvblm7_setup_arch() Unable to handle kernel paging request for data at address 0x Faulting instruction address: 0xc0012748 Oops: Kernel access of bad area, sig: 11 [#1] PREEMPT mvBlueLYNX-M7 Modules linked in: NIP: c0012748 LR: c0140c10 CTR: REGS: c01f9e40 TRAP: 0300 Not tainted (2.6.25-rc8-01197-g1de15bb-dirty) MSR: 1032 CR: 22008048 XER: 2000 DAR: , DSISR: 2000 TASK = c01e4510[0] 'swapper' THREAD: c01f8000 GPR00: c0140c84 c01f9ef0 c01e4510 c0197a7f c01f9edc GPR08: c01f15e4 0003 c0600b84 004d 22002048 ffdf 1fffd000 GPR16: ffdf 7fdf 1fff8974 1ff426f8 0004 00288000 GPR24: 0002 5f0f c01993e4 c01f9f28 c0197a80 c01f8000 d9e4 Call Trace: [c01f9ef0] [c001c190] (unreliable) [c01f9f10] [c0140c84] [c01f9f20] [c0140ccc] [c01f9f40] [c014145c] [c01f9f60] [c0014014] [c01f9fa0] [c01d1a40] [c01f9fb0] [c01ce64c] [c01f9fc0] [c01c55ac] [c01f9ff0] [3438] Instruction dump: 3884 8c050001 2c00 4082fff8 38a5 8c040001 2c00 9c050001 4082fff4 4e800020 38a3 3884 <8c650001> 2c83 8c040001 7c601851 ---[ end trace 8640abe69a316dee ]--- Kernel panic - not syncing: Attempted to kill the idle task! Rebooting in 180 seconds.. Please let me know if you need more information. regards, Andre MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweile
Re: MPC8343 - "unable to handle paging request @ 0"
On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote: > Kernel starts and crashes with "unable to handle kernel paging request @ > ". > > After turning debug on in some files I can see that the initrd memory > gets reserved and the dtb is parsed correctly. > PCI memory/io spaces are set up fine. > > At first I thought this is a problem with the device tree since the call > trace always points to "of_"-functions and "strcmp". Could you provide this call trace? -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
MPC8343 - "unable to handle paging request @ 0"
Kim, sorry for the general questions - but I'm running out of ideas. We never ever had that many problems getting a PowerPC running during the past 10 years. I've cross-checked the hardware and design with Freescale FAE. Everything looks fine and is approved. We're running latest u-boot v1.3.2 and kernel 2.6.25-rc8 from Denx. A MPC5200B System is up and running fine with this scenario, so hopefully there are no basic problems. The MPC8343B (rev.3.1) is working pretty fine with u-boot including mtest. Only problem is a the TSECs not working with our RGMII phy - but this can wait. I've set up a dts based on the MPC834x_mds and removed the 2nd PCI bus and local bus stuff. Kernel has been build with a new platform "MVBLM7" which is the name of our board - nothing special so far. u-boot fills out all parameters (clocks, mem, initrd @ chosen, ...) correctly and the kernel is started exactly the same way as the MPC5200B system using "bootm kernel_add initrd_addr dtb_addr". Kernel starts and crashes with "unable to handle kernel paging request @ ". After turning debug on in some files I can see that the initrd memory gets reserved and the dtb is parsed correctly. PCI memory/io spaces are set up fine. At first I thought this is a problem with the device tree since the call trace always points to "of_"-functions and "strcmp". So I removed nearly everything from the kernel and dts including PCI, net, USB and peripherals leaving only a minimum (cpu, mem, soc-node with ipic and serial). Unfortunately the error is still the same ! I wonder if there are some basic issues regarding MPC8343 or specialities from the Freescale boards not being present on our board. Major difference is the CPU (MPC8343B), 512MB RAM (using 2 BATs of course) and nothing else on the local bus besides the Nor-Flash. Of course the MPC8343 has only a single PCI-32 and only one USB. Do you have any hints on this ? Do you suggest to wait for the 2.6.25 release ? Do you know of any MPC8343 based boards already up and running ? regards, André Schwarz MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler - Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
