> Enough crashing for today. Strangest thing is the NMI watchdog does not
> fire...
It's disabled now by default.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Enough crashing for today. Strangest thing is the NMI watchdog does not
fire...
It's disabled now by default.
-Andi
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Chuck Ebbert wrote:
CONFIG_HPET_EMULATE_RTC=y
Did you try without that?
Just did. Still hangs same way; strace shows /sbin/hwclock dying after
hundreds of RTC_RD_TIME. And now /proc/interrupts shows no rtc
interrupts being generated (expected, I gues). Seems to take longer
Chuck Ebbert wrote:
Well, turns out this is a heisenbug. Which is good, since it means the
nop patch didn't change anything.
Try leaving the spinlocks and just disabling the callbacks. And maybe
enable spinlock debugging...
I tried removing all the spinlocks inside the interrupt
Zachary Amsden wrote:
> With this patch, /sbin/hwclock no longer hangs my AMD64 machine when run
> after reaching multiuser. What I don't understand is why. I have the
> RTC based sound sequencer timer as a module, but not loaded, and the
> error message I added to indicate broken rtc control
With this patch, /sbin/hwclock no longer hangs my AMD64 machine when run
after reaching multiuser. What I don't understand is why. I have the
RTC based sound sequencer timer as a module, but not loaded, and the
error message I added to indicate broken rtc control does not fire.
So why is it
With this patch, /sbin/hwclock no longer hangs my AMD64 machine when run
after reaching multiuser. What I don't understand is why. I have the
RTC based sound sequencer timer as a module, but not loaded, and the
error message I added to indicate broken rtc control does not fire.
So why is it
Zachary Amsden wrote:
With this patch, /sbin/hwclock no longer hangs my AMD64 machine when run
after reaching multiuser. What I don't understand is why. I have the
RTC based sound sequencer timer as a module, but not loaded, and the
error message I added to indicate broken rtc control does
Chuck Ebbert wrote:
Well, turns out this is a heisenbug. Which is good, since it means the
nop patch didn't change anything.
Try leaving the spinlocks and just disabling the callbacks. And maybe
enable spinlock debugging...
I tried removing all the spinlocks inside the interrupt
Chuck Ebbert wrote:
CONFIG_HPET_EMULATE_RTC=y
Did you try without that?
Just did. Still hangs same way; strace shows /sbin/hwclock dying after
hundreds of RTC_RD_TIME. And now /proc/interrupts shows no rtc
interrupts being generated (expected, I gues). Seems to take longer
10 matches
Mail list logo
