Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

[Absolut Hunter]

Anybody,

I ran into a peculiar issue, though it could be user error. 

I am using U-boot to configure up the SDRAM and SRAM in our system before we
launch Linux. We have 32 Mb of SDRAM and 2 MB of SRAM in the system. 

If I leave the SRAM mapped at higher addresses 0x10000000 and SDRAM at
0x00000000, like U-boot defaults to Linux works great. However, my goal is
to map SRAM <8ns speeds> down to the address 0x00000000, to map the vector
table, so I can achieve a very fast interrupt response time.

I hacked U-boot a little bit to remap these addresses, after all the init
code was finished. U-boot relocates itself to higher memory, i.e. the last
2MB's of SDRAM and all is well within U-boot. I ran a 14 hour test on the
memory area to proof it. Now we have 0x02200000 <34M> memory size being
reported to Linux, in the bd->memsize. However, now Linux crashes randomly
all over the place, mostly sig11's task: swapper. I know this is not an
issue with SDRAM stability, and I can't imagine SRAM having problems seeing
as its 8ns capable and we're running at 15ns at the moment (66mhz).

Linux reports BAT mappings as BAT2=32Mb, BAT3=2MB when all 34 Megs are
presented via U-boot. 

Does anyone have any idea what would cause this instability? Physically all
memory seems to be great if used by itself. I know very little about how
Linux manages its pages, BATS, TBLs, etc... Are the limits on odd memory
sizes? Or certain configurations that it expects to see?

Thanks in advance.

-Russell McGuire

Re: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

[Michael Richardson]

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Absolut" == Absolut Hunter <absoluthunter@comcast.net> writes:
    Absolut> If I leave the SRAM mapped at higher addresses 0x10000000
    Absolut> and SDRAM at 0x00000000, like U-boot defaults to Linux
    Absolut> works great. However, my goal is to map SRAM <8ns speeds>
    Absolut> down to the address 0x00000000, to map the vector table, so
    Absolut> I can achieve a very fast interrupt response time.

  Are you mapping the SRAM *OVER* the lower 2MB of address space?

  If so, then you won't have 34Mb of ram, you'll have 32Mb, and Linux
may well be running off the end under stress.

  My memory is that you can move the vector table to another address.
Wouldn't that be easier?

- -- 
] Michael Richardson          Xelerance Corporation, Ottawa, ON |  firewalls  [
] mcr @ xelerance.com           Now doing IPsec training, see   |net architect[
] http://www.sandelman.ca/mcr/    www.xelerance.com/training/   |device driver[
]                    I'm a dad: http://www.sandelman.ca/lrmr/                 [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQtJ7yoqHRg3pndX9AQF+eQQA0QBhaZAjq3vDQm8glqV0j+jmzO9+7U0m
aZvOt5FsXu2mv3lS/2FySIQf3UuRcl0lIR5zaNfyn+I11K0YlfZvXgY97U2TMcmu
1K5sod0j3DpaIrK/a+VyWa+tQFe9zoPktazinVoQm4+geNRlTZf9P5XyYwXE7knn
+TOTFRzLq7c=
=iPOS
-----END PGP SIGNATURE-----

Re: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

[Mark Chambers]

> I am using U-boot to configure up the SDRAM and SRAM in our system before
we
> launch Linux. We have 32 Mb of SDRAM and 2 MB of SRAM in the system.
>
> If I leave the SRAM mapped at higher addresses 0x10000000 and SDRAM at
> 0x00000000, like U-boot defaults to Linux works great. However, my goal is
> to map SRAM <8ns speeds> down to the address 0x00000000, to map the vector
> table, so I can achieve a very fast interrupt response time.
>

Your core is probably running at about 400MHz, so 66MHz SRAM is still slow.
This is what cache is for.  Maybe you should look into locking interrupt
code in
cache.  Probably, however, you will find that messing with the overall
optimizations
of the kernel will be a net slowdown.

Mark Chambers

Re: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

[Wolfgang Denk]

In message <20050711134713.D767067C13@ozlabs.org> you wrote:
> 
> If I leave the SRAM mapped at higher addresses 0x10000000 and SDRAM at
> 0x00000000, like U-boot defaults to Linux works great. However, my goal is
> to map SRAM <8ns speeds> down to the address 0x00000000, to map the vector
> table, so I can achieve a very fast interrupt response time.

