soc_name for supermicrox11-bmc machine: ast2400-a1 or ast2500-a1 ?

soc_name for supermicrox11-bmc machine: ast2400-a1 or ast2500-a1 ?

[Guenter Roeck]

Hi,

I always wondered why I am having trouble running Linux on supermicrox11-bmc.
Building the kernel with aspeed_g4_defconfig results in its clock running
at ~20x the real clock speed, and kernels built with aspeed_g5_defconfig
do not boot at all.

I ended up spending some time on it last weekend and noticed that the SOC
is configured to ast2400-a1. However, the Supermicro documentation as well
as the devicetree file in the Linux kernel suggest that the SOC on the X11
board is an ast2500.

Indeed, it turns out that all my problems are gone if I change the SOC
to ast2500-a1 and use aspeed_g5_defconfig to build the Linux kernel.

Was there a reason to select ast2400-a1 for this machine, or is that
a bug ?

Thanks,
Guenter

Re: soc_name for supermicrox11-bmc machine: ast2400-a1 or ast2500-a1 ?

[Cédric Le Goater]

Hello Guenter

On 10/24/22 22:56, Guenter Roeck wrote:
> Hi,
> 
> I always wondered why I am having trouble running Linux on supermicrox11-bmc.
> Building the kernel with aspeed_g4_defconfig results in its clock running
> at ~20x the real clock speed, and kernels built with aspeed_g5_defconfig
> do not boot at all.
> 
> I ended up spending some time on it last weekend and noticed that the SOC
> is configured to ast2400-a1. However, the Supermicro documentation as well
> as the devicetree file in the Linux kernel suggest that the SOC on the X11
> board is an ast2500.

It is true that the Linux DT file includes an AST2500 SoC.

However, the QEMU BMC machine was added to support such boards :

    https://www.supermicro.com/en/products/motherboard/X11SSL-F

where it says ASPEED AST2400 BMC for IPMI and graphics. The firmware
detects the SoC as an AST2300, which means it doesn't have support for
the ast2400 ...

  
> Indeed, it turns out that all my problems are gone if I change the SOC
> to ast2500-a1 and use aspeed_g5_defconfig to build the Linux kernel.
> 
> Was there a reason to select ast2400-a1 for this machine, or is that
> a bug ?


May be there were multiple generations of the X11 mother boards.

It wouldn't be difficult adding a new supermicrox11-<something>-bmc
machine with an AST2500 SoC for your needs.

Thanks,

C.



U-Boot 2009.01 ( 4月 02 2019 - 15:29:02) ASPEED (v.0.21)

I2C:   ready
DRAM:  128 MB
Flash: 32 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
H/W:   AST2400 series chip
COM:   port1 and port2
PWM:   port[ABCDH]
Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 21400000 ...
    Image Name:   21400000
    Image Type:   ARM Linux Kernel Image (gzip compressed)
    Data Size:    1536645 Bytes =  1.5 MB
    Load Address: 40008000
    Entry Point:  40008000
    Verifying Checksum ... cramfs size 15032320
cramfs size 7315456
OK
    Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.28.9 (root@localhost) (gcc version 4.9.1 (crosstool-NG 1.20.0) ) #1 Wed Nov 20 18:20:38 CST 2019
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: ASPEED-AST2300
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 20066
Kernel command line: console=ttyS1,115200 root=/dev/mtdblock2 rootfstype=cramfs noinitrd rw mem=79M
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
console [ttyS1] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 79MB = 79MB total
Memory: 76736KB available (2848K code, 358K data, 112K init)
SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 1012.53 BogoMIPS (lpj=5062656)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 636 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (extended precision)
NTFS driver 2.1.29 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
fuse init (API version 7.10)
msgmni has been set to 149
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Non-volatile memory driver v1.2
ttyS0 at MMIO 0x1e783000 (irq = 9) is a ASPEED UART
ttyS1 at MMIO 0x1e784000 (irq = 10) is a ASPEED UART
brd: module loaded
loop: module loaded
nbd: registered device at major 43
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
BMC flash ID:0xc21920c2
  platform_flash: MX25L25635E (32768 Kbytes)
Creating 7 MTD partitions on "spi0.0":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00400000 : "nvram"
0x00400000-0x01400000 : "rootFS"
0x01400000-0x01700000 : "kernel"
0x01700000-0x01f40000 : "webpage"
0x00000000-0x01fc0000 : "all_part"
0x01fc0000-0x01fd0000 : "uboot_env"
mice: PS/2 mouse device common for all mice
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver

