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 #2212: pppd: page allocation failure.
order:4, mode:0x4d0 (Openmoko Public Trac)
2. Re: Openmoko Bug #2212: pppd: page allocation failure.
order:4, mode:0x4d0 (Openmoko Public Trac)
3. Re: Openmoko Bug #2135: write kernel crash message somewhere
where it can be retrieved after reboot? (Openmoko Public Trac)
4. Re: Openmoko Bug #2135: write kernel crash message somewhere
where it can be retrieved after reboot? (Openmoko Public Trac)
--- Begin Message ---
#2212: pppd: page allocation failure. order:4, mode:0x4d0
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Thanks ! Yes, I was afraid that it may be pretty hard to reproduce.
We seem to run into fragmentation problems unusually fast, but this
may be just the usage pattern.
I guess we'll have to try one day to cap allocations after boot and
see what happens ...
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2212#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2212: pppd: page allocation failure. order:4, mode:0x4d0
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
At lesat on top of b8b36e5ec3db71 the patch does not cause breakage and I
can use gprs normally.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2212#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I tried booting with mem=127M and incrementing a byte in memory on every
boot
{{{
diff --git a/init/main.c b/init/main.c
index 7e117a2..fb2b531 100644
--- a/init/main.c
+++ b/init/main.c
@@ -693,6 +693,17 @@ asmlinkage void __init start_kernel(void)
ftrace_init();
+ {
+ char *buf;
+ buf = ioremap(127<<20, 4096);
+ if (buf) {
+ printk("ioremap returned %08x\n", buf);
+ printk("%02x %02x %02x\n", buf[0], buf[1], buf[2]);
+ buf[0]++;
+ iounmap(buf);
+ }
+ }
+
/* Do the rest non-__init'ed, we're now alive */
rest_init();
}
}}}
but every time I see zeroes. Any idea what is zeroing the memory?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2135: write kernel crash message somewhere where it can be retrieved after
reboot?
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I tried mem=120M and writing to 123<<20 just in case but this did not make
any difference.
I also tried changing the memory from uboot
{{{
GTA02v5 # base 0x30000000
Base Address: 0x30000000
GTA02v5 # md 0x087b00000 4
b7b00000: ffffffff ffffffff ffffffff ffffffff ................
GTA02v5 # mw 0x087b00000 1 1
GTA02v5 # md 0x087b00000 4
b7b00000: 00000001 ffffffff ffffffff ffffffff ................
}}}
but still only saw zeroes under linux. So either something is zeroing the
memory during boot or I am writing/reading a completely wrong memory
address?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2135#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
