From: Bryan Christ <bryan@mediafire.com>
To: linux-mm@kvack.org
Subject: PROBLEM: Kernel panics on do_raw_spin_lock()
Date: Mon, 23 May 2011 13:33:00 -0500 [thread overview]
Message-ID: <1306175580.2481.16.camel@tuxdev64> (raw)
Kernel seems to frequently panic with RIP at do_raw_spin_lock(). I
assume this might be vma related since the trace often implicates
vma_merge() and friends.
Linux version 2.6.38.6-26.rc1.fc14.x86_64
Module Size Used by
xfs 700603 5
exportfs 3440 1 xfs
p4_clockmod 4486 0
freq_table 3963 1 p4_clockmod
speedstep_lib 4847 1 p4_clockmod
ipv6 288342 26
iTCO_wdt 11592 0
shpchp 24810 0
iTCO_vendor_support 2634 1 iTCO_wdt
serio_raw 4442 0
i2c_i801 9293 0
i5000_edac 8340 0
edac_core 41090 3 i5000_edac
i5k_amb 4882 0
ioatdma 45294 9
e1000e 200202 0
ppdev 7868 0
parport_pc 21303 0
parport 31338 2 ppdev,parport_pc
microcode 18276 0
dca 5854 1 ioatdma
ext2 59952 1
usb_storage 45607 1
uas 7768 0
radeon 696138 1
ttm 55897 1 radeon
drm_kms_helper 27729 1 radeon
drm 189462 3 radeon,ttm,drm_kms_helper
i2c_algo_bit 5062 1 radeon
i2c_core 25745 5
i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
Screenshots of panic:
http://www.mediafire.com/imageview.php?quickkey=hnd1dedna9bed65
http://www.mediafire.com/imageview.php?quickkey=n86366d44i7mlx4
http://www.mediafire.com/imageview.php?quickkey=0sgzfd91dvl3jhl
http://www.mediafire.com/imageview.php?quickkey=zwly9x5c4zg28dn
I will be glad to provide as much information as I can. Just let me
know what is needed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2011-05-23 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1306175580.2481.16.camel@tuxdev64 \
--to=bryan@mediafire.com \
--cc=linux-mm@kvack.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