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

Re: "BUG: soft lockup" on A1200; was: Re: Updated installation images for Debian Ports 2019-04-20



Hi Finn,

On 18/06/19 11:51 AM, Finn Thain wrote:
On Tue, 18 Jun 2019, Michael Schmitz wrote:

On 15/06/19 11:15 AM, Finn Thain wrote:
On Wed, 12 Jun 2019, Szymon Bieganski wrote:

Here is the end of dmesg (full log in attachment) when kernel stalls,
just as before:

------------------------

[  122.430000] This architecture does not have kernel memory protection.
[  122.440000] Run /init as init process
[  126.690000] calling  ide_init+0x0/0x7c [ide_core] @ 43
[  126.700000] Uniform Multi-Platform E-IDE driver
[  126.710000] initcall ide_init+0x0/0x7c [ide_core] returned 0 after 7988 usecs
[  126.980000] calling  amiga_gayle_ide_driver_init+0x0/0x1c [gayle] @ 43
[  126.990000] ide: Gayle IDE controller (A1200 style)
[  127.000000] Probing IDE interface ide0...
[  127.390000] hda: probing with STATUS(0x50) instead of ALTSTATUS(0x0a)
[  127.540000] hda: SAMSUNG MP0402H, ATA DISK drive
[  127.610000] Z2RAM: using 0K Zorro II RAM and 512K Chip RAM (Total 512K)
[  127.980000] hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x0a)
[  128.200000] hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x0a)
[  148.570000] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:43]
Finn has raised the issue of systemd's short timeouts before. I'm
wondering whether that's part of your problem here. But the IDE driver
probe for a second disk should eventually complete, regardless of
systemd's udev module crashing?

I think this is essentially a kernel bug: There is no "initcall
amiga_gayle_ide_driver_init returned" in the log.

Yes, but what happens if systemd interrupts the modprobe call while the driver is waiting for some kind of timeout? Will we still see the modprobe complete?

Cheers,

    Michael



I've asked Szymon to try blacklisting that initcall (off-list).



Reply to: