[Bug 12356] [i915 drm] irq 16: nobody cared with 2.6.28 kernel

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12356


p...@gentoo.org changed:

   What|Removed |Added

 Regression|0   |1




-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12356] New: [i915 drm] irq 16: nobody cared with 2.6.28 kernel

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12356

   Summary: [i915 drm] irq 16: nobody cared with 2.6.28 kernel
   Product: Drivers
   Version: 2.5
 KernelVersion: 2.6.28
  Platform: All
OS/Version: Linux
  Tree: Mainline
Status: NEW
  Severity: normal
  Priority: P1
 Component: Video(DRI)
AssignedTo: drivers_video-...@kernel-bugs.osdl.org
ReportedBy: p...@gentoo.org


Latest working kernel version: unknown since this is new PC
Distribution: Gentoo
Hardware Environment: ThinkPad X61 Tablet 7762-CTO
Software Environment: Gentoo Linux
Problem Description: 

This problem already was reported in number of places:
https://bugs.freedesktop.org/show_bug.cgi?id=18609
http://bugzilla.kernel.org/show_bug.cgi?id=12161
http://lkml.org/lkml/2008/12/2/115
http://marc.info/?l=linux-kernelm=122822444615724w=4

Although first two links state that this bug is fixes, I've checked and commit
that should report this problem is applied in 2.6.28 but bug is still there.

The problem is that sometimes (yea, probably high system loads increase
probability) I see the following in the kernel:

Jan  3 18:45:56 tablet irq 16: nobody cared (try booting with the irqpoll
option)
Jan  3 18:45:56 tablet Pid: 4587, comm: cc1plus Not tainted
2.6.28-gentoo-noswap #1
Jan  3 18:45:56 tablet Call Trace:
Jan  3 18:45:56 tablet IRQ  [802559b8] __report_bad_irq+0x30/0x7d
Jan  3 18:45:56 tablet [80255b0a] note_interrupt+0x105/0x16b
Jan  3 18:45:56 tablet [8025618e] handle_fasteoi_irq+0xa6/0xcf
Jan  3 18:45:56 tablet [8020dcb0] do_IRQ+0x75/0xe5
Jan  3 18:45:56 tablet [8020b866] ret_from_intr+0x0/0xa
Jan  3 18:45:56 tablet EOI 3handlers:
Jan  3 18:45:56 tablet [80440d68] (ahci_interrupt+0x0/0x45c)
Jan  3 18:45:56 tablet [803e3672] (i915_driver_irq_handler+0x0/0x1e2)
Jan  3 18:45:56 tablet Disabling IRQ #16

After that my system became very slow and unusable.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12161] [i915 drm] irq 16: nobody cared with latest git kernels

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12161


p...@gentoo.org changed:

   What|Removed |Added

 CC||p...@gentoo.org




--- Comment #3 from p...@gentoo.org  2009-01-04 00:02 ---
Rafael, since this problem is not fixed I've opened new bug 12356.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12174] No backlight control on Samsung x360

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12174





--- Comment #11 from m.he...@gmx.net  2009-01-04 06:09 ---
For the record:
This bug only affects kernel 2.6.28. With older versions the backlight can be
controled via /sys/class/backlight/NVID/brightness iirc. The NVID interface was
removed for 2.6.28.

The brightness keys don't send acpi commands, they send just normal keycodes
(if you bind some keycodes for it). If you wanna use them, configure your
windowmanager to.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12345] X on Intel 965GM hangs on console switch if compositing is enabled

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12345





--- Comment #1 from no...@gmx.net  2009-01-04 07:56 ---
Created an attachment (id=19641)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=19641action=view)
kernel log with drm debug=0x

drm log of:
start compiz - switch to console 1 - switch back to console 7 (X console)


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12345] X on Intel 965GM hangs on console switch if compositing is enabled

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12345





--- Comment #2 from no...@gmx.net  2009-01-04 08:36 ---
Created an attachment (id=19642)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=19642action=view)
patch to remember the vblank enable state between leavevt and entervt

This patch remembers the vblank enable state for the two pipes between leavevt
and entervt. 

This fixes the problem for me but I don't know if its the right thing to do
since I have little idea how the drm stuff should work.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] New: WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359

   Summary: WARNING and other intel modesetting problems
   Product: Drivers
   Version: 2.5
 KernelVersion: 2.6.29-7d3b56ba37a95f1f370f50258ed3954c304c524b
  Platform: All
OS/Version: Linux
  Tree: Mainline
Status: NEW
  Severity: normal
  Priority: P1
 Component: Video(DRI)
AssignedTo: drivers_video-...@kernel-bugs.osdl.org
ReportedBy: dennis.jan...@web.de


Distribution: Ubuntu 8.10
Hardware Environment: Acer Extensa 5220
Software Environment: Xorg 7.4~5ubuntu3
Problem Description:

Intel modesetting works fine on the console (as long as vesafb is not used).
[   51.675136] allocated 1280x1024 fb: 0x007df000, bo 88007f1fd600
[   51.681325] Console: switching to colour frame buffer device 160x50
[   51.742152] [drm] DAC-6: set mode 1280x1024 24
[   51.762350] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count
for disabled pipe 1
[   51.802988] [drm] LVDS-8: set mode 1280x800 20
[   51.806349] fb0: inteldrmfb frame buffer device
[   51.806351] registered panic notifier
[   51.806356] [drm] Initialized i915 1.6.0 20080730 on minor 0

But I get a 
WARNING: at drivers/gpu/drm/drm_crtc.c:213 drm_mode_object_get+0x49/0xaf()

And I can't start X with it activated. I use intel xorg module v. 2.5.0. 

[  155.265134] Xorg:8838 map pfn expected mapping type uncached-minus for
d000-e000, got write-combining

Fatal server error:
AddScreen/ScreenInit failed for driver 0

I will attach log files.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #2 from dennis.jan...@web.de  2009-01-04 09:12 ---
Created an attachment (id=19644)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=19644action=view)
dualhead xorg.log


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12174] No backlight control on Samsung x360

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12174


washa...@gmail.com changed:

   What|Removed |Added

 CC||washa...@gmail.com




--- Comment #10 from washa...@gmail.com  2009-01-04 04:42 ---
Hello, I have the same problem. I am running Kubuntu Intrepid Ibex. Please let
me know if I can provide some information to help.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #4 from dennis.jan...@web.de  2009-01-04 10:20 ---
Created an attachment (id=19645)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=19645action=view)
xorg.conf

btw. intel module version 2.5.99.1 makes no difference. xorg.conf attached.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #3 from dennis.jan...@web.de  2009-01-04 09:57 ---
Booting with nopat let me start X, but the screens were partly garbled. I could
move the mouse, but when I tried to exit (Ctrl-Alt-F1 or Backspace), the
display hung up completely filled with noise.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #5 from cor...@debian.org  2009-01-04 10:34 ---
Maybe try to build intel module with --enable-kms?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #6 from dennis.jan...@web.de  2009-01-04 11:15 ---
Oh. that might well be it. intel driver 2.5.99 doesn't compile with
--enable-kms though... 2.5.0 doesn't have the option. I'll try 2.5.1.
Thanks!


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #1 from dennis.jan...@web.de  2009-01-04 09:12 ---
Created an attachment (id=19643)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=19643action=view)
dualhead dmesg

This seems related btw.
http://www.gossamer-threads.com/lists/linux/kernel/917056


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12359] WARNING and other intel modesetting problems

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12359





