http://bugzilla.kernel.org/show_bug.cgi?id=7107
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED],
|
http://bugzilla.kernel.org/show_bug.cgi?id=7273
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugzilla.kernel.org/show_bug.cgi?id=6626
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=7767
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED],
|
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2007-01-31 02:46 ---
I've revisited this. Although a few things have changed since I last tested,
including updated (from Fedora Core 6 updates) libdrm, Mesa,
xorg-x11-server-Xorg,
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2007-01-31 02:55 ---
OK, thanks. Can you please close off the bug if/when you think that's
appropriate?
--- You are receiving this mail because: ---
You are the assignee for the
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2007-01-31 03:18 ---
Sure, I'll give it to the end of the day.
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=7273
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-01-31 14:42 ---
it should all be synced up for ages, I've no outstanding differences between the
2.6.20 savage and drm git tree that I can see with a quick look.
Can you send me a
http://bugzilla.kernel.org/show_bug.cgi?id=6893
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugzilla.kernel.org/show_bug.cgi?id=7847
--- Additional Comments From [EMAIL PROTECTED] 2007-01-18 01:07 ---
It's possible that this bug happened because I had a device plugged into the
UHCI root hub that was sharing its IRQ with the Radeon 9200. It's not as if I
haven't
http://bugzilla.kernel.org/show_bug.cgi?id=7847
Summary: Radeon 9200 DRI driver IRQ, but no-one cared
Kernel Version: 2.6.18.6
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where
http://bugzilla.kernel.org/show_bug.cgi?id=7767
Summary: No hardware rendering for SuperSavage/IXC 64 and Xorg
7.2 RC3
Kernel Version: 2.6.20-rc3-git3
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter:
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-01-04 00:27 ---
Sorry, the correct link is [git://anongit.freedesktop.org/git/mesa/drm].
--- You are receiving this mail because: ---
You are the assignee for the bug, or are
http://bugzilla.kernel.org/show_bug.cgi?id=7661
--- Additional Comments From [EMAIL PROTECTED] 2006-12-11 08:03 ---
If this still happens with recent releases of X.org and Mesa, it might be better
reporting a bug against Mesa at http://bugs.freedesktop.org with at least full X
config
http://bugzilla.kernel.org/show_bug.cgi?id=7661
Summary: R200 lockup
Kernel Version: 2.6.19-rc5
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this bug did *NOT* occur: None
http://bugzilla.kernel.org/show_bug.cgi?id=7606
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=7606
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- You are receiving this
http://bugzilla.kernel.org/show_bug.cgi?id=7606
Summary: The SiS DRI driver isn't compiled as a module during the
kernel 2.6.19 compilation
Kernel Version: 2.6.19
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=7606
--- Additional Comments From [EMAIL PROTECTED] 2006-11-30 20:49 ---
Does this fix?
--- a/drivers/char/drm/drm_sman.c~drm-sis-linkage-fix
+++ a/drivers/char/drm/drm_sman.c
@@ -162,6 +162,7 @@ drm_sman_set_manager(drm_sman_t * sman,
http://bugzilla.kernel.org/show_bug.cgi?id=4607
--- Additional Comments From [EMAIL PROTECTED] 2006-11-18 12:39 ---
It seems like I can avoid the crashes with Option BusType PCI alone. Using
Option DmaMode None alone helps for glxgears, but crashes with other 3D
screensavers.
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2006-10-26 07:04 ---
The debian 2.6.18 kernel gave me a nice message yesterday stating that the AGP
aperture was too small. So, I went into the BIOS and made the aperture 64MB. X
now works
http://bugzilla.kernel.org/show_bug.cgi?id=7325
Summary: drm compile errors
Kernel Version: 2.6.19-rc1-git6
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this bug did not
http://bugzilla.kernel.org/show_bug.cgi?id=7325
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=4607
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
|
http://bugzilla.kernel.org/show_bug.cgi?id=7273
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
|
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2006-10-06 10:19 ---
Created an attachment (id=9173)
-- (http://bugzilla.kernel.org/attachment.cgi?id=9173action=view)
MSI K8T Master2-Far (VIA K8T8000) testgart output (dual Opteron 244s)
http://bugzilla.kernel.org/show_bug.cgi?id=7273
--- Additional Comments From [EMAIL PROTECTED] 2006-10-06 13:11 ---
$ cat /proc/mtrr
reg00: base=0x ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x7ff0 (2047MB), size= 1MB: uncachable, count=1
reg02:
http://bugzilla.kernel.org/show_bug.cgi?id=4602
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=4602
[EMAIL PROTECTED] changed:
What|Removed |Added
OtherBugsDependingO||7216
nThis|
http://bugzilla.kernel.org/show_bug.cgi?id=6870
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=7107
Summary: Kernel Oops on drm modules unload
Kernel Version: 2.6.17.11
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this bug
http://bugzilla.kernel.org/show_bug.cgi?id=6677
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=6946
--- Additional Comments From [EMAIL PROTECTED] 2006-08-03 01:50 ---
This is an X radeon driver issue that was fixed in the xf86-video-ati releases
6.5.8 (for X.Org 7.0) and 6.6.0 (for X.Org 7.1).
--- You are receiving this mail
http://bugzilla.kernel.org/show_bug.cgi?id=6946
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-08-03 13:21 ---
Is this bug fixed? shouldn't it be closed?
Boris, in your setup the video card is not sharing the irq with the ide device
and you are using a nvidia binary module
http://bugzilla.kernel.org/show_bug.cgi?id=6946
Summary: X Server not starting in about 1 of 7 starts
Kernel Version: 2.6.18-rc3-git1
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel
http://bugzilla.kernel.org/show_bug.cgi?id=6946
--- Additional Comments From [EMAIL PROTECTED] 2006-08-02 12:13 ---
Created an attachment (id=8675)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8675action=view)
Trace of two situtation where x hangs on loading
X server stops
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-30 02:50 ---
Created an attachment (id=8643)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8643action=view)
strace -e open,ioctl mythfrontend mythfrontend.strace
didn't know
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 11:56 ---
Here is the oops with a 2.6.18-rc2 with the patch applied:
Jul 29 20:48:56 tyron kernel: mtrr: 0xe000,0x800 overlaps existing
0xe000,0x200
Jul 29
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 12:02 ---
By the way, I hit 'Edit' on the 'gathering info patch' out of curiosity, but
didn't (mean to) modify it. Now it shows as edited.
I had to clean up the patch from
http://bugzilla.kernel.org/show_bug.cgi?id=6893
[EMAIL PROTECTED] changed:
What|Removed |Added
Attachment #8635 is|0 |1
obsolete|
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 12:36 ---
Created an attachment (id=8638)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8638action=view)
corrected patch
Sure, I am an asshole, it was colored patch.
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 12:37 ---
Anyway, I need whole dmesg after applying the patch, because I need to know
lines above your oops post.
--- You are receiving this mail because: ---
You are
http://bugzilla.kernel.org/show_bug.cgi?id=6893
[EMAIL PROTECTED] changed:
What|Removed |Added
Attachment #8638 is|0 |1
obsolete|
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 12:40 ---
Created an attachment (id=8639)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8639action=view)
finally the correct patch
--- You are receiving this mail
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 14:02 ---
Created an attachment (id=8641)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8641action=view)
here is the full dmesg corresponding to the last oops
--- You
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-29 15:21 ---
Cool, no init called, seems to be wrong in userspace, could you 'strace -e
open,ioctl' it?
--- You are receiving this mail because: ---
You are the assignee
http://bugzilla.kernel.org/show_bug.cgi?id=6893
--- Additional Comments From [EMAIL PROTECTED] 2006-07-25 12:05 ---
Here comes an oops #1 (since it is non-locking, I guessed I'd send any in the
first place). Kernel config was attached. Please note that I also tried without
http://bugzilla.kernel.org/show_bug.cgi?id=6893
Summary: kernel oops with radeon and mythfrontend
Kernel Version: 2.6.18-rc2
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where
http://bugzilla.kernel.org/show_bug.cgi?id=6893
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugzilla.kernel.org/show_bug.cgi?id=6865
Summary: kernel BUG at mm/swap.c:52
Kernel Version: 2.6.16-r12
Status: NEW
Severity: low
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this bug did not
http://bugzilla.kernel.org/show_bug.cgi?id=6865
--- Additional Comments From [EMAIL PROTECTED] 2006-07-19 04:32 ---
[ cut here ]
kernel BUG at mm/swap.c:52!
invalid opcode: [#1]
PREEMPT SMP
Modules linked in: fglrx
CPU:0
EIP:0060:[c014ddf9]
http://bugzilla.kernel.org/show_bug.cgi?id=6865
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=6870
Summary: kernel-2.6.17 on a P-IV locks up the machine: problem
with
Kernel Version: 2.6.17
Status: NEW
Severity: high
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL
http://bugzilla.kernel.org/show_bug.cgi?id=6110
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=6677
Summary: radeon driver with mobility radeon X600 SE
Kernel Version: 2.6.17-rc6
Status: NEW
Severity: low
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this
http://bugzilla.kernel.org/show_bug.cgi?id=6626
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |DEFERRED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 23:40 ---
This is most likely an issue with the OpenGL driver, or possibly the X driver.
Please check the Mesa and xorg products at http://bugs.freedesktop.org and file
a new bug
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-06-01 05:32 ---
Michel:
Thanks for your help. :)
I started with the bugtracker mentioned (strangely searching for bugtracker
xorg with google did not give any links to this). There
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-06-01 10:39 ---
Well, o.k. The new driver does not help. Just tried Enemy Territory and after 5
minutes the system froze again.
Now I will try disabling dynamicclocks (after already
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:36 ---
Created an attachment (id=8227)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8227action=view)
kern.log from the time of the last crash
--- You are receiving
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:37 ---
Created an attachment (id=8228)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8228action=view)
syslog from the time of the last crash
--- You are receiving
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:37 ---
Created an attachment (id=8229)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8229action=view)
/var/log/messages from the time of the last crash
--- You are
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:39 ---
Created an attachment (id=8230)
-- (http://bugzilla.kernel.org/attachment.cgi?id=8230action=view)
dmesg -s 100 (however, only starting after the last crash)
http://bugzilla.kernel.org/show_bug.cgi?id=6626
--- Additional Comments From [EMAIL PROTECTED] 2006-05-31 00:39 ---
Dmesg is a bit late for the last freeze as the ring buffer has run out already.
I still attach the output, but the first message is already after the restart of
the
http://bugzilla.kernel.org/show_bug.cgi?id=6626
Summary: Infrequent system freezes when using OpenGL on ATI
radeon driver r100
Kernel Version: 2.6.16
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter:
http://bugzilla.kernel.org/show_bug.cgi?id=6626
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugzilla.kernel.org/show_bug.cgi?id=5641
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=6110
--- Additional Comments From [EMAIL PROTECTED] 2006-02-22 13:30 ---
(WW) I810(0): i830 Kernel module detected, Use the i915 Kernel module instead,
aborting DRI init.
It's telling you what to do, use the 1915 module. So do not
http://bugzilla.kernel.org/show_bug.cgi?id=6110
Summary: mtrr: base(0xf002) is not aligned
Kernel Version: 2.6.16-rc3
Status: NEW
Severity: high
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Distribution: Debian testing
http://bugzilla.kernel.org/show_bug.cgi?id=6110
--- Additional Comments From [EMAIL PROTECTED] 2006-02-20 13:49 ---
are you building your own kernels? if so then you are using the wrong DRM driver
more than likely... you have the i830 driver loaded when it should be the i915,
this
http://bugzilla.kernel.org/show_bug.cgi?id=6110
--- Additional Comments From [EMAIL PROTECTED] 2006-02-20 14:13 ---
Created an attachment (id=7423)
-- (http://bugzilla.kernel.org/attachment.cgi?id=7423action=view)
kernel log information and tip
usefull info:
Feb 20 20:06:01 prog3
http://bugzilla.kernel.org/show_bug.cgi?id=6110
--- Additional Comments From [EMAIL PROTECTED] 2006-02-20 15:19 ---
Looks like something acquired agp but did not release it (drm?) which caused
intelfb to fail.
You can try these:
1. Make sure that intelfb gets loaded first (ie by
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-17 02:55 ---
Created an attachment (id=7381)
-- (http://bugzilla.kernel.org/attachment.cgi?id=7381action=view)
patch to invoke pci_enable_device() when using old PCI detect
If
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-17 05:12 ---
i just tried using pci=routeirq and it works
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-17 20:22 ---
this isn't a kernel bug if you are using drivers from DRM CVS.. if you are using
DRM CVS drivers please close this bug, I've check an always enavble device into
DRM
http://bugzilla.kernel.org/show_bug.cgi?id=6082
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugzilla.kernel.org/show_bug.cgi?id=6082
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|when making use of the drm |when making use of the drm
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-16 07:00 ---
Created an attachment (id=7367)
-- (http://bugzilla.kernel.org/attachment.cgi?id=7367action=view)
output of kernel.logs for this kernel (runing with the radeon module)
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-16 06:33 ---
/proc/interrupts
CPU0
0:1061648IO-APIC-edge timer
1: 15411IO-APIC-edge i8042
8: 4IO-APIC-edge rtc
9: 2
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-16 06:51 ---
with the DRM module loaded i get this /proc/interrupts:
CPU0
0: 98559IO-APIC-edge timer
1: 1939IO-APIC-edge i8042
8: 4
http://bugzilla.kernel.org/show_bug.cgi?id=6082
--- Additional Comments From [EMAIL PROTECTED] 2006-02-16 08:16 ---
Hi,
I have the same with r300 and realtek r8186 (onboard) network card.
Here is dmesg after X having started (probed drm and radeon modules):
http://bugzilla.kernel.org/show_bug.cgi?id=5641
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- You are receiving
http://bugzilla.kernel.org/show_bug.cgi?id=5641
--- Additional Comments From [EMAIL PROTECTED] 2006-01-19 02:30 ---
you didn't upgrade X.org by any chance at some point, or does going back to
2.6.13.1 work with your current X setup? do you get direct rendering with
2.6.13.1?
http://bugzilla.kernel.org/show_bug.cgi?id=5784
--- Additional Comments From [EMAIL PROTECTED] 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: ---
http://bugzilla.kernel.org/show_bug.cgi?id=5784
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=5784
--- Additional Comments From [EMAIL PROTECTED] 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
http://bugzilla.kernel.org/show_bug.cgi?id=5784
--- Additional Comments From [EMAIL PROTECTED] 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
http://bugzilla.kernel.org/show_bug.cgi?id=5784
--- Additional Comments From [EMAIL PROTECTED] 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...
http://bugzilla.kernel.org/show_bug.cgi?id=5784
--- Additional Comments From [EMAIL PROTECTED] 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
http://bugzilla.kernel.org/show_bug.cgi?id=5784
Summary: savage DRI: kernel oops when running glxgears in second
X.org session
Kernel Version: 2.6.15-rc6
Status: NEW
Severity: high
Owner: [EMAIL PROTECTED]
Submitter:
http://bugzilla.kernel.org/show_bug.cgi?id=5641
--- Additional Comments From [EMAIL PROTECTED] 2005-11-25 07:34 ---
Exactly the same problem in 2.6.14.3.
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=5641
Summary: Xinerama blocks chipset and GLX fails on Asus
M2400N/Centrino/855GM
Kernel Version: 2.6.14.2
Status: NEW
Severity: high
Owner: [EMAIL PROTECTED]
Submitter:
http://bugzilla.kernel.org/show_bug.cgi?id=2754
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 02:54 ---
Sorry, i can't test it.
I changed notebook model and vendor, so i can't help with report in
future.
Thanks
--
sign: Josef Rysanek (ailas) [EMAIL PROTECTED]
www:
http://bugzilla.kernel.org/show_bug.cgi?id=2754
--- Additional Comments From [EMAIL PROTECTED] 2005-08-20 09:27 ---
It looks like this only occurs with the Radeon in 1x mode while doing FID/VID
changes. Both 2x and 4x modes will lockup the system during a FID/VID but 1x
mode will
http://bugzilla.kernel.org/show_bug.cgi?id=3834
--- Additional Comments From [EMAIL PROTECTED] 2005-08-08 03:56 ---
I;m assuming this issue is fixed.
Please reopen this bug if it's still present in recent kernels.
--- You are receiving this mail because: ---
You are the
http://bugzilla.kernel.org/show_bug.cgi?id=3834
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |REJECTED
Resolution|
http://bugzilla.kernel.org/show_bug.cgi?id=4354
[EMAIL PROTECTED] changed:
What|Removed |Added
Owner|[EMAIL PROTECTED] |[EMAIL PROTECTED]
http://bugzilla.kernel.org/show_bug.cgi?id=3834
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
601 - 700 of 785 matches
Mail list logo
