| 6c34c2576eb241f134431b2cc847a6c7d70ef012 |
|
20-Aug-2015 |
Steve Fung <stevefung@google.com> |
crash_reporter: Relicense as Apache 2.
MODULE_LICENSE_BSD and NOTICE were removed as the license is no longer
different from the rest of system/core.
Bug: 23368756
Change-Id: I31e48eb7c3d153c7c5ec4f694c61474dedac2eeb
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 6aa551ec416bac9ec96a6103e25be78221cf36a4 |
|
06-Mar-2015 |
Peter Qiu <zqiu@chromium.org> |
crash-reporter: add support for device coredump
Copy the device coredump file to /var/spool/crash directory when
udev event "devcoredump" is detected. Also include the last 50 lines
of /var/log/messages and /var/log/net.log in the coredump file for
debugging purpose. Only perform the collection if feedback is allowed
(metrics are enabled) or the device is running a developer image.
By default, crash-reporter will not upload device coredumps to the crash
server. The user can enable device coredumps upload via a to-be-added
crosh command, which should only be done at the direction of CrOS engineers.
BUG=chromium:464872
TEST=USE="asan clang" FEATURES=test emerge-$BOARD crash-reporter
Manual Test:
1. Trigger wifi firmware error on a Clapper running developer image by
running following command:
"echo 1 > /sys/kernel/debug/iwlwifi/0000\:01\:00.0/iwlmvm/fw_restart"
2. Verify there is a device coredump file in "/var/spool/crash/"
"devcoredump_iwlwifi*.devcore", as well as the additional log file
".log" and the meta file ".meta".
Change-Id: Ic4cf67d4b5715a6f422505f409276d1261b7d51f
Reviewed-on: https://chromium-review.googlesource.com/257091
Reviewed-by: Zeping Qiu <zqiu@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 731da3379bd7ead7222b1a7add45e307bec7c865 |
|
28-Jan-2015 |
Daniel Erat <derat@chromium.org> |
crash-reporter: Use chromeos::KeyValueStore.
Make the crash reporter use libchromeos's KeyValueStore
class to read its log-collection config file and
/etc/lsb-release instead of its own parsing code.
Also update the log-collection config file to split long
commands across multiple lines and to use '=' instead of ':'
to separate executable names from commands.
BUG=chromium:452520
TEST=updated tests; also triggered powerd and chrome crashes
and checked that logs were attached
Change-Id: I4e2447712869608f32a4ae38f5d5cb9c6046af14
Reviewed-on: https://chromium-review.googlesource.com/244121
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 7e3b76d81fca476e08394eb40cc4b1ca8708475c |
|
27-Jan-2015 |
Daniel Erat <derat@chromium.org> |
crash-reporter: Add session_manager logs to Chrome crashes.
Attach the last twenty session_manager messages from
/var/log/messages to Chrome crash reports.
BUG=chromium:233833
TEST=manual: triggered a crash and checked chrome.txt in the
crash report (1f8c6ff259947e7a)
Change-Id: I733b448ccc6e01111556a5a632e185cc58dfd917
Reviewed-on: https://chromium-review.googlesource.com/243378
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Queue: Dan Erat <derat@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 8f5546adf995682142a3782036434c464ebfc885 |
|
22-Jan-2015 |
Daniel Erat <derat@chromium.org> |
crash-reporter: Attach Chrome logs to crash reports.
When Chrome crashes, gather the last 20 lines of each of the
latest two log files in /var/log/chrome and
/home/chronos/user/log. Attach them as gzipped metadata
using a "chrome.txt" key name and rename the GPU error state
key to "i915_error_state.log.xz".
(Re-landing after privacy review; originally reviewed at
https://chromium-review.googlesource.com/216427. Changes
since previous iteration include attaching the Chrome logs
and the GPU state separately and redirecting stderr to
/dev/null when listing user Chrome log files to avoid log
spam in the not-logged-in case.)
BUG=chromium:405732
TEST=triggered crashes and verified that logs were included
in crash reports: b7c4d7f2bee32e2f, 6292f090468fcf28
CQ-DEPEND=CL:242492
Change-Id: I1642a8971f1373726e5b0e3977dbfdbcc2aa6667
Reviewed-on: https://chromium-review.googlesource.com/242457
Commit-Queue: Dan Erat <derat@chromium.org>
Trybot-Ready: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 732bd3bb856fe07d15cbbc1770a21dfe6b30ef9a |
|
13-Sep-2014 |
Daniel Erat <derat@chromium.org> |
Revert "crash-reporter: Attach Chrome logs to crash reports."
I'm reverting this until I get a privacy review.
BUG=chromium:405732
TEST=none
Change-Id: Ib3af4752533f76c340d9b853be985bfc774104da
Reviewed-on: https://chromium-review.googlesource.com/218010
Reviewed-by: Daniel Erat <derat@chromium.org>
Commit-Queue: Daniel Erat <derat@chromium.org>
Tested-by: Daniel Erat <derat@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 55cb40aa95c64e2d7c6385c7e86a598968d5b841 |
|
03-Sep-2014 |
Daniel Erat <derat@chromium.org> |
crash-reporter: Attach Chrome logs to crash reports.
When Chrome crashes, gather the last 20 lines of each of the
latest two log files in /var/log/chrome and
/home/chronos/user/log and include them in the archive file
that's attached to crash reports.
BUG=chromium:405732
TEST=triggered crashes at the login screen and after logging
in and verified that logs were included in crash
reports: bdf766f0d6d1e066, a9d410e1a86f996b
Change-Id: I09e3cee23af108dc216d64aae85d78751d5649d4
Reviewed-on: https://chromium-review.googlesource.com/216427
Reviewed-by: Ben Chan <benchan@chromium.org>
Tested-by: Daniel Erat <derat@chromium.org>
Commit-Queue: Daniel Erat <derat@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| f290e9873ef4cd9821ba0b03f45894e942c1115c |
|
03-Sep-2014 |
Daniel Erat <derat@chromium.org> |
crash-reporter: Include powerd logs with crashes.
Attach relevant power manager logs to crash reports for
powerd, powerd_setuid_helper, and power_supply_info.
BUG=chromium:405727
TEST=induced crashes in powerd, powerd_setuid_helper, and
power_supply_info, then forced crash reporting with
"FORCE_OFFICIAL=1 crash_sender" and checked that the
following crash reports had the expected data attached
in the "Files" section:
2f710954e30472b1 (powerd)
e7d985b7dbd9d158 (powerd_setuid_helper)
2213b0413fc9e408 (power_supply_info)
Change-Id: Icddb7d0b99eb19b95c656f8c06d8766733eaae28
Reviewed-on: https://chromium-review.googlesource.com/216020
Tested-by: Daniel Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Daniel Erat <derat@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 8b05c32b5dd3a95dde313b3b2ae4fb22ed91a8bd |
|
11-Jul-2013 |
Yuly Novikov <ynovikov@chromium.org> |
crash_collector: Collect i915_error_state for chrome crashes
Since crash_collector runs as chronos for chrome crashes,
it doesn't have permission to read i915_error_state.
Switch to getting it from debugd instead of reading directly.
Also, collect it for all chrome crashes.
BUG=chromium:219121
TEST=Kill chrome, see the log gathered. Uploaded report id 7cbae7f70da9bd3e.
Change-Id: Ic74abea2fc86b16c5a7f0f11df73137d93e5220c
Reviewed-on: https://gerrit.chromium.org/gerrit/61606
Reviewed-by: Albert Chaulk <achaulk@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Tested-by: Yuly Novikov <ynovikov@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 5f23bbb37e95913495d28a9707f198175dea4ac4 |
|
16-Apr-2013 |
Yufeng Shen <miletus@chromium.org> |
Add support for sending Atmel TP/TS error message
This adds the support that when Pixel touchscreen/trackpad driver
atmel_mxt_ts is misbehaving, e.g. failed to update firmware, failed
to read messages from the chip, trigger crash reporter to send system
logging message for further debugging.
We also follow the policy that, for atmel/cypress logs, we only fetch
the last 30s of the logs.
BUG=chromium:226186
TEST=1. On Pixel, replace the touchscreen firmware file
/opt/google/touch/firmware/162.0_1.1.170.bin
with an empty file with the same name
2. Force touchscreen firmware update
/opt/google/touch/scripts/chromeos-touch-firmware-update.sh -d atmel_mxt_ts -f -n maxtouch-ts.fw
3. After the firmware update fails, check crash report exists at
/var/spool/crash/change__i2c_atmel_mxt_ts.XXX
4. Check that the log contains only 30s of entries with "atmel" keyword.
Change-Id: If46a575491378405e60ad1ccbd39026ae6bf2033
Reviewed-on: https://gerrit.chromium.org/gerrit/48239
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Will Drewry <wad@chromium.org>
Commit-Queue: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| ebb86ae82e7ed843683fd6b3502f669945be1c37 |
|
16-Jan-2013 |
Yufeng Shen <miletus@chromium.org> |
crash-reporter: Add rule to collect touch event log
We are having a daemon touch_noise_monitor which periodically dump
touch event logs to /var/log/touch_event.log. Adding this matching
rule to collect the logs.
BUG=chrome-os-partner:17244
TEST=Made fake touch event /var/log/touch_event.log and call
/sbin/crash_reporter --udev=SUBSYSTEM=TouchEvent to generate
crash report.
Change-Id: Ic2eaea021a3eef31f48c92688600171db961c09f
Reviewed-on: https://gerrit.chromium.org/gerrit/41325
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Commit-Queue: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 0b783111866ed6bc660717b2537c448e3b3e6e57 |
|
20-Dec-2012 |
Yufeng Shen <miletus@chromium.org> |
crash-reporter: Add rule to collect touch noise logs
We are having a daemon touch_noise_monitor which can monitor
raw touch device events and when identifying noise pattern, it
will call crash reporter to upload relevant touch logs. Adding
this matching rule to make this happen.
BUG=chrome-os-partner:16788
TEST=Made fake touch noise happen and check that crash reported
as reportid c34d76e413aa87ee
Change-Id: I2fa9a32d97a3f31f183623bd44cb3eb8f2436878
Reviewed-on: https://gerrit.chromium.org/gerrit/40014
Commit-Queue: Yufeng Shen <miletus@chromium.org>
Reviewed-by: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| ed61be67b0845a76f7347171a5aa780d2ce88028 |
|
06-Dec-2012 |
Michael Krebs <mkrebs@chromium.org> |
crash-reporter: Collect i915 error state for chrome crashes
Add in the i915 error state as a log file in "chrome" crash reports. "chrome"
isn't normally reported through crash_reporter, so this will only kick in where
a developer has explicitly changed a machine to report them as such.
Because the output can be quite large (as we saw with udev crash reports), the
log is compressed before uploading. Although the file attached to the crash
report will have a ".log" extension, it will actually have been gzip'ed.
BUG=chromium-os:36979
TEST=Tested same config with "sleep" command:
crash/reportdetail?reportid=f429dbcaee7494be
Change-Id: I618a4364dcdd751852a69a79452272b7cf5e61f8
Reviewed-on: https://gerrit.chromium.org/gerrit/39271
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| bbda0787c9d84b577995e9d44039681ed9d66fd4 |
|
05-Nov-2012 |
Yufeng Shen <miletus@chromium.org> |
crash-reporter: Add udev rule to collect cyapa trackpad logs
Add the udev rule that when trackpad driver cyapa detects abnormal
behavior and fired uevent, additional logs from system logs are
collected.
BUG=chromium-os:35169
TEST=Made fake cyapa uevent and checked that logs are generated
in /var/spool/crash
Change-Id: I7ebabd729e6ce362b6f5db12c7cff38ed75c9792
Reviewed-on: https://gerrit.chromium.org/gerrit/37376
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| bc2d7dde163e0a2bbb7a122053620a4bddcd0411 |
|
13-Sep-2012 |
Michael Krebs <mkrebs@chromium.org> |
crash-reporter: Don't send dmesg output with internal crash_reporter reports
Seeing as kernel crashes no longer include dmesg output, we probably
shouldn't either. This is for crash reports with signature
"crash_reporter-user-collection".
BUG=chromium-os:34389
TEST=Ran logging_UserCrash autotest
CQ-DEPEND=I813a711c3557227cc17a58be8f960bfe569722bc
Change-Id: I52debf6d8ad32132d3b64c7f313f306b26287dd1
Reviewed-on: https://gerrit.chromium.org/gerrit/33167
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| f70060c5e610ed0aa648dcb6aaea5d859834b8ba |
|
10-Apr-2012 |
Simon Que <sque@chromium.org> |
Add udev event-based crash reporting
This allows crash_reporter to handle nonfatal errors from the kernel
passed thru udev events. There is a udev .rules file for invoking crash
reporter. Currently it supports DRM error info logging.
BUG=chrome-os-partner:6492
TEST=Run:
"crash_reporter --udev=ACTION=change:KERNEL=card0:SUBSYSTEM=drm"
Check that a card0-drm log file has been created under /var/spool/crash
Change-Id: I05a1d508e5446988575b0c1924878b8e36ae46bb
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/10618
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 557bf456f7e58ad068ba13339b0877a4c6bc37a1 |
|
15-Mar-2012 |
Ben Chan <benchan@chromium.org> |
Update crash_reporter_logs.conf to collect log files for cros-installer.
BUG=chromium-os:27821
TEST=emerge crash-reporter and verified the updated crash_reporter_logs.conf is installed.
Change-Id: Id2b7de30b36eaa57e6251261d8bca6810d5e8b82
Reviewed-on: https://gerrit.chromium.org/gerrit/18181
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
/system/core/crash_reporter/crash_reporter_logs.conf
|
| c046f57ef36b14d01e49ae004c85bc7095a58430 |
|
07-Apr-2011 |
Michael Krebs <mkrebs@google.com> |
Revert "Revert "crash-reporter: Don't send ps command lines with crash reporter""
This reverts commit 59d8695734dac2ce70b17d2a58049083e65e997d.
My original commit did not actually break anything, so this just puts it back.
BUG=chromium-os:13576
TEST=unit tests, logging_{UserCrash,CrashSender} autotests
Review URL: http://codereview.chromium.org/6765017
Change-Id: I5b9ebb2b210b86fb4efaf49c71dcd2562805c973
/system/core/crash_reporter/crash_reporter_logs.conf
|
| c7dcf3f52c0fda0cbcc5a17c961a3601899632ee |
|
28-Mar-2011 |
Michael Krebs <mkrebs@google.com> |
Revert "crash-reporter: Don't send ps command lines with crash reporter"
This reverts commit 78599c9f195a9c324d2b0eb5a048b677e6a4229c.
BUG=chromium-os:13576
TEST=
Review URL: http://codereview.chromium.org/6765002
Change-Id: I2c110e13199cc6d3741fa030065dbb405c2a049a
/system/core/crash_reporter/crash_reporter_logs.conf
|
| ec951c7613876a1bb808c721fdd9e10fc2940021 |
|
25-Mar-2011 |
Michael Krebs <mkrebs@google.com> |
crash-reporter: Don't send ps command lines with crash reporter
When unable to generate a crash, don't show the commands' arguments with
'ps' because they may contain PII.
Change-Id: I1e2f40e59535f4de08f43012727ab8e92bad8a0d
BUG=chromium-os:13206
TEST=unit tests, logging_UserCrash autotest
Review URL: http://codereview.chromium.org/6722017
/system/core/crash_reporter/crash_reporter_logs.conf
|
| 1b8fe015585c0b966d5240b8e22eba1af8c69e88 |
|
25-Jan-2011 |
Ken Mixter <kmixter@chromium.org> |
crash-reporter: Add diagnostics to help diagnose failures in the wild
We add logging messages that are generated during invocation of core2md, but we also enable sending arbitrary system info based on the configuration file. In this case we add the list of running processes, meminfo, and dmesg.
Change-Id: Ifdf29b89dd60d56349fa39095d2aa07f6b5e2de2
BUG=chromium-os:6299,chromium-os:9345
TEST=UserCrash, unit tests
Review URL: http://codereview.chromium.org/6297004
/system/core/crash_reporter/crash_reporter_logs.conf
|
| c4e01cc146d67d8bb7e2c2764eb3b9403873ed3f |
|
10-Jan-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Change path from /home/autotest to /usr/local/autotest.
Additional change for the relocation of Autotest from /home/autotest to /usr/local/autotest. See http://codereview.chromium.org/6090004/
Change-Id: I2995fdc76f56d4efbb6450d4a7da3adc321eae91
BUG=chromium-os:10799
TEST=Will test as whole with rest of /usr/local changes.
Review URL: http://codereview.chromium.org/5964016
/system/core/crash_reporter/crash_reporter_logs.conf
|
| c49dbd4775986f32b2f09659595f9f28ef7f6b44 |
|
15-Dec-2010 |
Ken Mixter <kmixter@chromium.org> |
crash-reporter: Capture and send recent update_engine logs when it crashes
We also disallow more than 4 nested crashes. This way we know if core2md crashes for instance, but not if crash_reporter crashes while handling the core2md crash that came from crash_reporter. Note that the kernel does not know about parent/child process relationships, it just counts concurrent handling, so it is possible that some of many crashing processes will be discarded.
See crash report id 473c22ed428d33a9 for an example report with update_engine logs.
Change-Id: I9ff9f03a94dc87d2d42840511c2e5e42ee37cea8
BUG=9176
TEST=UserCrash,CrashSender,unit tests
Review URL: http://codereview.chromium.org/5814001
/system/core/crash_reporter/crash_reporter_logs.conf
|