Re: [PATCH 4.14 00/14] 4.14.230-rc1 review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/10/21 2:21 AM, Naresh Kamboju wrote:
> On Sat, 10 Apr 2021 at 01:43, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
>>
>> On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 4.14.230 release.
>>> There are 14 patches in this series, all will be posted as a response
>>> to this one.  If anyone has any issues with these being applied, please
>>> let me know.
>>>
>>> Responses should be made by Sun, 11 Apr 2021 09:52:52 +0000.
>>> Anything received after that time might be too late.
>>>
>>
>> Build results:
>>         total: 168 pass: 168 fail: 0
>> Qemu test results:
>>         total: 408 pass: 408 fail: 0
>>
>> Tested-by: Guenter Roeck <linux@xxxxxxxxxxxx>
>>
>> Having said this, I did see a spurious crash, and I see an unusual warning.
>> I have seen the crash only once, but the warning happens with every boot.
>> These are likely not new but exposed because I added network interface
>> tests. This is all v4.14.y specific; I did not see it in other branches.
>> See below for the tracebacks. Maybe someone has seen it before.
> 
> I do not notice these warnings.
> Please share the testing environment / device / setup / network interfaces
> and Kernel configs and steps to reproduce.
> 
>  - Naresh
> 

Hi Naresh,

the configuration is based on aspeed_g5_defconfig (see attached configuration file)
and the following qemu command line (qemu v5.2):

qemu-system-arm -M romulus-bmc -kernel \
	arch/arm/boot/zImage -no-reboot \
	-initrd rootfs-armv5.cpio -nic user -nodefaults \
	--append "panic=-1 slub_debug=FZPUA rdinit=/sbin/init console=ttyS4,115200 earlycon=uart8250,mmio32,0x1e784000,115200n8" \
	-dtb arch/arm/boot/dts/aspeed-bmc-opp-romulus.dtb \
	-nographic -monitor null -serial stdio

It also happens with other bmc platforms using the same network interface, though
it is for some reason more prevalent on romulus-bmc.

The root file system is generated with buildroot. See buildone.sh / buildall.sh
in branch local-2021.02 of git@xxxxxxxxxx:groeck/buildroot.git. The warning happens
with almost every boot; the crash in maybe one of 5-10 boots. The test, if you want
to call it that, uses udhcpc to get an IP address and then

net_test_successful=0
ifconfig eth0 2>/dev/null | grep -q "inet addr:10.0.2.15"
if [ $? -eq 0 ]; then
    ping -q -c 1 -s 1000 -W 1 -I eth0 10.0.2.2 >/dev/null
    if [ $? -eq 0 ]; then
	telnet 10.0.2.2:22 </dev/null >/dev/null 2>dev/null
	if [ $? -eq 0 ]; then
	    net_test_successful=1
	fi
    fi
fi

See package/busybox/run.sh in the above repository/branch.

Guenter

Attachment: defconfig.gz
Description: application/gzip


[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux