#9565 BLOC 1.5-F11: system freeze under os33
Zarro Boogs per Child
bugtracker at laptop.org
Thu Oct 29 12:47:01 EDT 2009
#9565: system freeze under os33
------------------------------------+---------------------------------------
Reporter: pgf | Owner:
Type: defect | Status: new
Priority: blocker | Milestone: 1.5-F11
Component: not assigned | Version: not specified
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Comment(by pgf):
another possibility -- we're spinning with continuous SCI interrupts?
twice, while acpi debug tracing has been on, i've experienced lockups.
first time it was continuous like this:
{{{
[ 1504.061847] evevent-0249 [00] ev_fixed_event_detect : Fixed Event
Block: Enable 00000100 Status 00000801
[ 1504.072072] evgpe-0445 [00] ev_gpe_detect : Read GPE
Register at GPE0: Status=00, Enable=00
[ 1504.082025] evgpe-0445 [00] ev_gpe_detect : Read GPE
Register at GPE8: Status=00, Enable=08
[ 1504.092005] olpc-dcon: scanline interrupt w/CPU
}}}
second time like this:
{{{
[ 1504.061847] evevent-0249 [00] ev_fixed_event_detect : Fixed Event
Block: Enable 00000100 Status 00000801
[ 1504.072072] evgpe-0445 [00] ev_gpe_detect : Read GPE
Register at GPE0: Status=00, Enable=00
[ 1504.082025] evgpe-0445 [00] ev_gpe_detect : Read GPE
Register at GPE8: Status=00, Enable=08
[ 1504.092005] olpc-dcon: scanline interrupt w/CPU
}}}
we wouldn't get the dcon message if acpi had handled the interrupt (and
it's not for dcon either). this implies an asserted interrupt from
elsewhere.
one obvious interrupt source that would cause SCI but not be shown in
those registers is SMBALRT#. this source is enabled, because DCONIRQ uses
it on B2. i'll do some probing.
--
Ticket URL: <http://dev.laptop.org/ticket/9565#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list