Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/4] tools: intel_gpu_abrt collecting more useful info
Date: Thu, 13 Dec 2012 14:11:22 -0200	[thread overview]
Message-ID: <1355415084-8431-2-git-send-email-rodrigo.vivi@gmail.com> (raw)
In-Reply-To: <1355415084-8431-1-git-send-email-rodrigo.vivi@gmail.com>

---
 tools/intel_gpu_abrt | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/tools/intel_gpu_abrt b/tools/intel_gpu_abrt
index b243a5f..fe3684d 100755
--- a/tools/intel_gpu_abrt
+++ b/tools/intel_gpu_abrt
@@ -8,6 +8,9 @@ get(){
 	cp -a ${@:1:$#-1} $tardir/${@:$#} 2>/dev/null
     fi
 }
+
+igtdir=`dirname $0`
+
 if [ -d /debug/dri ] ; then
 	debugfs_path=/debug_dri
 fi
@@ -38,6 +41,7 @@ get $i915_debugfs/* debugfs
 get /sys/module/i915/parameters/* mod_opts
 
 mkdir $tardir/X
+xrandr --verbose > $tardir/X/xrandr
 get /var/log/Xorg.0.log X
 get /var/log/Xorg.0.log.old X
 get /etc/X11/xorg.conf X
@@ -46,6 +50,14 @@ get /etc/X11/xorg.conf.d/ X
 dmesg > $tardir/dmesg
 lspci -nn > $tardir/lspci
 
+$igtdir/intel_reg_dumper > $tardir/intel_reg_dumper.txt
+$igtdir/intel_bios_dumper $tardir/intel_bios_dump
+$igtdir/intel_stepping > $tardir/intel_stepping
+
+echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
+cat /sys/devices/pci0000:00/0000:00:02.0/rom > $tardir/vbios.dump
+echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom
+
 (cd $tmpdir; tar -c intel_gpu_abrt ) > intel_gpu_abrt.tar
 
 rm $tmpdir -Rf
-- 
1.7.11.7

  reply	other threads:[~2012-12-13 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 16:11 [PATCH 1/4] tools: intel_gpu_abrt "get" function Rodrigo Vivi
2012-12-13 16:11 ` Rodrigo Vivi [this message]
2012-12-13 16:11 ` [PATCH 3/4] tools: intel_gpu_abrt checking for root access Rodrigo Vivi
2012-12-13 16:11 ` [PATCH 4/4] tools: intel_gpu_abrt bug report template Rodrigo Vivi
2012-12-13 17:16   ` Daniel Vetter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1355415084-8431-2-git-send-email-rodrigo.vivi@gmail.com \
    --to=rodrigo.vivi@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox