- Mar 10, 2014
-
-
Laura Abbott authored
When reading soc info, the ram information has not yet been fully plumbed into the parser (this is very early!). We should not take the address for the start of ram into account at this point as smem should only be given as an offset. Update the calculations. Change-Id: Ib02db2f118685b306457e2591e4bbc5f19f2edbc
-
Laura Abbott authored
When adding a new board, it can be non-obvious what went wrong if the board is not immediately detected. Add an option to trace through socinfo addresses for a specific board to print out useful addresses as a debugging aid. Also clean up some error handling, mostly among the tracing code. Change-Id: I65f4a38b95912b81676f44cd371751abc96aae9e
-
Laura Abbott authored
The pagetype info gives useful data but it's helpful to see the data in other formats that often involve having to do math. Make the parser do the math of calculating the total number of pages per migrate type and the total number of pages per order. Additionally, print out the total number of ram pages with vmstat to make it easier to determine just how low a system may be on memory. Change-Id: I812288fe4c25de06c7017fb0b6515e514f799134
-
- Mar 08, 2014
-
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
- Mar 04, 2014
-
-
Laura Abbott authored
Full slabs are only stored when CONIFG_SLUB_DEBUG is enabled. Move the parsing for full slabs to this conditional check. Change-Id: I6bdd402f888f857c9c0ce1b2443d8436e90cdb84
-
Laura Abbott authored
The logbuf for kernel dmesg logs may be re-sized at bootup to be non-static. Account for this by parsing the non-static version which should should also point to the static version. Change-Id: Id5a2da0036b31ac0b5f4622a5e1cd74e38e8dae4
-
- Feb 27, 2014
-
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
Laura Abbott authored
A recent build has generated multiple badly corrupted dumps. Fix all the errors found by the unintentional fuzzing. Change-Id: I0854bee4558d31037f51ed2ea941eb58997607c8
-
- Feb 18, 2014
-
-
Laura Abbott authored
Red/Black trees are supposed to be trees, not directed cyclic graphs. Sometimes trees in ramdumps may become corrupted though, resulting in cycles. Detect these cycles in the tree to avoid looping forever. Change-Id: I68cf018c6786b3c6947789a18c63c7a3a1f8d7bc
-
- Feb 15, 2014
-
-
Laura Abbott authored
The IRQ state is stable and isn't likely to change any time soon. Remove the version checks which do nothing for now. Change-Id: I3ba2d4fcde6694c16d5f8b79d26b971341f1acc2
-
- Feb 13, 2014
-
-
Laura Abbott authored
The specification of boards of the parser is not very clean. Re-write it into an easier to read fashion. Change-Id: Icae5b8421cf574ee910e4702fcf14d29378ed703
-
- Feb 12, 2014
-
-
Linux Build Service Account authored
-
- Feb 11, 2014
-
-
Laura Abbott authored
We never check the binaries in and its annoying to see them with a git/diff. Add generated pyc files to .gitignore Change-Id: Ie181bc8e278d090d088fc1aaba290ac77f724363
-
- Feb 05, 2014
-
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
- Feb 03, 2014
-
-
Linux Build Service Account authored
-
- Jan 30, 2014
-
-
Laura Abbott authored
Workqueues may be modified at runtime which can leave them in an inconsistent state in ram dumps. Check for infinite loops in workqueue lists caused by this state. Change-Id: If5d8ebe48a538ffae58a8ed485cd4a50b20d60bf
-
- Jan 27, 2014
-
-
Mitchel Humpherys authored
Somewhere along the way we started ignoring the --nm-path and --gdb-path options. Fix this. Also ensure that the command line options take precedence over anything from local_settings.py or anything discovered from CROSS_COMPILE. Change-Id: I39ff653c7de7fb1de170701b898567c9b2356835
-
Mitchel Humpherys authored
We are currently printing gdb_path when there are issues with nm_path. Fix this by printing nm_path. Also change local_settings.pyi to local_settings.py. Change-Id: I391abb423b32cf571be1d6da3b8961cc3c6e2ee4
-
- Jan 26, 2014
-
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
Linux Build Service Account authored
-
- Jan 25, 2014
-
-
Laura Abbott authored
Sometimes the slabinfo data structures may be corrupt because of software error or when the ramdumps were collected. Detect this bettter to avoid looping forever or going out of bounds. Change-Id: I5b0202048d61b937355d7e3d2b2b18f629529657
-
Laura Abbott authored
Older targets use a slightly different version of map around the hole which has different variable names. Account for this in the code. Change-Id: Ia657b265dc6f34c9fb33f71c1ef62dbf0c0c2114
-
Laura Abbott authored
Several imports were dropped during code refactor. Re-add them. Change-Id: I29b6d680c19400f1e246891ec0e32730f8a6424c
-
Laura Abbott authored
The alternate workqueue function is based on 3.0, not 3.4. Fix the name. Change-Id: I8a1c4c4e3e6ae6e968c8704316a2a72ef0b118aa
-
- Jan 18, 2014
-
-
Linux Build Service Account authored
-
- Jan 03, 2014
-
-
Laura Abbott authored
After a crash, ramdumps may be collected for analysis. The ram parser is a tool to aid in analysis of these dumps. The script extracts useful information from the dumps to help with debugging. Please see the README for full details. Change-Id: I7795686a96bbfe246edf47d09e3f616131688429
-
- Nov 25, 2013
-
-
Git User Service Account authored
-