#7458 BLOC 8.2.0 (: Intermitent suspend/resume lockup
Zarro Boogs per Child
bugtracker at laptop.org
Thu Jul 17 05:15:29 EDT 2008
#7458: Intermitent suspend/resume lockup
----------------------------+-----------------------------------------------
Reporter: dsaxena | Owner: dsaxena
Type: defect | Status: assigned
Priority: blocker | Milestone: 8.2.0 (was Update.2)
Component: not assigned | Version: Development build as of this date
Resolution: | Keywords: joyride-2131:-
Next_action: diagnose | Verified: 0
Blockedby: | Blocking: 7393
----------------------------+-----------------------------------------------
Comment(by dsaxena):
Replying to [comment:28 rsmith]:
> oops2.log is another oops. I stopped the log since the kernel appeared
to be in runaway oops mode. Eventually it did recover.
>
> I do see timeouts in the log but nothing in my EC log indicates anything
is wrong. Currently I'm very suspect of the fact that the timestamp on
the printk does not increase between ec commands. That's something I've
not see in prior kernels.
Investigating the timestamp oddness and the way that printk() is getting
timestamps has changed from 2.6.22 to 2.6.25. In 2.6.22 we just read the
TSC and used that for the printk() time whereas in the new kernel we're
doing calling a wrapper function (__update_rq_clock) that does some range
checking. Looking at this wrapper, I believe it may be possible to end up
with duplicate timestamps when coming out of resume, but I need to add
some debug prints and dig a bit more into the timer code to validate.
I doubt that this is related to EC timeouts, but will test to rule it out
for sure as we've got too many variables we're dealing with in this bug
and I need to narrow down what to look at.
--
Ticket URL: <http://dev.laptop.org/ticket/7458#comment:29>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list