maemo.org Bugzilla – Bug 10808
kernel oops on activating heartbeat trigger
Last modified: 2010-10-25 17:12:54 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: Linux Nokia-N900-42-11 2.6.28-omap1 #1 PREEMPT Thu Apr 15 09:47:09 EEST 2010 armv7l unknown EXACT STEPS LEADING TO PROBLEM: open ssh to N900, wait until screen black and white breathing light, do Nokia-N900-42-11:~# root Nokia-N900-42-11:~# echo heartbeat >/sys/class/leds/lp5523:b/trigger EXPECTED OUTCOME: blue LED should start pulsing (maybe overridden by breathing light, but no matter what ->) ACTUAL OUTCOME: immediate system reboot REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: none OTHER COMMENTS: /dev/mtd2ro: [80632.341247] [<bf0342f8>] (lp5523_set_brightness+0x0/0x2d8 [leds_lp5523]) from [<c01ef944>] (led_heartbeat_function+0xdc/0xfc) [80632.341400] r7:c01ef868 r6:cf38398c r5:c8556180 r4:0000001e [80632.341461] [<c01ef868>] (led_heartbeat_function+0x0/0xfc) from [<c0061114>] (run_timer_softirq+0x188/0x240) [80632.341552] r7:c01ef868 r6:c0352000 r5:c038afc0 r4:00000103 [80632.341613] [<c0060f8c>] (run_timer_softirq+0x0/0x240) from [<c005bfc8>] (__do_softirq+0x64/0xf4) [80632.341705] r8:00000004 r7:00000001 r6:c038ad40 r5:c0352000 r4:00000103 [80632.341766] [<c005bf64>] (__do_softirq+0x0/0xf4) from [<c005c3d0>] (irq_exit+0x4c/0xa8) [80632.341857] [<c005c384>] (irq_exit+0x0/0xa8) from [<c002c088>] (__exception_text_start+0x88/0xa8) [80632.341918] r5:00000000 r4:00000025 [80632.341979] [<c002c000>] (__exception_text_start+0x0/0xa8) from [<c0285f04>] (__irq_svc+0x44/0xa4) [80632.342041] Exception stack(0xc0353ee0 to 0xc0353f28) [80632.342071] 3ee0: 017752b1 00000000 017752b1 3b9ac9ff 00000000 00000003 00000003 c0384300 [80632.342163] 3f00: c03b234c 411fc083 0000001f c0353f5c c0353f28 c0353f28 c003b558 c003b564 [80632.342254] 3f20: 20000053 ffffffff [80632.342346] r5:d8200000 r4:ffffffff [80632.342376] [<c003b440>] (omap3_enter_idle+0x0/0x15c) from [<c003b628>] (omap3_enter_idle_bm+0x54/0x5c) [80632.342468] r7:c03843d0 r6:c0384440 r5:c0384440 r4:c03843d0 [80632.342529] [<c003b5d4>] (omap3_enter_idle_bm+0x0/0x5c) from [<c01edb14>] (cpuidle_idle_call+0x98/0xf4) [80632.342620] r5:c0352000 r4:c01eda7c [80632.342651] [<c01eda7c>] (cpuidle_idle_call+0x0/0xf4) from [<c002d950>] (cpu_idle+0x40/0x78) [80632.342742] r9:411fc083 r8:80027ee4 r7:c0356570 r6:c0029f04 r5:c0352000 [80632.342803] r4:c01eda7c [80632.342834] [<c002d910>] (cpu_idle+0x0/0x78) from [<c0281f00>] (rest_init+0x74/0x88) [80632.342895] r5:c038326c r4:c0352000 [80632.342926] [<c0281e8c>] (rest_init+0x0/0x88) from [<c0008a28>] (start_kernel+0x29c/0x2fc) [80632.343017] r5:c038326c r4:c039d7c4 [80632.343048] [<c000878c>] (start_kernel+0x0/0x2fc) from [<80008034>] (0x80008034) [80632.343170] r5:c03837c0 r4:10c5387d [80632.343200] Code: bad PC value. ��������������������������������������������������������]][80632.344055] mtdoops: Ready 3, 4 (no erase) [80632.344177] Kernel panic - not syncing: Fatal exception in interrupt [80632.344238] Panic info buffer: [80632.344268] OSSO_PRODUCT_HARDWARE='RX-51' [80632.344299] OSSO_PRODUCT_NAME='N900' [80632.344299] OSSO_PRODUCT_FULL_NAME='Nokia N900' [80632.344299] OSSO_PRODUCT_RELEASE_NAME='Maemo 5' [80632.344329] OSSO_PRODUCT_RELEASE_FULL_NAME='Maemo 5' [80632.344360] OSSO_PRODUCT_RELEASE_VERSION='10.2010.19-1' [80632.344360] OSSO_PRODUCT_WLAN_CHANNEL='fcc/us' [80632.344390] OSSO_PRODUCT_KEYBOARD='English, Dutch' [80632.344390] OSSO_PRODUCT_REGION='Britain' [80632.344421] OSSO_PRODUCT_SHORT_NAME='Nokia N900' [80632.344421] OSSO_VERSION='RX-51_2009SE_10.2010.19-1_PR_MR0' [80632.344451] �����������������������������������������������������������������������������������������������������������������������������
This is easily reproducible, but what is "heartbeat trigger"? (no crashes from this internally so I don't think this is anything that user can trigger.)
This has been fixed in package kernel 2.6.28-20103003+0m5 which is part of the internal build version 2010.31-2 (Note: 2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
The problem reported here should be fixed in the update that was released today for public: The Maemo5 update version 20.2010.36-2 (also called "PR1.3" sometimes). Please leave a comment if the problem is not fixed for you in this update version.