Bug 266505 - Upgrading an i386 from 12.3p6 to 13.1-RELEASE it hangs after rebooting in the new kernel.
Summary: Upgrading an i386 from 12.3p6 to 13.1-RELEASE it hangs after rebooting in the...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: i386 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash, regression
Depends on:
Blocks:
 
Reported: 2022-09-19 17:27 UTC by Maurizio
Modified: 2024-01-29 22:50 UTC (History)
3 users (show)

See Also:

Attachments
dmesg output command of the working FreeBSD 12.3p6 (7.70 KB, text/plain)
2022-09-19 17:27 UTC, Maurizio 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maurizio 2022-09-19 17:27:53 UTC 
Created attachment 236691 [details]
dmesg output command of the working FreeBSD 12.3p6

Using the instructions at https://www.freebsd.org/releases/13.1R/installation/
following: Upgrading Using "FreeBSD Update",
the system hangs after rebooting in the new kernel.

The system boots, but at the console, repetitiously print the message:
"CPU0: local APIC error 0x4"

I can only switch off the PC.

I have tested booting the system with these two images:
FreeBSD-13.1-STABLE-i386-20220819-6ecf086d5a0-252127-mini-memstick.img
FreeBSD-14.0-CURRENT-i386-20220819-545db925c3d-257513-mini-memstick.img
but it hangs with the above message.


Attached the output of the dmesg command of the working FreeBSD 12.3p6
Comment 1 Andriy Gapon freebsd_committer freebsd_triage 2022-09-20 10:27:18 UTC 
Kostik did a lot of work on i386 architecture code, perhaps he may have an idea of what's going wrong.
Comment 2 Maurizio 2022-10-06 12:45:55 UTC 
I have tested the latest i386 snapshot. I have downloaded:

FreeBSD-14.0-CURRENT-i386-20220930-42dc8696df5-258315-bootonly.iso
FreeBSD-14.0-CURRENT-i386-20220930-42dc8696df5-258315-mini-memstick.img
and put on a CD and USB stick respectively.

On the Soltek Qbic with an AMD Athlon XP 2000+, the PC where I have found this error.
Booting from the USB stick it gives the previous error:
the system boots, but at the console, repetitiously print the message:
"CPU0: local APIC error 0x4"

For this error I have found a pair of running old PC.

A Fujitsu Siemens with Intel Pentium 4 CPU 3.06 GHz.
Booting from CD it panics after printing the message:
panic: ata_action: cbb 0x119431b0, func_code 0x901 should not be allocated from UMA zone
Should I open a new bug ?

An ASUS P4 with Intel Pentium 4 CPU 2.00 GHz.
It boots from the CD and can reach the login prompt.
Comment 3 Maurizio 2023-02-21 17:17:34 UTC 
On the Soltek Qbic with an AMD Athlon XP 2000+, booting an USB stick with FreeBSD-13.2-BETA2-i386-mini-memstick.img gives the same error: at the console, repetitiously print the message:
"CPU0: local APIC error 0x4"
Comment 4 Maurizio 2023-09-23 10:03:57 UTC 
On the Soltek Qbic with an AMD Athlon XP 2000+, booting an USB stick with FreeBSD-14.0-BETA3-i386-mini-memstick.img gives the same error: at the console, repetitiously print the message:
"CPU0: local APIC error 0x4"
Comment 5 Maurizio 2023-09-30 10:39:10 UTC 
On the Soltek Qbic with an AMD Athlon XP 2000+, booting an USB stick with
FreeBSD-14.0-BETA4-i386-mini-memstick.img
gives the same error: at the console, repetitiously print the message:
"CPU0: local APIC error 0x4"
Comment 6 freebsd-bug-report.e3f7c7f2e19a@inrobotico.com 2024-01-29 22:50:35 UTC 
I got over this problem by setting the following, either as parameter to the kernel (press Esc) while booting from memstick:

set hint.apic.0.disabled="1"

boot

And then, adding hint.acpi.0.disabled="1" to /boot/device.hints.