From: <bug...@bu...> - 2005-12-28 18:33:30
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From jfr...@ho... 2005-12-28 10:23 ------- I had posted 2 corresponding bug reports 3 weeks ago at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174906 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174975 The bug might be furthermore related to: https://bugs.freedesktop.org/show_bug.cgi?id=3835 The good news is that by building "drm.ko" and "savage.ko" kernel modules from current "savage-2005xxxx-linux.i386.tar.bz2 snapshots corresponding to "DRM" version 1.0.1 instead of 1.0.0 of the current Linux kernel, the issue is settled. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2005-12-29 17:04:50
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 avi...@ce... changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |PATCH_ALREADY_AVAILABLE ------- Additional Comments From avi...@ce... 2005-12-29 08:54 ------- Tried http://dri.freedesktop.org/snapshots/savage-20051220-linux.i386.tar.bz2 and the kernel oops went away. I am glad that this was solved, but also annoyed that this drm version is not being pushed into the main kernel tree. Thanks anyway for the links. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2005-12-30 10:28:54
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From ai...@li... 2005-12-30 02:19 ------- It is going into the kernel.. I'm just not sure whats changed.. my git tree might have it already in it... the savage driver hasn't moved in 4 months or so... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2005-12-30 10:36:39
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From jfr...@ho... 2005-12-30 02:26 ------- I have found out that not the very update to "DRM" version 1.0.1 keeps "Mesa" from segfaulting. As a matter of fact, what made the difference for me was loading the "savage.ko" module explicitly. Appending "modprobe savage" to "rc.sysinit" makes it impossible for me to reproduce the segmentation faults reported earlier. Before, I loaded the compiled "savage.ko" built from current "DRI" snapshots and corresponding to "DRM" version 1.0.1 via "insmod". However, even loading the original kernel module delivered as part of kernel 2.6.14-1.1653_FC4 and corresponding to "DRM" version 1.0.0 makes the reported behaviour disappear. When you tried out the new "DRM" version, did you load the module "by hand" via "insmod" or did you copy it to "/lib/modules/`uname -r`/kernel/drivers/char/drm"? As pointed out above, even the current module works. At least when you "modprobe" it in "rc.sysinit" as I did. Setting the status to "RESOLVED PATCH_ALREADY_AVAILABLE" is hence a bit premature because after updating the kernel "DRM", one might still encounter the reported problem. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2005-12-30 12:24:48
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From jfr...@ho... 2005-12-30 04:14 ------- Essentially the same problem occurs after bootig from a Ubuntu 6.04 alpha Live CD. The (modular) X server release is 7.0.0 RC4. The bug is thus not Red Hat specific. I have been able to trigger one segmentation fault aborting the X session. Most of the time however, the "glxgears" window simply remains black. After a couple of seconds, "glxgears" aborts. There is an error message in "dmesg": [4295522.874000] [drm:savage_bci_wait_event_shadow] *ERROR* failed! which points a the origin of the trouble. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2005-12-30 13:18:17
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From jfr...@ho... 2005-12-30 05:08 ------- After rebuilding "drm.ko" and "savage.ko" from the current "DRI" snapshot "savage-20051220-linux.i386.tar.bz2" and pushing the kernel modules into /lib/modules/`uname -r`/kernel/drivers/char/drm, I am not able to reproduce kernel oopses or segmentation faults as before. This seems to indicate that a corresponding kernel tree update might actually resolve the issue. In contrast with previous cases, I have spotted an aditional entry in "/var/log/dmesg" which reads: [drm] Used old pci detect: framebuffer loaded Hopefully, integration of the "dri.freedesktop.org" branch into the kernel tree and subsequent modifications won't alter the status quo. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@bu...> - 2006-01-14 11:52:32
|
http://bugzilla.kernel.org/show_bug.cgi?id=5784 ------- Additional Comments From jfr...@ho... 2006-01-14 03:41 ------- Seems to have been fixed in kernel 2.6.15-git9 thanks to a "DRM" update to version 1.0.1 by D. Airlie. Please check! ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |