On Wednesday 06 Jul 2005 21:44, Ingo Molnar wrote:
[snip]
>
> the ACPI-idle bug's primary effects were the missed wakeups, but they
> should not cause lockups, because timer interrupts should always occur
> and should eventually 'fix up' such missed wakeups.
>
> but there's another side-effect of the ACPI-idle bug: the ACPI code was
> running with interrupts enabled and maybe the hardware locks up if
> interrupted in the wrong moment. ACPI sleeps are sensitive things and
> closely related to other IRQ hardware, which we all program with
> interrupts disabled. So i'd not be surprised if the lockups were caused
> by the ACPI-idle bug.
>
> Ingo
Okay, well an hour later and still no lockups, so you're probably right.
This is a completely unrelated question, but now we've got everything under
control.. how do I make "quiet" actually do something on the RT patchset?
Currently I flag it on the kernel cmdline, but I still get everything spewed
to my primary VT.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/CSim Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |