Skip to contentSkip to conversation

hangs in verify_pmtmr_rate()

DISCUSSION Dave Hansen 3 participants 4 messages Jun 3, 2015

lore
Share & tools
lore
#0 lore raw

I'm seeing boot hangs when trying to boot a 32-bit 4.1.0-rc5 kernel on some 64-bit CPUs (I'm not sure if it is a regression). The NMI watchdog shows init_acpi_pm_clocksource() as the last thing in the backtrace, specifically verify_pmtmr_rate()'s I/O instructions. It appears to be mach_countup()'s while loop that gets stuck.

Booting with "pmtmr=0" works around this for me, as would unsetting CONFIG_X86_PM_TIMER I'd imagine.

The hardware I'm doing this on is a bit wonky and I think the hpet is broken on it.

Does this look like *really* broken hardware, or something that we should be detecting and able to recover from?

#1 lore raw
Quoted 6 lines · Dave Hansen

I'm seeing boot hangs when trying to boot a 32-bit 4.1.0-rc5 kernel on some 64-bit CPUs (I'm not sure if it is a regression). The NMI watchdog shows init_acpi_pm_clocksource() as the last thing in the backtrace, specifically verify_pmtmr_rate()'s I/O instructions. It appears to be mach_countup()'s while loop that gets stuck.

Quoted 8 lines

Booting with "pmtmr=0" works around this for me, as would unsetting CONFIG_X86_PM_TIMER I'd imagine.

The hardware I'm doing this on is a bit wonky and I think the hpet is broken on it.

Does this look like *really* broken hardware, or something that we should be detecting and able to recover from?

Hrm. Does this machine have a working PIT?

Does pit_calibrate_tsc() end up being used on this box to calibrate the TSC (its similar logic, so it should get stuck in the same way), or does it use a different method for tsc calibration?

thanks
-john

#2 lore raw
Quoted 10 lines · John Stultz
Quoted 9 lines · Dave Hansen

I'm seeing boot hangs when trying to boot a 32-bit 4.1.0-rc5 kernel on some 64-bit CPUs (I'm not sure if it is a regression). The NMI watchdog shows init_acpi_pm_clocksource() as the last thing in the backtrace, specifically verify_pmtmr_rate()'s I/O instructions. It appears to be mach_countup()'s while loop that gets stuck.

Booting with "pmtmr=0" works around this for me, as would unsetting CONFIG_X86_PM_TIMER I'd imagine.

Quoted 7 lines
Quoted 5 lines

The hardware I'm doing this on is a bit wonky and I think the hpet is broken on it.

Does this look like *really* broken hardware, or something that we should be detecting and able to recover from?

Hrm. Does this machine have a working PIT?

It _should_. :)

Quoted 3 lines

Does pit_calibrate_tsc() end up being used on this box to calibrate the TSC (its similar logic, so it should get stuck in the same way), or does it use a different method for tsc calibration?

I end up seeing:

Quoted 4 lines

tsc: Fast TSC calibration failed
tsc: Using PIT calibration value
tsc: Detected 911.616 MHz processor
Calibrating delay loop (skipped) , value calculated using timer frequency.. 1823.23 BogoMIPS... (lpj=3646464)

Which makes it look like native_calibrate_tsc() managed to successfully do a pit_calibrate_tsc() and got to the code below (otherwise we would have hit the (tsc_pit_min == ULONG_MAX) case).

Quoted 5 lines
        /* We don't have an alternative source, use the PIT calibration value */
        if (!hpet && !ref1 && !ref2) {
                pr_info("Using PIT calibration value\n");
                return tsc_pit_min;
        }

I later see:

Quoted 2 lines

timekeeping watchdog: Marking clocksource 'tsc' as unstable, because skew is too large:
'refined-jiffies' wd_now: ffeef86 wd_last: fffeef09 mask: ffffffff

#3 lore raw
In reply to Dave Hansen
Quoted 11 lines

From: Dave Hansen [mailto:[email protected]]
Sent: Wednesday, June 03, 2015 12:55 PM
To: LKML; Yu, Fenghua; John Stultz; the arch/x86 maintainers
Subject: hangs in verify_pmtmr_rate()

I'm seeing boot hangs when trying to boot a 32-bit 4.1.0-rc5 kernel on some 64-bit CPUs (I'm not sure if it is a regression). The NMI watchdog shows init_acpi_pm_clocksource() as the last thing in the backtrace, specifically verify_pmtmr_rate()'s I/O instructions. It appears to be mach_countup()'s while loop that gets stuck.

Quoted 8 lines

Booting with "pmtmr=0" works around this for me, as would unsetting CONFIG_X86_PM_TIMER I'd imagine.

The hardware I'm doing this on is a bit wonky and I think the hpet is broken on it.

Does this look like *really* broken hardware, or something that we should be detecting and able to recover from?

Latest 4.1.0-rc5 defconfig boots fine without "pmtmr=0" on my machine which is same kind as Dave's.

I always give "hpet=disable" on this machine to w/a a known hw issue.

Thanks.

-Fenghua

���{.n�+�������+%�����ݶ��w��{.n�+����{��G�����{ay�ʇڙ�,j��f���h��������z_�(�階�ݢj"���m������G������?����&���~��iO��z��v�^�m���� ������?�I