#11525 HIGH 1.75-so: EC timeout reading battery data after resume snowballs into kernel panic with runin
Zarro Boogs per Child
bugtracker at laptop.org
Tue Dec 6 14:46:40 EST 2011
#11525: EC timeout reading battery data after resume snowballs into kernel panic
with runin
-----------------------+----------------------------------------------------
Reporter: greenfeld | Owner:
Type: defect | Status: new
Priority: high | Milestone: 1.75-software
Component: kernel | Version: Development build as of this date
Keywords: | Next_action: diagnose
Verified: 0 | Deployment_affected:
Blockedby: | Blocking:
-----------------------+----------------------------------------------------
A SKU 201 XO-1.75 (not our misbehaving unit) running runin had an EC
timeout reading the battery after resume, which led to a lot more EC
timeout errors getting data from the battery, and an eventual kernel panic
inside an interrupt handler.
But it seems to all start with this, tested with 11.3.1 os18:
{{{
[16957.459686] Suspending console(s) (use no_console_suspend to debug)
[16957.469138] dcon_source_switch to DCON
[16957.493254] olpc-dcon: The DCON has control
[16957.494477] RAYDIUM_i2c_suspend, disable i2c irq
[16957.494817] libertas_sdio mmc1:0001:1: mmc1:0001:1: suspend: PM flags =
0x3
[16957.494852] libertas_sdio mmc1:0001:1: Suspend without wake params --
powering down card
[16957.507542] mmc1: card 0001 removed
[16957.507754] [galcore]: gpu_suspend, 1358
[16957.507771] >>>>>>[_gpu_off]@1127
[16957.517109] <<<<<<[_gpu_off]@1145
[16957.607305] PM: suspend of devices complete after 140.913 msecs
[16957.607624] PM: late suspend of devices complete after 0.294 msecs
[16957.609142] PM: early resume of devices complete after 0.447 msecs
[16957.609240] mmp2_pm_finish
[16967.598109] olpc-ec-1.75: EC protocol error: timeout waiting for
command to transmit
[16967.598141] power_supply olpc-battery: driver failed to report `temp'
property
[16967.598193] olpc-ec-1.75: failing command because of prior EC protocol
error
[16967.598193] power_supply olpc-battery: driver failed to report `status'
property
[16967.598222] olpc-ec-1.75: failing command because of prior EC protocol
error
[16967.847992] [galcore]: gpu_resume, 1369
[16967.848435] >>>>>>[_gpu_on]@1153
[16967.857993] <<<<<<[_gpu_on]@1173
[16967.878898] mmcblk0: error -110 sending status command
[16967.878922] mmcblk0: error -110 sending read/write command, response
0x0, card status 0x0
[16967.880821] mmcblk0: error -110 requesting status
[16967.880829] end_request: I/O error, dev mmcblk0, sector 2501752
[16967.880848] Buffer I/O error on device mmcblk0p2, logical block 295311
[16967.880866] lost page write due to I/O error on mmcblk0p2
[16967.881012] JBD2: Detected IO errors while flushing file data on
mmcblk0p2-8
[16967.881646] mmcblk0: error -110 sending status command
[16967.881646] mmcblk0: error -110 sending SET_BLOCK_COUNT command,
response 0x0, card status 0x0
[16967.883556] mmcblk0: error -110 requesting status
[16967.883563] end_request: I/O error, dev mmcblk0, sector 3650856
[16967.883577] end_request: I/O error, dev mmcblk0, sector 3650864
[16967.883626] Aborting journal on device mmcblk0p2-8.
[16967.884371] mmcblk0: error -110 sending status command
[16967.884384] mmcblk0: error -110 sending SET_BLOCK_COUNT command,
response 0x0, card status 0x0
[16967.886285] mmcblk0: error -110 requesting status
[16967.886285] end_request: I/O error, dev mmcblk0, sector 3547136
[16967.886298] Buffer I/O error on device mmcblk0p2, logical block 425984
[16967.886314] lost page write due to I/O error on mmcblk0p2
[16967.886366] JBD2: I/O error detected when updating journal superblock
for mmcblk0p2-8.
[16967.897996] usb 1-1: reset high speed USB device number 2 using pxau2o-
ehci
[16968.178717] dcon_source_switch to CPU
[16968.179349] PM: resume of devices complete after 10570.108 msecs
[16968.426118] olpc-dcon: The CPU has control
[16968.430205] Restarting tasks ...
[16968.475507] EXT4-fs error (device mmcblk0p2):
ext4_journal_start_sb:296:
[16968.484777] olpc-ec-1.75: failing command because of prior EC protocol
error
[16968.498075] EXT4-fs error (device mmcblk0p2):
ext4_journal_start_sb:296: Detected aborted journal
[16968.498106] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[16968.538064] done.
}}}
--
Ticket URL: <http://dev.laptop.org/ticket/11525>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list