Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2238: CONFIG_FUNCTION_TRACER panics very
early (Openmoko Public Trac)
2. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
3. Re: Openmoko Bug #2238: CONFIG_FUNCTION_TRACER panics very
early (Openmoko Public Trac)
4. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
5. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
6. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
--- Begin Message ---
#2238: CONFIG_FUNCTION_TRACER panics very early
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
On second try I got a different backtrace:
{{{
[ 1017.980000] gadgetfs: USB Gadget filesystem, version 24 Aug 2004
[ 1261.730000] Bad mode in data abort handler detected
[ 1261.730000] Internal error: Oops - bad mode: 0 [#1] PREEMPT
[ 1261.730000] Modules linked in: gadgetfs s3c2410_wdt [last unloaded:
g_ether]
[ 1261.730000] CPU: 0 Not tainted (2.6.28-GTA02_lindi-andy-
tracking_b8b36e5ec3db71d5-mokodev #53)
[ 1261.730000] PC is at rb_reserve_next_event+0x4/0x3c8
[ 1261.730000] LR is at 0x20000013
[ 1261.730000] pc : [<c008db84>] lr : [<20000013>] psr: 800000d1
[ 1261.730000] sp : c7997e60 ip : 00590000 fp : c7997ebc
[ 1261.730000] r10: 00000014 r9 : 00000001 r8 : 00000015
[ 1261.730000] r7 : c003f9b4 r6 : c09cce48 r5 : 200000d1 r4 : 00000000
[ 1261.730000] r3 : 00000017 r2 : 00000014 r1 : 00000003 r0 : c7810ba0
[ 1261.730000] Flags: Nzcv IRQs off FIQs off Mode FIQ_32 ISA ARM
Segment kernel
[ 1261.730000] Control: c000717f Table: 37b88000 DAC: 00000017
[ 1261.730000] Process events/0 (pid: 5, stack limit = 0xc7996268)
[ 1261.730000] Stack: (0xc7997e60 to 0xc7998000)
[ 1261.730000] 7e60: c7810ba0 00000003 00000014 00000017 00000000 200000d1
c09cce48 c003f9b4
[ 1261.730000] 7e80: 00000015 00000001 00000014 c7997ebc 00590000 c7997e60
20000013 c008db84
[ 1261.730000] 7ea0: 800000d1 ffffffff 00000001 c051cb10 c7997ed4 c7997ec0
c02928c8 c003f108
[ 1261.730000] 7ec0: c7b58d10 00000002 c7997efc c7997ed8 c0291f0c c0292884
c7b58d10 c780bc80
[ 1261.730000] 7ee0: c7b58ca0 c7b58d0c 00000000 c7997f58 c7997f3c c7997f00
c0292484 c0291eec
[ 1261.730000] 7f00: c7997f3c c7997f10 c0078860 c0078078 00000001 00000000
00000000 c0068bac
[ 1261.730000] 7f20: c7b58d10 c780bc80 c7996000 c7b58d0c c7997f94 c7997f40
c0068c24 c0292458
[ 1261.730000] 7f40: 00000001 00000000 c0068bac 20000013 c780bca0 c0292448
c0a03354 00000000
[ 1261.730000] 7f60: c049fa01 00000000 c7997f74 c780bca8 c7996000 c780bc80
c780bca0 c7997f9c
[ 1261.730000] 7f80: 00000000 00000000 c7997fd4 c7997f98 c0069134 c0068b08
c03bde68 00000000
[ 1261.730000] 7fa0: c79940a0 c006d54c c7997fa8 c7997fa8 c780bc80 c7996000
c780bc80 c0069030
[ 1261.730000] 7fc0: 00000000 00000000 c7997ff4 c7997fd8 c006d20c c0069040
00000000 00000000
[ 1261.730000] 7fe0: 00000000 00000000 00000000 c7997ff8 c005a914 c006d1b8
ffffffff ffffffff
[ 1261.730000] Backtrace:
[ 1261.730000] [<c003f0f8>] (fiq_kick+0x0/0xbc) from [<c02928c8>]
(gta02hdq_read+0x54/0xb0)
[ 1261.730000] r4:c051cb10
[ 1261.730000] [<c0292874>] (gta02hdq_read+0x0/0xb0) from [<c0291f0c>]
(hdq_read16+0x30/0x88)
[ 1261.730000] r5:00000002 r4:c7b58d10
[ 1261.730000] [<c0291edc>] (hdq_read16+0x0/0x88) from [<c0292484>]
(bq27000_battery_work+0x3c/0x13c)
[ 1261.730000] [<c0292448>] (bq27000_battery_work+0x0/0x13c) from
[<c0068c24>] (run_workqueue+0x12c/0x228)
[ 1261.730000] r7:c7b58d0c r6:c7996000 r5:c780bc80 r4:c7b58d10
[ 1261.730000] [<c0068af8>] (run_workqueue+0x0/0x228) from [<c0069134>]
(worker_thread+0x104/0x118)
[ 1261.730000] [<c0069030>] (worker_thread+0x0/0x118) from [<c006d20c>]
(kthread+0x64/0x98)
[ 1261.730000] r8:00000000 r7:00000000 r6:c0069030 r5:c780bc80
r4:c7996000
[ 1261.730000] [<c006d1a8>] (kthread+0x0/0x98) from [<c005a914>]
(do_exit+0x0/0x308)
[ 1261.730000] r6:00000000 r5:00000000 r4:00000000
[ 1261.730000] Code: c09cb9c0 00000367 0000028e e1a0c00d (e92ddff0)
[ 1261.730000] Bad mode in data abort handler detected
[ 1261.730000] BUG: spinlock lockup on CPU#0, events/0/5, c04d751c
[ 1261.730000] [<c03bd434>] (dump_stack+0x0/0x18) from [<c01bfd38>]
(_raw_spin_lock+0x114/0x150)
[ 1261.730000] [<c01bfc24>] (_raw_spin_lock+0x0/0x150) from [<c03c061c>]
(_spin_lock_irq+0x7c/0x8c)
[ 1261.730000] [<c03c05a0>] (_spin_lock_irq+0x0/0x8c) from [<c003973c>]
(die+0x3c/0xcc)
[ 1261.730000] r7:c7997de0 r6:c0464b51 r5:00000000 r4:c7997de0
[ 1261.730000] [<c0039700>] (die+0x0/0xcc) from [<c0039818>]
(bad_mode+0x4c/0x5c)
[ 1261.730000] [<c00397cc>] (bad_mode+0x0/0x5c) from [<c0056e04>]
(add_taint+0x24/0x30)
[ 1261.730000] r4:00000007
[21474541.070000] ramconsole: old data ends here
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2238#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
I don't think I have any special powers in trac. Don't you have an "Attach
file" button above the change history ?
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:26>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2238: CONFIG_FUNCTION_TRACER panics very early
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
http://marc.info/?l=linux-arm-kernel&m=123334871704646&w=2
"Re: [PATCH] [ARM] ftrace: fix crash due to tracing of __naked"
has a patch that modifies the ringbuffer code however it can not be
applied since it depends on at least
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=abc9b56d66fbd4d93302ef4bf6fa726e1b8255f9
if I understand this correctly.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2238#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Replying to [comment:26 werner]:
> I don't think I have any special powers in trac. Don't you have an
"Attach file" button above the change history ?
>
> - Werner
I'm blind... I did not see the "Attach file" button, because it was 4
pages from the beginning and many pages from the end...
There is a screenshot available here:
https://docs.openmoko.org/trac/attachment/ticket/2217/OpenMoko%20Freerunner%20crash%20with%20kernel%209029dff1f370018665a6e2999632a34fd0518f4d.2.jpeg
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:27>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
That randomish noise is not that easy to generate. Plus, it comes from
the top and ends in a linear way.
I wonder if what has happened is that too much data is written from the SD
Card unit in the Glamo (which is done by local Glamo DMA), so that it
blows through the allocation of Glamo internal memory and wraps into an
alias that is the framebuffer.
Is the noise always appearing from the "top" when it comes?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:28>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Replying to [comment:28 andy]:
> Is the noise always appearing from the "top" when it comes?
The overwrite direction is always from top to bottom.
I think it happens almost always that it starts at the top.
In rare cases (but I do not quite remember), it may be that it starts,
stops, then starts again in a lower region, so there may be gaps.
Maybe I should add something to the system setup:
> That randomish noise is not that easy to generate.
My complete filesystem is encrypted. That is, I run ext3 over dm-crypt
over /dev/mmcblk0p2. So, in my case, the encrypted filesystem data is a
good explanation of why the data visible is actually noisy.
Triggering the bug may also have something to with the CPU load due to
encryption or with effects of encryption onto timing (e.g. loading takes
longer).
> I wonder if what has happened is that too much data is written from the
SD Card unit in the Glamo (which is done by local Glamo DMA), so that it
blows through the allocation of Glamo internal memory and wraps into an
alias that is the framebuffer.
This looks like an interesting theory, but as I'm not a hardware hacker, I
cannot really comment. However, I'm eager to compile some special kernels
with debugging messages and the like in order to help you diagnose and
fix.
I may add that, when running from internal flash memory instead of SD-
card, I almost never experienced such crashes. However, I cannot properly
compare, because I cannot run dm-crypt over the internal flash memory,
because the internal flash memory is not a normal Linux block device.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:29>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
