kexec bug

[koberx]

Using kexec to restart the kernel, under the stress test, the kernel will be dead！

[koberx]

loongnix kexec dead.log

[FlyGoat]

That appears to be a device driver issue.
The device keeps emitting interrupt even after kernel driver shutdown it, and the newly booted kernel can't handle it as the new driver haven't registered at the time.

Btw: It's generally discouraged to use kexec reboot on Loongson.

[FlyGoat]

You cat

cat /proc/interrupts

To show IRQ number allocation and see witch device caused the issue.

[koberx]

You cat

cat /proc/interrupts

To show IRQ number allocation and see witch device caused the issue.

[koberx]

That appears to be a device driver issue.
The device keeps emitting interrupt even after kernel driver shutdown it, and the newly booted kernel can't handle it as the new driver haven't registered at the time.

Btw: It's generally discouraged to use kexec reboot on Loongson.

Btw: It's generally discouraged to use kexec reboot on Loongson. =====>> What causes this?

[FlyGoat]

That appears to be a device driver issue.
The device keeps emitting interrupt even after kernel driver shutdown it, and the newly booted kernel can't handle it as the new driver haven't registered at the time.
Btw: It's generally discouraged to use kexec reboot on Loongson.

Btw: It's generally discouraged to use kexec reboot on Loongson. =====>> What causes this?

Well because this function is rarely used by community users and thus we can't guarantee it's status.

[koberx]

That appears to be a device driver issue.
The device keeps emitting interrupt even after kernel driver shutdown it, and the newly booted kernel can't handle it as the new driver haven't registered at the time.
Btw: It's generally discouraged to use kexec reboot on Loongson.

Btw: It's generally discouraged to use kexec reboot on Loongson. =====>> What causes this?

Well because this function is rarely used by community users and thus we can't guarantee it's status.

Is there any way to turn off the interruption before kexec -e

[FlyGoat]

Is there any way to turn off the interruption before kexec -e

This is a device specified issue. You must figure out which device is emitting the interrupt and apply workaround in the device.
However, the spurious IRQ doesn't match any of the entry in /proc/interrupt, which is unreasonable.