From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 32402] New: Oops associated with radeon_unpin_work_func
Date: Thu, 31 Mar 2011 23:13:04 GMT [thread overview]
Message-ID: <bug-32402-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=32402
Summary: Oops associated with radeon_unpin_work_func
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: smf.linux@ntlworld.com
Regression: No
If this system (LFS build) is left idle for several hours with xscreensaver
running(don't currently know which screen saver app. I am assuming one of the
Mesa 3D ones) the system will oops. The system is locked solid and there is no
trace in messages.old on reboot. The attached jpg is a photo of the screen at
system failure. I first noticed the problem in 2.6.38-rc8 but have waited until
now to report the problem in the hope of obtaining a more repeatable scenario.
Version info:
Xorg server 1.10.0
Xorg ati driver 6.14.1
libdrm-2.4.24
Mesa-7.10.1
Processor AMD Phenom(tm) II X4 940 Processor
Linux Andromeda 2.6.38.2 #1 SMP Mon Mar 28 22:17:13 BST 2011 i686 athlon-4 i386
GNU/Linux
Gnu C 4.6.0
Gnu make 3.81
binutils 2.21
util-linux 2.14.1
mount support
module-init-tools 3.5
e2fsprogs 1.41.4
Linux C Library 2.13
Dynamic linker (ldd) 2.13
Linux C++ Library 6.0.15
Procps 3.2.7
Net-tools 1.60
Kbd 1.15
Sh-utils 7.4
Modules Loaded md4 md5 hmac cryptomgr aead nls_cp437 cifs crypto_hash
crypto_algapi microcode nfs fscache nfsd lockd sunrpc exportfs fuse usbhid
firewire_ohci sr_mod sg firewire_core cdrom psmouse i2c_piix4 crc_itu_t button
vboxnetflt fifo splitter ohci_hcd ehci_hcd usbcore nls_base vboxnetadp
snd_hda_codec_hdmi snd_hda_codec_analog snd_hda_intel snd_hda_codec
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore brd loop
asus_atk0110 powernow_k8 processor thermal_sys mperf pata_atiixp vboxdrv sky2
rtc eeprom unix
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2011-03-31 23:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 23:13 bugzilla-daemon [this message]
2011-03-31 23:20 ` [Bug 32402] Oops associated with radeon_unpin_work_func bugzilla-daemon
2011-04-01 8:12 ` bugzilla-daemon
2011-04-04 22:59 ` bugzilla-daemon
2011-04-04 23:11 ` bugzilla-daemon
2011-04-04 23:14 ` bugzilla-daemon
2011-04-04 23:17 ` bugzilla-daemon
2011-04-06 14:26 ` bugzilla-daemon
2011-04-06 14:27 ` bugzilla-daemon
2011-04-07 7:38 ` bugzilla-daemon
2011-04-14 14:11 ` bugzilla-daemon
2011-04-16 21:08 ` bugzilla-daemon
2011-04-16 21:28 ` bugzilla-daemon
2011-05-19 13:04 ` bugzilla-daemon
2011-05-29 8:30 ` bugzilla-daemon
2011-05-29 8:30 ` bugzilla-daemon
2011-05-29 10:09 ` bugzilla-daemon
2011-05-29 10:24 ` bugzilla-daemon
2011-05-30 8:00 ` bugzilla-daemon
2011-06-14 11:21 ` bugzilla-daemon
2011-06-16 14:50 ` bugzilla-daemon
2011-06-16 14:50 ` bugzilla-daemon
2011-06-26 12:58 ` bugzilla-daemon
2011-07-10 23:14 ` bugzilla-daemon
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=bug-32402-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.