X.org hanging under 7.2-PRERELEASE
I update -STABLE about once a week. On Wednesday I update, and subsequently started getting hangs and lockups. This happens only when DRI is enabled. When DRI is disabled there is no problem. The seriousness can vary. Sometimes I can ssh in from another machine to reboot, other times I can't. The last time it hung, top showed X.org at 100.0% CPU. The previous time it was stuck with in a "drmwtq" state. The hang always occurs within twenty minutes of starting X. Particulars: FreeBSD 7.2-PRERELEASE #2: Thu Mar 26 19:21:26 xf86-video-ati-6.12.1 (with Radeon X1550) kdelibs-4.2.1_1 Relevant portions of my xorg.conf: Section "Module" Load "extmod" Load "dbe" Load "dri" Load "glx" Load "xtrap" Load "freetype" EndSection Section "Device" Identifier "Card0" Driver "radeon" ... Option "AGPMode" "4" Option "RenderAccel" "on" Option "AccelMethod" "EXA" EndSection I have had no prior problems with -STABLE. I have an Intel Q45 chipset, so I need to run -STABLE, and don't have the option of going back to -RELEASE. Is there any easy way to go back to an earlier -STABLE? -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: X.org hanging under 7.2-PRERELEASE
On Friday 27 March 2009 11:34:17 pm Robert Noland wrote: > Actually, the commits that I might have expected to cause this, haven't > been MFC'd yet. You probably did pick up the r6/7xx code in this > update. I also made an error in the GART mapping code, but that should > only effect pci(e) based radeons. Actually, my card is a PCI-Express. > It could also be related to the 6.12.1 ati driver. AGP mode 4x is > always suspect as well, you might try reducing that to 2 or 1 and see if > the problems go away. > > As for checking out an earlier release, with csup you just have to > specify a date that you want to checkout. See man csup and reference > the section titled CHECKOUT MODE. If PCI-Express is not allowed (do they even make AGP boards anymore?) then I'll have to downgrade until the GART gets fixed. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: X.org hanging under 7.2-PRERELEASE
On Saturday 28 March 2009 11:07:49 am Robert Noland wrote: > Ok, the GART should be fixed in HEAD as well... > > r190282 is what you need. You probably need 190123 for it to apply > cleanly. I'll attach both. To clarify, this is for STABLE? Will these changes make it into STABLE in the near future? -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: X.org hanging under 7.2-PRERELEASE
On Saturday 28 March 2009 11:07:49 am Robert Noland wrote: > Ok, the GART should be fixed in HEAD as well... > > r190282 is what you need. You probably need 190123 for it to apply > cleanly. I'll attach both. That appears to work. Half an hour now, and no hang yet. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: X.org hanging under 7.2-PRERELEASE
On Saturday 28 March 2009 01:55:23 am Robert Noland wrote: > Actually, hanging in drmwtq is usually an indication of the card going > belly up, or of interrupts being trashed. Make sure that you aren't > getting an interrupt storm on a shared irq with drm/vgapci. Can you > send me a full dmesg after drm is loaded and an xorg.log. Without drm, > you really don't use interrupts, so... My last email was premature. I hung again while trying to open an image. I am attaching the output of dmesg, ps and the Xorg log. The latter is full of the following messages: [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. I can't afford to be a tester, I have work I need to get done with this system. Please let me know if this gets fixed. In the meantime I'm going back to older code. -- David Johnson Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-PRERELEASE #3: Sat Mar 28 18:44:05 PDT 2009 da...@radagast.usermode.org:/usr/obj/usr/src/sys/RADAGAST Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (2833.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x10677 Stepping = 7 Features=0xbfebfbff Features2=0x8e3fd AMD Features=0x2010 AMD Features2=0x1 Cores per package: 4 real memory = 3220176896 (3071 MB) avail memory = 3146973184 (3001 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xd000-0xd0ff mem 0xd000-0xdfff,0xfea3-0xfea3 irq 16 at device 0.0 on pci1 vgapci1: mem 0xfea2-0xfea2 at device 0.1 on pci1 pci0: at device 3.0 (no driver attached) atapci0: port 0xe210-0xe217,0xe200-0xe203,0xe1f0-0xe1f7,0xe1e0-0xe1e3,0xe1d0-0xe1df irq 18 at device 3.2 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] pci0: at device 3.3 (no driver attached) em0: port 0xe0e0-0xe0ff mem 0xfeb0-0xfeb1,0xfeb24000-0xfeb24fff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1c:c0:7e:5e:32 uhci0: port 0xe0c0-0xe0df irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe0a0-0xe0bf irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe080-0xe09f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfeb26400-0xfeb267ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: waiting for BIOS to give up control usb3: timed out waiting for BIOS usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered hdac0: mem 0xfeb2-0xfeb23fff irq 22 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090316_0130 hdac0: [ITHREAD] uhci3: port 0xe060-0xe07f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xe040-0xe05f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xe020-0xe03f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xfeb26000-0xfeb263ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: waiting for BIOS to give up control usb7: timed out waiting for BIOS usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb7: USB revision 2.0 uhub7: on usb7 uhub7: 6 ports with 6 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 fwohci0: mem 0xfe90-0xfe900fff,0xfe901000-0xfe9010ff irq 22 a
Re: X.org hanging under 7.2-PRERELEASE
On Saturday 28 March 2009 10:45:24 pm David Johnson wrote: > My last email was premature. I hung again while trying to open an image. I > am attaching the output of dmesg, ps and the Xorg log. The latter is full > of the following messages: Forgot the Xorg log. Here it is: -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: X.org hanging under 7.2-PRERELEASE
On Saturday 28 March 2009 11:08:49 pm David Johnson wrote: > On Saturday 28 March 2009 10:45:24 pm David Johnson wrote: > > My last email was premature. I hung again while trying to open an image. > > I am attaching the output of dmesg, ps and the Xorg log. The latter is > > full of the following messages: > > Forgot the Xorg log. Here it is: Weird. Don't know why I won't send. Oh well. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Xorg hangs with drmwtq in 7.2-RELEASE
This topic has been recently discussed twice before in the past month and a half, but without resolution. It now reappears on my system as I upgrade to 7.2-RELEASE. It does not happen with a build from RELENG_7 date=2009.03.13. I am desperately hoping for a resolution. To reiterate the problem: Xorg will occassionally hang. This only happens when compositing it enabled. I am using KDE 4.2.2, radeon driver, all ports updated to this morning. About a third of the time the kernel locks up, and I cannot ssh into the system. The other half of the time I can ssh into the system. There I notice that Xorg has the state of "drmwtq", with perhaps some other GUI processes in the same state. The video card is a Radeon X1550. I have tried with and without AGPMode set, and both XAA and EXA render modes. No change. You can look at my xorg.conf and Xorg log at: http://www.usermode.org/misc/xorg.conf http://www.usermode.org/misc/Xorg.0.log.old p.s. Posting to freebsd-stable, as this problem has been previously discussed here. If this is no longer the appropriate list, please let me know. Thank you, -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Monday 04 May 2009 11:20:17 pm Robert Noland wrote: > This generally suggests that the GPU is locked up... Given that you say > sometimes it locks up hard (usually a panic, that you can't see since X > is running) and other times only X is stalled it might be related to > this patch, if you haven't tried this on already. > > http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch Nope, that didn't help. Still froze when I tried opening multiple windows at once. I'm backing out the patch to get back to a clean state. I also edited my xorg.conf to be closer to yours. No difference. What information do you need to go forward, and how do I collect it? p.s. I didn't have a problem with sources from RELENG_7 date=2009.03.13, if that helps any. Thanks for you time, -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Tuesday 05 May 2009 08:41:48 pm David Johnson wrote: > On Monday 04 May 2009 11:20:17 pm Robert Noland wrote: > > This generally suggests that the GPU is locked up... Given that you say > > sometimes it locks up hard (usually a panic, that you can't see since X > > is running) and other times only X is stalled it might be related to > > this patch, if you haven't tried this on already. > > > > http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch > > Nope, that didn't help. Still froze when I tried opening multiple windows > at once. I'm backing out the patch to get back to a clean state. > > I also edited my xorg.conf to be closer to yours. No difference. > > What information do you need to go forward, and how do I collect it? > > p.s. I didn't have a problem with sources from RELENG_7 date=2009.03.13, if > that helps any. I just upgraded graphics/libdrm. It didn't help any. I'm just shooting blanks in the dark. Any help would be greatly appreciated. Please let me know what information is needed and how I collect it. Thank you, -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Friday 08 May 2009 07:35:45 am Robert Noland wrote: > I still can't reproduce this... I updated the Xserver, libGL and dri > ports yesterday, all of which could be related to locking up the GPU and > worth a shot. Failing that, I need you to enabled drm debugging. Start > the system without X, kldload radeon.ko, set sysctl hw.dri.0.debug=1 > then startx. I've got all the updated ports as of last night, so that wasn't it. I turned AIGLX back on, and it promptly locked up again. This time, however, the screen went black instead of freezing, but otherwise the same as always. I then turned on hw.dri.0.debug, and messages quickly filled up with the following repeated message: [drm:pid1195:drm_ioctl] returning 4 [drm:pid1195:drm_ioctl] pid=1195, cmd=0x80046457, nr=0x57, dev 0xc615fa00, auth=1 -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote: > In order to guess what might be causing this, drm debugging needs to be > enabled before the hang, so that we can hopefully figure out what leads > up to the hung GPU. Unfortunately that won't work, because turning on hw.dri.0.debug slows down compositing so much that it won't reproduce. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote: > In order to guess what might be causing this, drm debugging needs to be > enabled before the hang, so that we can hopefully figure out what leads > up to the hung GPU. I'm not able to do that, but I did manage to get debug turned on and dmesg captured early enough to catch some additional information. I've place the full file online at http://www.usermode.org/misc/dmesg.txt, but am including some snippets here. Hopefully this is enough to move forward. -- David Johnson ... [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0286429, nr=0x29, dev 0xc615fa00, auth=1 [drm:pid1822:radeon_freelist_get] done_age = 102778 [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc010644d, nr=0x4d, dev 0xc615fa00, auth=1 [drm:pid1822:radeon_cp_indirect] idx=27 s=0 e=88 d=1 [drm:pid1822:radeon_cp_dispatch_indirect] buf=27 s=0x0 e=0x58 [drm:pid1822:drm_close] open_count = 2 [drm:pid1822:drm_close] pid = 1822, device = 0xc615fa00, open_count = 2 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x80086442, nr=0x42, dev 0xc615fa00, auth=1 [drm:pid1822:radeon_cp_stop] [drm:pid1822:radeon_do_cp_flush] [drm:pid1822:radeon_do_cp_idle] [drm:pid1822:radeon_do_cp_stop] [drm:pid1822:radeon_do_engine_reset] info: [drm] Num pipes: 1 [drm:pid1822:radeon_do_cp_reset] [drm:pid1822:drm_ioctl] pid=1822, cmd=0x800c6459, nr=0x59, dev 0xc615fa00, auth=1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x80086414, nr=0x14, dev 0xc615fa00, auth=1 [drm:pid1822:drm_irq_uninstall] irq=16 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x80546440, nr=0x40, dev 0xc615fa00, auth=1 [drm:pid1822:radeon_do_cleanup_cp] [drm:pid1822:drm_ioctl] pid=1822, cmd=0x80086439, nr=0x39, dev 0xc615fa00, auth=1 [drm:pid1822:drm_sg_free] sg free virtual = 0xe8a64000 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x8004667e, nr=0x7e, dev 0xc615fa00, auth=1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x8004667d, nr=0x7d, dev 0xc615fa00, auth=1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0086421, nr=0x21, dev 0xc615fa00, auth=1 [drm:pid1822:drm_rmctx] 2 [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0086421, nr=0x21, dev 0xc615fa00, auth=1 [drm:pid1822:drm_rmctx] 1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0086426, nr=0x26, dev 0xc615fa00, auth=1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0086426, nr=0x26, dev 0xc615fa00, auth=1 [drm:pid1822:drm_ioctl] pid=1822, cmd=0x8008642b, nr=0x2b, dev 0xc615fa00, auth=1 [drm:pid1822:drm_unlock] 1 (pid 1822) requests unlock (0x8001), flags = 0x [drm:pid1822:drm_close] open_count = 1 [drm:pid1822:drm_close] pid = 1822, device = 0xc615fa00, open_count = 1 [drm:pid1822:drm_lastclose] [drm:pid1822:radeon_do_cleanup_cp] info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 info: [drm] Setting GART location based on new memory map info: [drm] Loading R500 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] [drm:pid6216:drm_ioctl] returning 4 [drm:pid6216:drm_ioctl] pid=6216, cmd=0x80046457, nr=0x57, dev 0xc615fa00, auth=1 [drm:pid6216:drm_ioctl] returning 4 [drm:pid6216:drm_ioctl] pid=6216, cmd=0x80046457, nr=0x57, dev 0xc615fa00, auth=1 [drm:pid6216:drm_ioctl] returning 4 [drm:pid6216:drm_ioctl] pid=6216, cmd=0x80046457, nr=0x57, dev 0xc615fa00, auth=1 [drm:pid6216:drm_ioctl] returning 4 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Tuesday 12 May 2009 08:17:51 am Robert Noland wrote: > On Sat, 2009-05-09 at 18:41 -0700, David Johnson wrote: > > On Friday 08 May 2009 03:31:04 pm Robert Noland wrote: > > > In order to guess what might be causing this, drm debugging needs to be > > > enabled before the hang, so that we can hopefully figure out what leads > > > up to the hung GPU. > > > > I'm not able to do that, but I did manage to get debug turned on and > > dmesg captured early enough to catch some additional information. I've > > place the full file online at http://www.usermode.org/misc/dmesg.txt, but > > am including some snippets here. Hopefully this is enough to move > > forward. > > > > -- > > David Johnson > > This trace still looks odd... This should have been a single trace, with debugging turned after X was hung. I turned debug on once, grabbed output of dmesg, then rebooted. 1) Run script to launch four windows in rapid succession. 2) Only two windows manage to make it up before X hangs. 3) Switch over to laptop, which is ssh'd into system 4) sysctl hw.drm.0.debug=1 5) dmesg > dmesg.txt 6) Done I may have made a mistake though, and briefly turned on debugging earlier in the session. I'll get another trace this evening when I have time, to double check. p.s. I've put 7.1-STABLE from March 13th on a different partition. I will add in commits until it breaks, to help narrow it down. I'm fairly sure it was something on the 15th or 16th. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
On Tuesday 12 May 2009 11:52:29 am David Johnson wrote: > I may have made a mistake though, and briefly turned on debugging earlier > in the session. I'll get another trace this evening when I have time, to > double check. Yup, I must have turned on debugging earlier in that session. All I can get now is that repetitous drm_ioctl. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
I don't know if this helps pinpointing my problem, but when I unload the drm module, I get the following message: May 15 19:57:52 radagast kernel: vgapci0: child drm0 requested pci_disable_busmaster May 15 19:57:52 radagast kernel: drm0: detached May 15 19:57:52 radagast kernel: Warning: memory type drm_bufs leaked memory on destroy (4 allocations, 128 bytes leaked). After this I can load the radeon and drm modules, but X will not start, complaining about no screen found. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
After much rebuilding and testing, I have narrowed down the introduction of this bug to commit #189855. Most of this commit is related to r600/700 chips, but there are other changes. I don't understand the code and can't see anything obvious. But it is a place to start. Does this help any? Or should I keep banging my head against the wall? -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg hangs with drmwtq in 7.2-RELEASE
I haven't heard anything on this in three weeks. I filed a bug report, but no acceptance yet. Does this imply that there is no intention to fix this problem? What is happening with this? Am I even posting to the right list? I'm completely in the dark here. -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
