Unable to analyse kernel crash dump

[selig]

My system crashes from time to time (approximately once in a couple of weeks) and I suspect the ath9k driver to be the culprit (because of the backtrace I see on the screen when the kernel panics). I set up kdump and was able to copy the /proc/vmcore file to disk after the kernel crash had occurred. But now, I am unable to debug it. I have the "kernel debugging" etc. options turned on in the kernel but invoking the crash utility gives me this error:

Code: Select all

# crash /boot/System.map-3.4.9-gr vmlinux /var/cache/torrents/vmcore 

crash 6.0.8
Copyright (C) 2002-2012  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...

                                                                       
crash: neither runqueue nor rq structures exist

I have also tried it without giving crash the System.map file, with the same result. Am I doing something wrong or is the crash dump unusable?

[Thistled]

Would I be correct to say if you try an older kernel (i.e. driver) this does not happen?