How fast is your bus? 8 ns is not exactly very fast.

> I hacked U-boot a little bit to remap these addresses, after all the init

Hacked? No hack at all should have been necessary. This  is  standard
configuration stuff.

> reported to Linux, in the bd->memsize. However, now Linux crashes randomly
> all over the place, mostly sig11's task: swapper. I know this is not an

SO one or your memory banks does not work reliably.

> issue with SDRAM stability, and I can't imagine SRAM having problems seeing
> as its 8ns capable and we're running at 15ns at the moment (66mhz).

And what about the state of your hardware? Did you check the signals,
especially when the CPU is stressing the bus in burst mode?


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Let the programmers be many and the managers few -- then all will  be
productive.               -- Geoffrey James, "The Tao of Programming"

About 2.6.14 on AMCC Yosemite board

[KylongMu]

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

Hi, Denk
	I've got my Yosemite board today, it's shows very good by default
test.
I downloaded the 2.6.14 according the repository from your website by
cogito.
with default configure, I boot with the uImage, but the system halt,
attachment
is the message.
	I don't know what happen with it, pls help me.

Thanks a lot!

Kylong Mu

[-- Attachment #2: make_command.txt --]
[-- Type: text/plain, Size: 76 bytes --]

  924  make yosemite_defconfig
  925  make menuconfig
  926  make uImage

[-- Attachment #3: bootmessage.txt --]
[-- Type: text/plain, Size: 6122 bytes --]


U-Boot 1.1.3 (Sep  7 2005 - 09:03:02)

IBM PowerPC 440 EP Rev. B
Board: AMCC YOSEMITE
        VCO: 1066 MHz
        CPU: 533 MHz
        PLB: 133 MHz
        OPB: 66 MHz
        PER: 66 MHz
        PCI: 66 MHz
I2C:   ready
DRAM:  256 MB
FLASH: 32 MB
PCI:   Bus Dev VenId DevId Class Int
        00  0c  105a  4d68  0180  0e
In:    serial
Out:   serial
Err:   serial
Net:   ppc_440x_eth0, ppc_440x_eth1
Hit any key to stop autoboot:  0
=> tftp 0x4000000 uImage
Waiting for PHY auto negotiation to complete.. done
Using ppc_440x_eth0 device
TFTP from server 192.168.0.93; our IP address is 192.168.0.66
Filename 'uImage'.
Load address: 0x4000000
Loading: #################################################################
         #################################################################
         #################################################################
         #############################################
done
Bytes transferred = 1225628 (12b39c hex)
=> bootm 0x4000000 fed40000
## Booting image at 04000000 ...
   Image Name:   Linux-2.6.14
   Created:      2005-11-02  13:20:24 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1225564 Bytes =  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at fed40000 ...
   Image Name:   Yosemite Ramdisk
   Created:      2005-08-30   2:13:49 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    17770706 Bytes = 16.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 0ee9b000, end 0ff8d8d2 ... OK
Linux version 2.6.14 (root@dxp) (gcc �.� 3.3.3 (DENX ELDK 3.1.1 3.3.3-10)) #2 Wed Nov 2 21:20:16 CST 2005
AMCC PowerPC 440EP Yosemite Platform
Built 1 zonelists
Kernel command line: ramdisk=49152 root=/dev/ram ip=192.168.1.62:::::eth0:off
PID hash table entries: 2048 (order: 11, 32768 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 239360k available (1876k kernel code, 708k data, 140k init, 0k highmem)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
softlockup thread 0 started up.
Freeing initrd memory: 17354k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
usbcore: registered new driver usbfs
usbcore: registered new driver hub
SCSI subsystem initialized
usbmon: debugfs is not available
ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000
usb usb1: Product: USB Host Controller
usb usb1: Manufacturer: Linux 2.6.14 ohci_hcd
usb usb1: SerialNumber: PPC-SOC USB
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
pegasus: v0.6.12 (2005/01/13), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new driver pegasus
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 49152K size 1024 blocksize
PPC 4xx OCP EMAC driver, version 3.53
mal0: initialized, 4 TX channels, 2 RX channels
zmii0: bridge in RMII mode
eth0: emac0, MAC 00:10:ec:00:8f:aa
eth0: found Generic MII PHY (0x01)
eth1: emac1, MAC 00:10:ec:80:8f:aa
eth1: found Generic MII PHY (0x03)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
yosemite: flash mapping: 4000000 at fc000000
Data machine check in kernel mode.
PLB0: BEAR=0x0000000000000000 ACR=  0x00000000 BESR= 0xfdffffff
POB0: BEAR=0xc27e319400000001 BESR0=0x00000000 BESR1=0x00000000
OPB0: BEAR=0x0000000000000151 BSTAT=0x00000000
Oops: machine check, sig: 7 [#1]
NIP: 00000000 LR: C015D7C8 SP: C0521E30 REGS: c0291f50 TRAP: 0202    Not tainted
MSR: 00000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00
TASK = cee98b10[1] 'swapper' THREAD: c0520000
Last syscall: 120
GPR00: 00000002 C0521E30 CEE98B10 C0242F18 00000000 00000000 C0521EE0 CEF0C3F8
GPR08: 000000FF 00000004 00000002 00000001 42254128 C0020028 0FFE6E00 00000001
GPR16: FFFFFFFF 007FFF00 0FFE1AD4 00000000 00000003 007FFE70 00800000 00000001
GPR24: 00000000 C0521EE0 C0242DB0 00000000 C0242F18 C0521EE0 00000000 C0242F18
NIP [00000000] 0x0
LR [c015d7c8] genprobe_new_chip+0xa8/0xc0
Call trace:
 [c015d7c8] genprobe_new_chip+0xa8/0xc0
 [c015d508] genprobe_ident_chips+0x3c/0x254
 [c015d444] mtd_do_chip_probe+0x18/0xa0
 [c01587b8] cfi_probe+0x18/0x28
 [c01570c4] do_map_probe+0x40/0xe0
 [c028594c] init_yosemite_flash+0x90/0xec
 [c026c728] do_initcalls+0x54/0xfc
 [c000137c] init+0x2c/0x13c
 [c0004630] kernel_thread+0x48/0x64
Data machine check in kernel mode.
PLB0: BEAR=0x0000000000000000 ACR=  0x00000000 BESR= 0xfdffffff
POB0: BEAR=0xc27e319400000001 BESR0=0x00000000 BESR1=0x00000000
OPB0: BEAR=0x0000000000000151 BSTAT=0x00000000
Oops: machine check, sig: 7 [#2]
NIP: 00000000 LR: C000229C SP: C0291E60 REGS: c0291f50 TRAP: 0202    Not tainted
MSR: 00000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00
TASK = cee98b10[1] 'swapper' THREAD: c0520000
Last syscall: 120
GPR00: 08000000 C0291E60 CEE98B10 C0291E70 000015D7 FFFFFFFF C0230000 C0290000
GPR08: C0230000 C000229C 00021002 C00036D0 CEE98CD8 C0020028 0FFE6E00 00000001
GPR16: FFFFFFFF 007FFF00 0FFE1AD4 00000000 00000003 007FFE70 00800000 00000001
GPR24: 00000000 C0521EE0 C0242DB0 00000000 C0242F18 C0521EE0 C0291F50 00000007
NIP [00000000] 0x0
LR [c000229c] ret_from_except+0x0/0x18
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 180 seconds..

Re: About 2.6.14 on AMCC Yosemite board

[Wolfgang Denk]

Dear Kylong Mu,

in message <20051102135009.27C46102A@smtp.263.net> you wrote:
> 
> 	I've got my Yosemite board today, it's shows very good by default test.
> I downloaded the 2.6.14 according the repository from your website by cogito.
> with default configure, I boot with the uImage, but the system halt, attachment
> is the message.
> 	I don't know what happen with it, pls help me.
...
> DRAM:  256 MB
> FLASH: 32 MB
---------^^^^^

That's the problem. The board we got from AMCC for the port  and  for
testing  all had 64 MB flash, and there was no information that other
configurations are available too. The MTD mapping driver  ist  a  bit
braindead at the moment and assumes 64 MB. This fails on your board.

The quick and dirty fix is to edit "drivers/mtd/maps/yosemite.c" and
replace the lines:

    ...
     31
     32 #define WINDOW_ADDR 0xfc000000
     33 #define WINDOW_SIZE 0x04000000
     34
    ...

with:

	#define WINDOW_ADDR 0xFE000000
	#define WINDOW_SIZE 0x02000000

We will implement a better fix (automatically adjust values according
to the values pased by the boot loader) later today / early tomorrow.

Sorry for the inconvenience.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If you want strict real-time behavior, run in the real  time  schedu-
ling class.  But there are no seatbelts or airbags;  main(){for(;;);}
can hard hang your system.                          -- Bart Smaalders

Today's 2.6.14 can't finish build with yosemite-defconfig

[KylongMu]

Dear Denk
	After cg-update today's kernel repository, I test with these steps:
Make yosemite-defconfig
Make uImage

But the build stops with some errors, last cg-update (5 days ago) is ok.

Cordially,

Kylong Mu

11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[KylongMu]

[-- Attachment #1: Type: text/plain, Size: 204 bytes --]

Dear Denk:
	With today's update, I can make the kernel by Yosemite_defconfig,
but
When boot my board with this new kernel, it halt at boot time, the
attachment
Is the boot message.

Cordially,
Kylong Mu


[-- Attachment #2: bootmessage.txt --]
[-- Type: text/plain, Size: 5911 bytes --]

U-Boot 1.1.3 (Sep  7 2005 - 09:03:02)

IBM PowerPC 440 EP Rev. B
Board: AMCC YOSEMITE
        VCO: 1066 MHz
        CPU: 533 MHz
        PLB: 133 MHz
        OPB: 66 MHz
        PER: 66 MHz
        PCI: 66 MHz
I2C:   ready
DRAM:  256 MB
FLASH: 32 MB
PCI:   Bus Dev VenId DevId Class Int
In:    serial
Out:   serial
Err:   serial
Net:   ppc_440x_eth0, ppc_440x_eth1
Hit any key to stop autoboot:  0
=> tftp 0x400000 uImage
Waiting for PHY auto negotiation to complete.. done
Using ppc_440x_eth0 device
TFTP from server 192.168.0.93; our IP address is 192.168.0.66
Filename 'uImage'.
Load address: 0x400000
Loading: #################################################################
         #################################################################
         #################################################################
         ##########################################
done
Bytes transferred = 1212626 (1280d2 hex)
=> bootm 0x400000 0xfed40000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.14
   Created:      2005-11-11   1:51:20 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1212562 Bytes =  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at fed40000 ...
   Image Name:   Yosemite Ramdisk
   Created:      2005-08-30   2:13:49 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    17770706 Bytes = 16.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 0ee9b000, end 0ff8d8d2 ... OK
Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Fri Nov 11 09:51:04 CST 2005
AMCC PowerPC 440EP Yosemite Platform
Built 1 zonelists
Kernel command line: ramdisk=49152 root=/dev/ram ip=192.168.1.62:::::eth0:off
PID hash table entries: 2048 (order: 11, 32768 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 239488k available (1852k kernel code, 604k data, 136k init, 0k highmem)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
softlockup thread 0 started up.
Freeing initrd memory: 17354k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
usbcore: registered new driver usbfs
usbcore: registered new driver hub
SCSI subsystem initialized
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
usbmon: debugfs is not available
ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000
usb usb1: Product: USB Host Controller
usb usb1: Manufacturer: Linux 2.6.14 ohci_hcd
usb usb1: SerialNumber: PPC-SOC USB
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
pegasus: v0.6.12 (2005/01/13), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new driver pegasus
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 49152K size 1024 blocksize
PPC 4xx OCP EMAC driver, version 3.53
mal0: initialized, 4 TX channels, 2 RX channels
zmii0: bridge in RMII mode
eth0: emac0, MAC 00:10:ec:00:8f:aa
eth0: found Generic MII PHY (0x01)
eth1: emac1, MAC 00:10:ec:80:8f:aa
eth1: found Generic MII PHY (0x03)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Data machine check in kernel mode.
PLB0: BEAR=0x0000000000000000 ACR=  0x00000000 BESR= 0xfdfff7ff
POB0: BEAR=0xc27e3194ffffffff BESR0=0x00000000 BESR1=0x00000000
OPB0: BEAR=0x0000000000000151 BSTAT=0x00000000
Oops: machine check, sig: 7 [#1]
NIP: 00000000 LR: C0157E9C SP: CFFA1EE0 REGS: c0270f50 TRAP: 0202    Not tainted
MSR: 00000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00
TASK = cee98b10[1] 'swapper' THREAD: cffa0000
Last syscall: 120
GPR00: 00000002 CFFA1EE0 CEE98B10 C022673C 00000000 00000000 CFFA1F18 00000000
GPR08: 00000002 00000002 00000002 00000001 000F1FFF 60000428 0FFE6E00 00000001
GPR16: FFFFFFFF 007FFF00 0FFE1AD4 00000000 00000003 007FFE70 00800000 00000001
GPR24: C01D0000 C01D0000 C0270000 00000000 C022673C CFFA1F18 00000000 C022673C
NIP [00000000] 0x0
LR [c0157e9c] mtd_do_chip_probe+0xdc/0x334
Call trace:
 [c0157e9c] mtd_do_chip_probe+0xdc/0x334
 [c0152214] cfi_probe+0x18/0x28
 [c0152160] do_map_probe+0x40/0xdc
 [c0265568] init_yosemite_flash+0xb4/0x110
 [c00013ac] init+0xb4/0x254
 [c00046c0] kernel_thread+0x48/0x64
Data machine check in kernel mode.
PLB0: BEAR=0x0000000000000000 ACR=  0x00000000 BESR= 0xfdfff7ff
POB0: BEAR=0xc27e3194ffffffff BESR0=0x00000000 BESR1=0x00000000
OPB0: BEAR=0x0000000000000151 BSTAT=0x00000000
Oops: machine check, sig: 7 [#2]
NIP: 00000000 LR: C000235C SP: C0270E70 REGS: c0270f50 TRAP: 0202    Not tainted
MSR: 00000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00
TASK = cee98b10[1] 'swapper' THREAD: cffa0000
Last syscall: 120
GPR00: 08000000 C0270E70 CEE98B10 C0270E80 00001529 FFFFFFFF C0270000 00004000
GPR08: C0270000 C000235C 00021002 C00039E8 CEE98CD8 60000428 0FFE6E00 00000001
GPR16: FFFFFFFF 007FFF00 0FFE1AD4 00000000 00000003 007FFE70 00800000 00000001
GPR24: C01D0000 C01D0000 C0270000 00000000 C022673C CFFA1F18 00000007 C0270F50
NIP [00000000] 0x0
LR [c000235c] ret_from_except+0x0/0x18
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 180 seconds..

Re: 11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[Wolfgang Denk]

In message <20051111020420.9644C1073@smtp.263.net> you wrote:
> 
> 	With today's update, I can make the kernel by Yosemite_defconfig,
> but
> When boot my board with this new kernel, it halt at boot time, the
> attachment
> Is the boot message.

What you show is NOT the current code.

> U-Boot 1.1.3 (Sep  7 2005 - 09:03:02)

Please update U-Boot as well. You need this commit included:

commit f190c11b1f22ff766e046588e5a7bb55f28ae305
tree 1c41a7beffe8a293174dcb7c28b394349204a047
parent 4d03a21f2329bb13a9661a23742ac0b77a7a76d5
author Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100
committer Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100

    Adjust bd->bi_flashstart on Yellowstone & Yosemite to correct size
    Patch by Stefan Roese, 05 Nov 2005

I recommend to use the top-of-tree from the CVS or GIT repositories.

> Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Fri Nov 11
> 09:51:04 CST 2005

This is not the current code base. You should  use  top-of-tree  from
GIT repository (commit ff1df84b3c3154ffdb646941e1c70d17554e3042); the
kernel will display something like this:

Linux version 2.6.14-gff1df84b ...



Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
                  Nail here --X-- for new monitor.

Re: 11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[KylongMu]

[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]

Dear Denk:

 

>What you show is NOT the current code.

     By update with the most recent code, I did new test, and get

Different error message, that I can't solve it, pls check the attachment. 

 

> U-Boot 1.1.3 (Sep  7 2005 - 09:03:02)

 

>Please update U-Boot as well. You need this commit included:

 

>commit f190c11b1f22ff766e046588e5a7bb55f28ae305

>tree 1c41a7beffe8a293174dcb7c28b394349204a047

>parent 4d03a21f2329bb13a9661a23742ac0b77a7a76d5

>author Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100

>committer Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100

 

>    Adjust bd->bi_flashstart on Yellowstone & Yosemite to correct size

>    Patch by Stefan Roese, 05 Nov 2005

 

>I recommend to use the top-of-tree from the CVS or GIT repositories.

 

> Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Fri Nov 11

> 09:51:04 CST 2005

 

>This is not the current code base. You should  use  top-of-tree  from

>GIT repository (commit ff1df84b3c3154ffdb646941e1c70d17554e3042); the

>kernel will display something like this:

 

>Linux version 2.6.14-gff1df84b ...

     I update my source code by "cg-update" directly, after many message and
file download it shows "full merged",

I think it is work. But the version only is 2.6.14. 

 

Thanks a lot!

 

Kylong Mu


[-- Attachment #1.2: Type: text/html, Size: 11347 bytes --]

[-- Attachment #2: bootmessage.txt --]
[-- Type: text/plain, Size: 8284 bytes --]

[root@dxp filesystem]# kermit -c
Connecting to /dev/ttyS0, speed 9600
 Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------


U-Boot 1.1.4 (Nov 11 2005 - 19:35:30)

AMCC PowerPC 440EP Rev. B
Board: Yosemite - AMCC PPC440EP Evaluation Board
        VCO: 1066 MHz
        CPU: 533 MHz
        PLB: 133 MHz
        OPB: 66 MHz
        EPB: 66 MHz
        PCI: 66 MHz
I2C:   ready
DRAM:  256 MB
FLASH: 64 MB
PCI:   Bus Dev VenId DevId Class Int
In:    serial
Out:   serial
Err:   serial
Net:   ppc_4xx_eth0, ppc_4xx_eth1

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
=>
=> tftp 400000 uImage
ENET Speed is 100 Mbps - FULL duplex connection
Using ppc_4xx_eth0 device
TFTP from server 192.168.0.93; our IP address is 192.168.0.66
Filename 'uImage'.
Load address: 0x400000
Loading: #################################################################
         #################################################################
         #################################################################
         ##########################################
done
Bytes transferred = 1212624 (1280d0 hex)
=> tftp 4000000 ramdisk.img
Using ppc_4xx_eth0 device
TFTP from server 192.168.0.93; our IP address is 192.168.0.66
Filename 'ramdisk.img'.
Load address: 0x4000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############################################
done
Bytes transferred = 8547050 (826aea hex)
=> bootm 400000 4000000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.14
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1212560 Bytes =  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 04000000 ...
   Image Name:   Yosemite Ramdisk
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    8546986 Bytes =  8.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 0f713000, end 0ff39aaa ... OK
Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Sat Nov 12 23:29:30 CST 2005
AMCC PowerPC 440EP Yosemite Platform
Built 1 zonelists
Kernel command line:
PID hash table entries: 2048 (order: 11, 32768 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 248576k available (1852k kernel code, 604k data, 136k init, 0k highmem)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
softlockup thread 0 started up.
Freeing initrd memory: 8346k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
usbcore: registered new driver usbfs
usbcore: registered new driver hub
SCSI subsystem initialized
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
usbmon: debugfs is not available
ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000
usb usb1: Product: USB Host Controller
usb usb1: Manufacturer: Linux 2.6.14 ohci_hcd
usb usb1: SerialNumber: PPC-SOC USB
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
pegasus: v0.6.12 (2005/01/13), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new driver pegasus
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
PPC 4xx OCP EMAC driver, version 3.53
mal0: initialized, 4 TX channels, 2 RX channels
zmii0: bridge in RMII mode
eth0: emac0, MAC 00:10:ec:00:87:40
eth0: found Generic MII PHY (0x01)
eth1: emac1, MAC 00:10:ec:00:87:47
eth1: found Generic MII PHY (0x03)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
AMCC440-flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
AMCC440-flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Creating 5 MTD partitions on "AMCC440-flash":
0x00000000-0x00180000 : "kernel"
0x00180000-0x00400000 : "root"
0x00400000-0x03f40000 : "user"
0x03f40000-0x03f80000 : "env"
0x03f80000-0x04000000 : "u-boot"
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
RAMDISK: incomplete write (-28 != 32768) 4194304
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 136k init
attempt to access beyond end of device
ram0: rw=0, want=32776, limit=8192
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=4001, block=16387
Warning: unable to open an initial console.
attempt to access beyond end of device
ram0: rw=0, want=49538, limit=8192
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=6003, block=24768
attempt to access beyond end of device
ram0: rw=0, want=65544, limit=8192
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=8001, block=32771
attempt to access beyond end of device
ram0: rw=0, want=16770, limit=8192
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=2001, block=8384
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
 <0>Rebooting in 180 seconds.. 

Problem solved: 11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[KylongMu]

[-- Attachment #1: Type: text/plain, Size: 3156 bytes --]

Dear Denk:

      The problem is solved After I check the document at:

http://www.denx.de/wiki/view/DULG/RamdiskGreaterThan4MBCausesProblems

It wrote:

14.3.14. Ramdisk Greater than 4 MB Causes Problems

Question: 

I built a ramdisk image which is bigger than 4 MB. I run into problems when
I try to boot Linux with this image, while other (smaller) ramdisk images
work fine. 

Answer: 

The Linux kernel has a default maximum ramdisk size of 4096 kB. To boot with
a bigger ramdisk image, you must raise this value. There are two methods: 

*   Dynamical adjustment using boot arguments:
You can pass a boot argument ramdisk_size=<size-in-kB> to the Linux kernel
to overwrite the configured maximum. Note that this argument needs to be
before any root argument. A flexible way to to this is using U-Boot
environment variables. For instance, to boot with a ramdisk image of 6 MB
(6144 kB), you can define: 

=> setenv rd_size 6144

=> setenv bootargs ... ramdisk_size=\$(rd_size) ...

=> saveenv

       

If you later find out that you need an even bigger ramdisk image, or that a
smaller one is sufficient, all that needs changing is the value of the
"rd_size" environment variable.

With the first way I modify the boorargs, and all work OK

*    

*	Increasing the Linux kernel default value:
When configuring your Linux kernel, adjust the value of the
CONFIG_BLK_DEV_RAM_SIZE parameter so that it contains a number equal or
larger than your ramdisk (in kB). (In the 2.4 kernel series, you'll find
this setting under the "Block devices" menu choice while, in the 2.6 series,
it will be under "Device drivers" -> "Block devices".) 

With the second way I only modify the CONFIG_BLK_DEV_RAM_SIZE, but when it
boot, it's shows this problem still:

Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

 

Last file I wrote:

 

>What you show is NOT the current code.

     By update with the most recent code, I did new test, and get

Different error message, that I can't solve it, pls check the attachment. 

 

> U-Boot 1.1.3 (Sep  7 2005 - 09:03:02)

 

>Please update U-Boot as well. You need this commit included:

 

>commit f190c11b1f22ff766e046588e5a7bb55f28ae305

>tree 1c41a7beffe8a293174dcb7c28b394349204a047

>parent 4d03a21f2329bb13a9661a23742ac0b77a7a76d5

>author Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100

>committer Stefan Roese <sr@denx.de> Sat, 05 Nov 2005 15:50:16 +0100

 

>    Adjust bd->bi_flashstart on Yellowstone & Yosemite to correct size

>    Patch by Stefan Roese, 05 Nov 2005

 

>I recommend to use the top-of-tree from the CVS or GIT repositories.

 

> Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Fri Nov 11

> 09:51:04 CST 2005

 

>This is not the current code base. You should  use  top-of-tree  from

>GIT repository (commit ff1df84b3c3154ffdb646941e1c70d17554e3042); the

>kernel will display something like this:

 

>Linux version 2.6.14-gff1df84b ...

     I update my source code by "cg-update" directly, after many message and
file download it shows "full merged",

I think it is work. But the version only is 2.6.14. 

 

Thanks a lot!

 

Kylong Mu


[-- Attachment #2: Type: text/html, Size: 21079 bytes --]

Re: Problem solved: 11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[Wolfgang Denk]

In message <20051112180127.10C03CEA@smtp.263.net> you wrote:
> 
>       The problem is solved After I check the document at:
> http://www.denx.de/wiki/view/DULG/RamdiskGreaterThan4MBCausesProblems

Yes, reading the FAQ has always been an excellent idea. But there was
no need to quote the text here in full.

> Last file I wrote:
...
>      I update my source code by "cg-update" directly, after many message and
> file download it shows "full merged",
> 
> I think it is work. But the version only is 2.6.14. 

It ain't the current version.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Two wrongs don't make a right, but three rights make a left.

Re: 11-11-05 2.6.14 on AMCC Yosemite board(boot error)

[Wolfgang Denk]

In message <20051112164751.CA6C6DBB@smtp.263.net> you wrote:
> 
> >What you show is NOT the current code.
> 
>      By update with the most recent code, I did new test, and get
> Different error message, that I can't solve it, pls check the attachment. 

...
> => tftp 4000000 ramdisk.img
...
> Bytes transferred = 8547050 (826aea hex)

That's a ramdisk image of more than 8 MB ... 

> ## Booting image at 00400000 ...
>    Image Name:   Linux-2.6.14
...
> Linux version 2.6.14 (root@dxp) (gcc version 4.0.0) #1 Sat Nov 12 23:29:30 CST 2005

And  this  is  not  the  current  code.  Current   code   is   commit
99a21389...,  and  a U-Boot image built from current code (like that
available at ftp://ftp.denx.de/pub/linux/images/amcc/yosemite/uImage)
will identify itself as "Image Name: Linux-2.6.14-g99a21389".


> Kernel command line:

And you don't pass *any* boot arguments to the kernel.

...
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

Because of not passing appropriate boot  arguments,  nor  configuring
the kernel correctly, your maximum ramdisk size is 4 MB = the default
value.

...
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (-28 != 32768) 4194304
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 136k init
> attempt to access beyond end of device
> ram0: rw=0, want=32776, limit=8192

And here you see the consequences.


>      I update my source code by "cg-update" directly, after many message and
> file download it shows "full merged",
> 
> I think it is work. But the version only is 2.6.14. 

I don't know what exactly you did, but the current code  on  our  GIT
server as of now shows:

-> cg-log
commit 99a21389c2b0e55f30b6cf6550cb492b87dbaa3b
tree 417c9550fff5763f30f67a1fa041386281339b71
parent ff1df84b3c3154ffdb646941e1c70d17554e3042
author Heiko Schocher <hs@pollux.(none)> Fri, 11 Nov 2005 12:47:32 +0100
committer Heiko Schocher <hs@pollux.(none)> Fri, 11 Nov 2005 12:47:32 +0100

    [PATCH]     ppc32: fix Kernel Panic for PM82x Board with gcc-4.0.0.
        
    Signed-off-by: Heiko Schocher <hs@denx.de>
...

If you don't see commit 99a21389..., then you don't have the current code.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Plan to throw one away.  You will anyway."
                              - Fred Brooks, "The Mythical Man Month"

Re: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?

[Dan Malek]

On Jul 11, 2005, at 6:38 AM, Absolut Hunter wrote:

> ..... However, my goal is
> to map SRAM <8ns speeds> down to the address 0x00000000, to map the 
> vector
> table, so I can achieve a very fast interrupt response time.

The things Linux does to cause interrupt latencies are going to ensure
you aren't going to see any differences to the "interrupt response 
time." :-)
 From a system perspective, you are going to be much better off using
your SRAM for CPM data buffering than for any general software use.

> Does anyone have any idea what would cause this instability?

Yeah, I can't find a way to actually map the memory as you have
described.  You actually have the SRAM and SDRAM multiply mapped
on top of one another, and depending upon which chip selects
are used and the values in their registers, you are selecting between
the two memories.  Several cases exist.  You are either mapping the
SRAM on top of the SDRAM, or vice versa.  You really have only 32M
of memory available, so any access to the "upper" 2M is wrapping
around to the lower memory.  Basically, you have a big mess ;-)

You need to map these memories to modulo their size, so to put
the 2M at low memory, you are going to have a hole up to a 32M
boundary before you can map the SDRAM.  It's possible to do
this, but not without some custom Linux modifications.

Thanks.

	-- Dan