Re: soc_name for supermicrox11-bmc machine: ast2400-a1 or ast2500-a1 ?

[Guenter Roeck]

On 10/24/22 23:25, Cédric Le Goater wrote:
> Hello Guenter
> 
> On 10/24/22 22:56, Guenter Roeck wrote:
>> Hi,
>>
>> I always wondered why I am having trouble running Linux on supermicrox11-bmc.
>> Building the kernel with aspeed_g4_defconfig results in its clock running
>> at ~20x the real clock speed, and kernels built with aspeed_g5_defconfig
>> do not boot at all.
>>
>> I ended up spending some time on it last weekend and noticed that the SOC
>> is configured to ast2400-a1. However, the Supermicro documentation as well
>> as the devicetree file in the Linux kernel suggest that the SOC on the X11
>> board is an ast2500.
> 
> It is true that the Linux DT file includes an AST2500 SoC.
> 
> However, the QEMU BMC machine was added to support such boards :
> 
>     https://www.supermicro.com/en/products/motherboard/X11SSL-F
> 
> where it says ASPEED AST2400 BMC for IPMI and graphics. The firmware
> detects the SoC as an AST2300, which means it doesn't have support for
> the ast2400 ...
> 

Interesting. I was looking at

https://www.supermicro.com/en/solutions/management-software/bmc-resources

where X11 boards are associated with AST2500, and X10 boards with AST2400,
However, I do see that the motherboard list shows that it is indeed a mixed
bag.

> 
>> Indeed, it turns out that all my problems are gone if I change the SOC
>> to ast2500-a1 and use aspeed_g5_defconfig to build the Linux kernel.
>>
>> Was there a reason to select ast2400-a1 for this machine, or is that
>> a bug ?
> 
> 
> May be there were multiple generations of the X11 mother boards.
> 

Looks like it.

> It wouldn't be difficult adding a new supermicrox11-<something>-bmc
> machine with an AST2500 SoC for your needs.
> 

Makes sense.

Thanks,
Guenter

Re: soc_name for supermicrox11-bmc machine: ast2400-a1 or ast2500-a1 ?

[Cédric Le Goater]

On 10/25/22 15:37, Guenter Roeck wrote:
> On 10/24/22 23:25, Cédric Le Goater wrote:
>> Hello Guenter
>>
>> On 10/24/22 22:56, Guenter Roeck wrote:
>>> Hi,
>>>
>>> I always wondered why I am having trouble running Linux on supermicrox11-bmc.
>>> Building the kernel with aspeed_g4_defconfig results in its clock running
>>> at ~20x the real clock speed, and kernels built with aspeed_g5_defconfig
>>> do not boot at all.
>>>
>>> I ended up spending some time on it last weekend and noticed that the SOC
>>> is configured to ast2400-a1. However, the Supermicro documentation as well
>>> as the devicetree file in the Linux kernel suggest that the SOC on the X11
>>> board is an ast2500.
>>
>> It is true that the Linux DT file includes an AST2500 SoC.
>>
>> However, the QEMU BMC machine was added to support such boards :
>>
>>     https://www.supermicro.com/en/products/motherboard/X11SSL-F
>>
>> where it says ASPEED AST2400 BMC for IPMI and graphics. The firmware
>> detects the SoC as an AST2300, which means it doesn't have support for
>> the ast2400 ...
>>
> 
> Interesting. I was looking at
> 
> https://www.supermicro.com/en/solutions/management-software/bmc-resources
> 
> where X11 boards are associated with AST2500, and X10 boards with AST2400,
> However, I do see that the motherboard list shows that it is indeed a mixed
> bag.
> 
>>
>>> Indeed, it turns out that all my problems are gone if I change the SOC
>>> to ast2500-a1 and use aspeed_g5_defconfig to build the Linux kernel.
>>>
>>> Was there a reason to select ast2400-a1 for this machine, or is that
>>> a bug ?
>>
>>
>> May be there were multiple generations of the X11 mother boards.
>>
> 
> Looks like it.
> 
>> It wouldn't be difficult adding a new supermicrox11-<something>-bmc
>> machine with an AST2500 SoC for your needs.

I would suggest supermicrox11-spi-bmc to match the DT.

mac0 and mac1 are active. It would be nice to have some flash models
commonly attached to these boards. May be Ryan can tell.

Thanks,

C.