Better information how to provide kernel debugging logs.

1 files changed, 1 insertions, 1 deletions

diff --git a/RH_Data-packages.json b/RH_Data-packages.json
index 50ab1b1..840b5d9 100644
--- a/RH_Data-packages.json
+++ b/RH_Data-packages.json
@@ -188,7 +188,7 @@
         "noDebugSymbols": "Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).\n\nUnfortunately, we cannot use this backtrace.\n\nClosing as INSUFFICIENT_DATA.",
         "noTriageString": "There is nothing to triage here.\n\nSwitching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.",
         "getAbrtReproInfo": "Reporter, could you please describe us what you have done to get to this point, and how we can reproduce this issue here? Is there anything special about your system, network, configuration which we need to replicate here in order to reproduce your problem please?",
-        "getLogsString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.\n\nPlease attach\n\n* your X server config file (/etc/X11/xorg.conf, if available),\n* output of the dmesg command,\n* system log (/var/log/messages), and\n* X server log file (/var/log/Xorg.*.log)\n\nto the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThanks in advance.",
+        "getLogsString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.\n\nPlease add drm.debug=0x04 to the kernel command line, restart computer, and attach\n\n* your X server config file (/etc/X11/xorg.conf, if available),\n* output of the dmesg command,\n* system log (/var/log/messages), and\n* X server log file (/var/log/Xorg.*.log)\n\nto the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThanks in advance.",
         "getLogsLiveCDString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue.\n\nIf the anaconda crashes during the switching to the graphic mode, most likely the problem lies in Xorg support for your graphics chip. There are couple of options how we can obtain information necessary for resolving the issue.\n\nIf the computer is not completely frozen when installation fails, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, somewhere on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.\n\nIf the computer is completely useless after installation fails, you can also install Fedora with a VESA mode driver (see https://fedoraproject.org/wiki/Documentation_Beats_Installer\nfor more information on that). Then after successful installation you can collect /var/log/anaconda.xlog, /var/log/Xorg.0.log, and the output of the program dmesg instead.\n\nOr you can install Fedora in a text mode completely, and then start X after that. If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThank you very much in advance.",
         "getFirefoxBacktraceString": "Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.\n\nFirst of all, could we get output of the command\n\n\u0009rpm -qa \\*xulrun\\* \\*firefox\\* \\*mozilla\\* \\*flash\\* \\*plugin\\*\n\nPlease also install firefox-debuginfo (debuginfo-install is from\nyum-utils package).\n\n\u0009debuginfo-install firefox\n\nThen run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run\n\n\u0009(gdb) thread apply all backtrace\n\nThis produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.\n\nPlease, install also valgrind (from valgrind package) and run\n\n\u0009valgrind --trace-children=yes --log-file=/tmp/firefox-valgrind-log.txt /usr/bin/firefox\n\n(that's one line command, browser breaking this line into two notwithstanding)\n\nPlease, attach the file /tmp/firefox-valgrind-log.txt to this bug as an attachment as well.\n\nWe will review this issue again once you've had a chance to attach this information.\n\nThanks in advance.",
         "noResponseString": "Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.\n\nUsers who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.\n\nClosing as INSUFFICIENT_DATA.",