--- Comment #7 from cor...@debian.org  2009-01-04 11:26 ---
You first have to figure out how to build 2.5.99 with enable-kms (mainly, I
needed to update x11proto-core-dev to 7.0.14.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[PATCH] Claim PCI device when running in modesetting mode.

2009-01-04 Thread Kristian Høgsberg
Under kernel modesetting, we manage the device at all times, regardless
of VT switching and X servers, so the only decent thing to do is to
claim the PCI device.  In that case, we call the suspend/resume hooks
directly from the pci driver hooks instead of the current class device detour.

Signed-off-by: Kristian Høgsberg k...@redhat.com
---
 drivers/gpu/drm/drm_drv.c   |   67 +-
 drivers/gpu/drm/drm_stub.c  |   85 --
 drivers/gpu/drm/drm_sysfs.c |8 +++-
 drivers/gpu/drm/i915/i915_drv.c |   38 +
 include/drm/drmP.h  |2 +-
 5 files changed, 119 insertions(+), 81 deletions(-)

diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index febb517..44bf3ae 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -252,15 +252,19 @@ int drm_lastclose(struct drm_device * dev)
 int drm_init(struct drm_driver *driver)
 {
struct pci_dev *pdev = NULL;
-   struct pci_device_id *pid;
+   const struct pci_device_id *pid;
int i;
 
DRM_DEBUG(\n);
 
INIT_LIST_HEAD(driver-device_list);
 
+   if (driver-driver_features  DRIVER_MODESET)
+   return pci_register_driver(driver-pci_driver);
+
+   /* If not using KMS, fall back to stealth mode manual scanning. */
for (i = 0; driver-pci_driver.id_table[i].vendor != 0; i++) {
-   pid = (struct pci_device_id *)driver-pci_driver.id_table[i];
+   pid = driver-pci_driver.id_table[i];
 
/* Loop around setting up a DRM device for each PCI device
 * matching our ID and device class.  If we had the internal
@@ -285,64 +289,17 @@ int drm_init(struct drm_driver *driver)
 
 EXPORT_SYMBOL(drm_init);
 
-/**
- * Called via cleanup_module() at module unload time.
- *
- * Cleans up all DRM device, calling drm_lastclose().
- *
- * \sa drm_init
- */
-static void drm_cleanup(struct drm_device * dev)
-{
-   DRM_DEBUG(\n);
-
-   if (!dev) {
-   DRM_ERROR(cleanup called no dev\n);
-   return;
-   }
-
-   drm_vblank_cleanup(dev);
-
-   drm_lastclose(dev);
-
-   if (drm_core_has_MTRR(dev)  drm_core_has_AGP(dev) 
-   dev-agp  dev-agp-agp_mtrr = 0) {
-   int retval;
-   retval = mtrr_del(dev-agp-agp_mtrr,
- dev-agp-agp_info.aper_base,
- dev-agp-agp_info.aper_size * 1024 * 1024);
-   DRM_DEBUG(mtrr_del=%d\n, retval);
-   }
-
-   if (drm_core_has_AGP(dev)  dev-agp) {
-   drm_free(dev-agp, sizeof(*dev-agp), DRM_MEM_AGPLISTS);
-   dev-agp = NULL;
-   }
-
-   if (dev-driver-unload)
-   dev-driver-unload(dev);
-
-   drm_ht_remove(dev-map_hash);
-   drm_ctxbitmap_cleanup(dev);
-
-   if (drm_core_check_feature(dev, DRIVER_MODESET))
-   drm_put_minor(dev-control);
-
-   if (dev-driver-driver_features  DRIVER_GEM)
-   drm_gem_destroy(dev);
-
-   drm_put_minor(dev-primary);
-   if (drm_put_dev(dev))
-   DRM_ERROR(Cannot unload module\n);
-}
-
 void drm_exit(struct drm_driver *driver)
 {
struct drm_device *dev, *tmp;
DRM_DEBUG(\n);
 
-   list_for_each_entry_safe(dev, tmp, driver-device_list, driver_item)
-   drm_cleanup(dev);
+   if (driver-driver_features  DRIVER_MODESET) {
+   pci_unregister_driver(driver-pci_driver);
+   } else {
+   list_for_each_entry_safe(dev, tmp, driver-device_list, 
driver_item)
+   drm_put_dev(dev);
+   }
 
DRM_INFO(Module unloaded\n);
 }
diff --git a/drivers/gpu/drm/drm_stub.c b/drivers/gpu/drm/drm_stub.c
index 5ca132a..e8b2c3f 100644
--- a/drivers/gpu/drm/drm_stub.c
+++ b/drivers/gpu/drm/drm_stub.c
@@ -372,6 +372,7 @@ int drm_get_dev(struct pci_dev *pdev, const struct 
pci_device_id *ent,
}
 
if (drm_core_check_feature(dev, DRIVER_MODESET)) {
+   pci_set_drvdata(pdev, dev);
ret = drm_get_minor(dev, dev-control, DRM_MINOR_CONTROL);
if (ret)
goto err_g2;
@@ -409,29 +410,7 @@ err_g1:
drm_free(dev, sizeof(*dev), DRM_MEM_STUB);
return ret;
 }
-
-/**
- * Put a device minor number.
- *
- * \param dev device data structure
- * \return always zero
- *
- * Cleans up the proc resources. If it is the last minor then release the 
foreign
- * drm data, otherwise unregisters the drm data, frees the dev list and
- * unregisters the character device.
- */
-int drm_put_dev(struct drm_device * dev)
-{
-   DRM_DEBUG(release primary %s\n, dev-driver-pci_driver.name);
-
-   if (dev-devname) {
-   drm_free(dev-devname, strlen(dev-devname) + 1,
-DRM_MEM_DRIVER);
-   dev-devname = NULL;
-   }
-   drm_free(dev, sizeof(*dev), DRM_MEM_STUB);

[PATCH] Claim PCI device when running in modesetting mode.

2009-01-04 Thread Kristian Høgsberg
Under kernel modesetting, we manage the device at all times, regardless
of VT switching and X servers, so the only decent thing to do is to
claim the PCI device.  In that case, we call the suspend/resume hooks
directly from the pci driver hooks instead of the current class device detour.

Signed-off-by: Kristian Høgsberg k...@redhat.com
---
 drivers/gpu/drm/drm_drv.c   |   67 +-
 drivers/gpu/drm/drm_stub.c  |   85 --
 drivers/gpu/drm/drm_sysfs.c |8 +++-
 drivers/gpu/drm/i915/i915_drv.c |   38 +
 include/drm/drmP.h  |2 +-
 5 files changed, 119 insertions(+), 81 deletions(-)

diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index febb517..44bf3ae 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -252,15 +252,19 @@ int drm_lastclose(struct drm_device * dev)
 int drm_init(struct drm_driver *driver)
 {
struct pci_dev *pdev = NULL;
-   struct pci_device_id *pid;
+   const struct pci_device_id *pid;
int i;
 
DRM_DEBUG(\n);
 
INIT_LIST_HEAD(driver-device_list);
 
+   if (driver-driver_features  DRIVER_MODESET)
+   return pci_register_driver(driver-pci_driver);
+
+   /* If not using KMS, fall back to stealth mode manual scanning. */
for (i = 0; driver-pci_driver.id_table[i].vendor != 0; i++) {
-   pid = (struct pci_device_id *)driver-pci_driver.id_table[i];
+   pid = driver-pci_driver.id_table[i];
 
/* Loop around setting up a DRM device for each PCI device
 * matching our ID and device class.  If we had the internal
@@ -285,64 +289,17 @@ int drm_init(struct drm_driver *driver)
 
 EXPORT_SYMBOL(drm_init);
 
-/**
- * Called via cleanup_module() at module unload time.
- *
- * Cleans up all DRM device, calling drm_lastclose().
- *
- * \sa drm_init
- */
-static void drm_cleanup(struct drm_device * dev)
-{
-   DRM_DEBUG(\n);
-
-   if (!dev) {
-   DRM_ERROR(cleanup called no dev\n);
-   return;
-   }
-
-   drm_vblank_cleanup(dev);
-
-   drm_lastclose(dev);
-
-   if (drm_core_has_MTRR(dev)  drm_core_has_AGP(dev) 
-   dev-agp  dev-agp-agp_mtrr = 0) {
-   int retval;
-   retval = mtrr_del(dev-agp-agp_mtrr,
- dev-agp-agp_info.aper_base,
- dev-agp-agp_info.aper_size * 1024 * 1024);
-   DRM_DEBUG(mtrr_del=%d\n, retval);
-   }
-
-   if (drm_core_has_AGP(dev)  dev-agp) {
-   drm_free(dev-agp, sizeof(*dev-agp), DRM_MEM_AGPLISTS);
-   dev-agp = NULL;
-   }
-
-   if (dev-driver-unload)
-   dev-driver-unload(dev);
-
-   drm_ht_remove(dev-map_hash);
-   drm_ctxbitmap_cleanup(dev);
-
-   if (drm_core_check_feature(dev, DRIVER_MODESET))
-   drm_put_minor(dev-control);
-
-   if (dev-driver-driver_features  DRIVER_GEM)
-   drm_gem_destroy(dev);
-
-   drm_put_minor(dev-primary);
-   if (drm_put_dev(dev))
-   DRM_ERROR(Cannot unload module\n);
-}
-
 void drm_exit(struct drm_driver *driver)
 {
struct drm_device *dev, *tmp;
DRM_DEBUG(\n);
 
-   list_for_each_entry_safe(dev, tmp, driver-device_list, driver_item)
-   drm_cleanup(dev);
+   if (driver-driver_features  DRIVER_MODESET) {
+   pci_unregister_driver(driver-pci_driver);
+   } else {
+   list_for_each_entry_safe(dev, tmp, driver-device_list, 
driver_item)
+   drm_put_dev(dev);
+   }
 
DRM_INFO(Module unloaded\n);
 }
diff --git a/drivers/gpu/drm/drm_stub.c b/drivers/gpu/drm/drm_stub.c
index 5ca132a..e8b2c3f 100644
--- a/drivers/gpu/drm/drm_stub.c
+++ b/drivers/gpu/drm/drm_stub.c
@@ -372,6 +372,7 @@ int drm_get_dev(struct pci_dev *pdev, const struct 
pci_device_id *ent,
}
 
if (drm_core_check_feature(dev, DRIVER_MODESET)) {
+   pci_set_drvdata(pdev, dev);
ret = drm_get_minor(dev, dev-control, DRM_MINOR_CONTROL);
if (ret)
goto err_g2;
@@ -409,29 +410,7 @@ err_g1:
drm_free(dev, sizeof(*dev), DRM_MEM_STUB);
return ret;
 }
-
-/**
- * Put a device minor number.
- *
- * \param dev device data structure
- * \return always zero
- *
- * Cleans up the proc resources. If it is the last minor then release the 
foreign
- * drm data, otherwise unregisters the drm data, frees the dev list and
- * unregisters the character device.
- */
-int drm_put_dev(struct drm_device * dev)
-{
-   DRM_DEBUG(release primary %s\n, dev-driver-pci_driver.name);
-
-   if (dev-devname) {
-   drm_free(dev-devname, strlen(dev-devname) + 1,
-DRM_MEM_DRIVER);
-   dev-devname = NULL;
-   }
-   drm_free(dev, sizeof(*dev), DRM_MEM_STUB);

[Bug 19170] compiz w/ 3D effects causes Intel GM45 hang in drm module

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19170


M. Edwin Zakaria medw...@gmail.com changed:

   What|Removed |Added

 CC||medw...@gmail.com




--- Comment #1 from M. Edwin Zakaria medw...@gmail.com  2009-01-04 20:26:14 
PST ---
I use openSUSE 11.1 kernel 2.6.27.7-9-pae, with kde 3.5.10 in my HP2230s
laptop, chipset Intel GM45. When I activate 3D in Sax then my laptop is hang
upon running google earth 4.3. The system become not responsive, screen is
freeze, cannot login from konsole, keyboard also freezed. 

It does not happen when I disable 3D support.

Compiz is running well in 3D mode, no problem.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] New: incorrect font rendering when run googlearth 4.3()

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396

   Summary: incorrect  font rendering when run googlearth 4.3()
   Product: Mesa
   Version: unspecified
  Platform: Other
OS/Version: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: Drivers/DRI/i915
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: haien@intel.com


Created an attachment (id=21668)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=21668)
xorg.0.log

System Environment:
--
Host:   g45
Arch:   i386
OSD:Fedora release 9 (Sulphur)
Kernel: 2.6.28
Libdrm_stable:  (master)c34539e8bb5568b1d6059abf139dd08e07e84eea
Mesa_stable:(intel-2008-q4)88f4b17555be36f3023f74a1b9c792294f09912b
Xorg:   7.2
Xserver_stable: (server-1.6-branch)32e81074b967716865aef08b66ec29caf0fec2c5
Xf86_video_intel_stable: (xf86-video-intel-2.6-branch)
  fac43181af0ad59fa6d06e26d369d886ce221c10
GEM_kernel:   (drm-intel-2.6.28)72e2bfb03f46f7eef1ae8907593dd35e2c5603d

Bug detailed description:
-
start X,then run googleearth, we will get some incorrect font rendering as is
shown in the attached screenshots.it happens on all platforms. 

Reproduce steps:

1.xinit
2. run googleearth


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googlearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396


liuhaien haien@intel.com changed:

   What|Removed |Added

Summary|incorrect  font rendering   |incorrect  font rendering
   |when run googlearth 4.3()   |when run googlearth 4.3




-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googlearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396





--- Comment #1 from liuhaien haien@intel.com  2009-01-04 22:50:00 PST ---
Created an attachment (id=21669)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=21669)
xorg conf file


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googleearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396


liuhaien haien@intel.com changed:

   What|Removed |Added

Summary|incorrect  font rendering   |incorrect  font rendering
   |when run googlearth 4.3 |when run googleearth 4.3




-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googleearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396





--- Comment #2 from liuhaien haien@intel.com  2009-01-04 22:51:31 PST ---
Created an attachment (id=21670)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=21670)
screenshot1


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googleearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396





--- Comment #3 from liuhaien haien@intel.com  2009-01-04 22:54:42 PST ---
Created an attachment (id=21671)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=21671)
screenshot2


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googleearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396





--- Comment #4 from liuhaien haien@intel.com  2009-01-04 22:57:16 PST ---
googleearth4.0 works with the same code.this issue only happens with
googleearth4.3(beta).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 12345] X on Intel 965GM hangs on console switch if compositing is enabled

2009-01-04 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=12345


gordon@intel.com changed:

   What|Removed |Added

 CC||jbar...@virtuousgeek.org




--- Comment #3 from gordon@intel.com  2009-01-04 23:03 ---
This seems the same as http://bugs.freedesktop.org/show_bug.cgi?id=18879


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19170] compiz w/ 3D effects causes Intel GM45 hang in drm module

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19170





--- Comment #2 from Gordon Jin gordon@intel.com  2009-01-04 23:15:28 PST 
---
(In reply to comment #1)
 I use openSUSE 11.1 kernel 2.6.27.7-9-pae, with kde 3.5.10 in my HP2230s
 laptop, chipset Intel GM45. When I activate 3D in Sax then my laptop is hang
 upon running google earth 4.3. The system become not responsive, screen is
 freeze, cannot login from konsole, keyboard also freezed. 

Your opensuse problem seems bug#19242.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 19396] incorrect font rendering when run googleearth 4.3

2009-01-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=19396





--- Comment #5 from Gordon Jin gordon@intel.com  2009-01-04 23:23:29 PST 
---
maybe bug#19233. So can you verify with server-1.5 branch?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [git pull] drm

2009-01-04 Thread Gabriel C
Dave Airlie wrote:

Hi Dave ,

...


 
 Please pull the 'drm-next' branch from
 ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-next
 
 Major highlights:
 Kernel Modesetting (KMS) core code (jbarnes you can go to drinking island 
 now)
 Intel i915 support for kernel modesetting






 commit 79e539453b34e35f39299a899d263b0a1f1670bd
 Author: Jesse Barnes jbar...@virtuousgeek.org
 Date:   Fri Nov 7 14:24:08 2008 -0800
 
 DRM: i915: add mode setting support
 
 This commit adds i915 driver support for the DRM mode setting APIs.
 Currently, VGA, LVDS, SDVO DVI  VGA, TV and DVO LVDS outputs are
 supported.  HDMI, DisplayPort and additional SDVO output support will
 follow.
 
 Support for the mode setting code is controlled by the new 'modeset'
 module option.  A new config option, CONFIG_DRM_I915_KMS controls the
 default behavior, and whether a PCI ID list is built into the module for
 use by user level module utilities.
 
 Note that if mode setting is enabled, user level drivers that access
 display registers directly or that don't use the kernel graphics memory
 manager will likely corrupt kernel graphics memory, disrupt output
 configuration (possibly leading to hangs and/or blank displays), and
 prevent panic/oops messages from appearing.  So use caution when
 enabling this code; be sure your user level code supports the new
 interfaces.
 
 A new SysRq key, 'g', provides emergency support for switching back to
 the kernel's framebuffer console; which is useful for testing.
 
 Co-authors: Dave Airlie airl...@linux.ie, Hong Liu hong@intel.com
 
 Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
 Signed-off-by: Eric Anholt e...@anholt.net
 Signed-off-by: Dave Airlie airl...@redhat.com
 


This commit added the following text to drivers/gpu/drm/Kconfig :

config DRM_I915_KMS
   bool Enable modesetting on intel by default
   depends on DRM_I915
   help
   Choose this option if you want kernel modesetting enabled by default,
   and you have a new enough userspace to support this. Running old
   userspaces with this enabled will cause pain.  Note that this causes
   the driver to bind to PCI devices, which precludes loading things
   like intelfb.


I don't think any 'normal' user has a clue what you guys meant by 
'new and old userspace' . Could someone clarify 'what versions of probably Xorg 
and libs are
needed to have that support and which are for sure broken or old' please ?

Also while testing this with xorg-server 1.4* I found out the 'pain' means an 
broken X and a broken box since 
it broke the kernel as well and the only way to get the box to live again was 
an hard reset. Please clarify the 'pain' part too.

Thanks for your time.

Best regards ,

Gabriel C



--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel