Error updating to 159

Getting Started with IPFire Updates Trouble
1

Good morning to all.

I have updated about 25 PC Engines - apu2 and in two computers I have problems in starting. The errors are as follows:

Mon Aug 23 09:22:02 CEST 2021                                          [  OK  ]
Starting Random Number Generator Daemon...                             [  OK  ]
Initializing kernel random number generator...                         [  OK  ]
Setting up Linux console...                                            [  OK  ]
Setting up Pakfire Package Manager...                                  [  OK  ]
Bringing up the loopback interface...                                  [  OK  ]
Setting hostname to bs.xxxxxx-xxxxxxxx.ex...                          [  OK  ]
INIT: Entering runlevel: 3                                             [  OK
Starting vnstatd...                                                    [  OK  ]
Starting kernel log daemon...                                          [  OK  ]
Starting system log daemon...                                          [  OK  ]
Saving Bootlog...                                                      [  OK  ]
Starting Unbound DNS Proxy...                                          [  OK  ]
Starting ACPI daemon...                                                [  OK  ]
Starting hostapd...
blue0: interface state UNINITIALIZED->COUNTRY_UPDATE                   [  OK  ]
Enabling S.M.A.R.T.: sda                                               [  OK  ]
Bringing up the green0 interface...
watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u8:2:95]

and in another:


Bringing up the loopback interface...                                  [  OK  ]
Setting hostname to bs.xxxxxxxxxx.ex...                               [  OK  ]
INIT: Entering runlevel: 3                                             [  OK
Starting vnstatd...                                                    [  OK  ]
Starting kernel log daemon...                                          [  OK  ]
Starting system log daemon...                                          [  OK  ]
Saving Bootlog...                                                      [  OK  ]
Starting Unbound DNS Proxy...                                          [  OK  ]
Starting ACPI daemon...                                                [  OK  ]
Starting hostapd...
blue0: interface state UNINITIALIZED->COUNTRY_UPDATE                   [  OK  ]
Enabling S.M.A.R.T.: sda                                               [  OK  ]
Bringing up the green0 interface...
Adding IPv4 address 172.26.0.1 to the green0 interface...              [  OK  ]
Bringing up the blue0 interface...
Adding IPv4 address 172.26.1.1 to the blue0 interface...               [  OK  ]
Bringing up the orange0 interface...
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u8:2:95]
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u8:2:95]

It stays there and doesnā€™t pass from there.

Any idea how to fix it?

Best regards.

2

It occurred to me to change the msata to another PCengines APU2 with another version of BIOS and it boots without problems.

Maybe itā€™s PCengines APU BIOS version problems.

Iā€™ll keep looking at it.

Greetings.

1 Like
3

I confirm that the problem is with BIOS 4.10.0.3. With this BIOS it gives this problem.

Solution: Update to the latest PCengines BIOS (apu2 v4.14.0.3)

Greetings.

3 Likes
4

Hi guys!!!.

I have detected in another BIOS version this problem in ā€œPC Engines ā€ apu2ā€ with core162:

imagen

The symptoms are the following:

  • Total loss of communications.
  • You find it on but with the SYS LED blinking constantly. The Tx and Rx leds are off.
  • Access through COM (Putty) and the image appears.
  • If the device restarts, everything starts to work correctly (until the next one).

BIOS versiĆ³n 4.13.04

SOLUTION:

Update the BIOS to the latest version (4.15.0.2, hoping that the latter does not cause problems).

Regards.

3 Likes