NetBSD Problem Report #44565
From campbell@mumble.net Sun Feb 13 23:12:18 2011
Return-Path: <campbell@mumble.net>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
by www.NetBSD.org (Postfix) with ESMTP id 5B3FA63B100
for <gnats-bugs@gnats.NetBSD.org>; Sun, 13 Feb 2011 23:12:18 +0000 (UTC)
Message-Id: <20110213231216.C386398298@pluto.mumble.net>
Date: Sun, 13 Feb 2011 23:12:16 +0000 (UTC)
From: Taylor R Campbell <campbell+netbsd@mumble.net>
Reply-To: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@gnats.NetBSD.org
Subject: X works for about thirty seconds and then freezes on my MacBook1,1
X-Send-Pr-Version: 3.95
>Number: 44565
>Category: xsrc
>Synopsis: X works for about thirty seconds and then freezes on my MacBook1,1
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: xsrc-manager
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Feb 13 23:15:00 +0000 2011
>Closed-Date: Sun Nov 25 20:38:05 +0000 2018
>Last-Modified: Sun Nov 25 20:38:05 +0000 2018
>Originator: Taylor R Campbell <campbell+netbsd@mumble.net>
>Release: NetBSD 5.1
>Organization:
>Environment:
NetBSD oberon.local 5.1 NetBSD 5.1 (GENERIC) #0: Sun Nov 7 14:39:56 UTC 2010 builds@b6.netbsd.org:/home/builds/ab/netbsd-5-1-RELEASE/i386/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
On my MacBook1,1, when I launch X (approximately, by typing
`startx'), it runs for about thirty seconds, and then
everything but the mouse cursor freezes. If I move the mouse
about, the cursor changes styles occasionally.
I am using modular X.org from pkgsrc-2010Q3, with libpciaccess
from pkgsrc-current as of a couple of days ago to include
jmcneill's i386 mtrr fix. The MacBook has an Intel graphics
card for which I have installed x11/xf86-video-intel from
pkgsrc. If you want detailed information about it, or about
any other part of my system, let me know what to run to procure
the information. Here are the relevant lines from `pcictl pci0
list':
000:02:0: Intel 82945GM/PM/GMS Integrated Graphics Device (VGA display, revision 0x03)
000:02:1: Intel 82945GM/PM/GMS Integrated Graphics Device (miscellaneous display, revision 0x03)
The problem persists in a 5.1_STABLE kernel that I built from
netbsd-5 as of a couple of weeks ago. The problem goes away if
instead I boot a kernel built from HEAD as of a couple of weeks
ago. (But I don't want to run a NetBSD-current kernel.)
>How-To-Repeat:
Install x11/modular-xorg-server and x11/xf86-video-intel under
NetBSD 5.1 on a MacBook1,1. Launch X. Try to use it. Watch
it freeze.
>Fix:
Yes, please!
>Release-Note:
>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 13:12:13 +0100
On which tty is the X server running? Can you log in via ssh when it
"froze"?
Is the coresponding tty marked "off" in your /etc/ttys file?
Martin
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, Martin Husemann <martin@duskware.de>
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 13:51:48 +0000
Date: Mon, 14 Feb 2011 13:12:13 +0100
From: Martin Husemann <martin@duskware.de>
On which tty is the X server running? Can you log in via ssh when it
"froze"?
Is the coresponding tty marked "off" in your /etc/ttys file?
I can log in via ssh and kill X -- it's just the display of windows
that is frozen. The mouse cursor still works, and it still changes
style as it moves over where the windows would be.
My Xorg.log.0 says
(--) Using wscons driver on /dev/ttyE1 in pcvt compatibility mode (version =
3.32)
and nothing else about ttys or consoles. My /etc/ttys is unchanged
from revision 1.19 of src/etc/etc.i386/ttys, so /dev/ttyE1 is off --
/dev/console is on and everything else is off.
From: Martin Husemann <martin@duskware.de>
To: Taylor R Campbell <campbell+netbsd@mumble.net>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 15:20:19 +0100
On Mon, Feb 14, 2011 at 01:51:48PM +0000, Taylor R Campbell wrote:
> (--) Using wscons driver on /dev/ttyE1 in pcvt compatibility mode (version 3.32)
ttyE1 is likely the problem, check if you have a getty process running
on ttyE1 (I suppose you have), I certainly do on most machines:
375 ttyE1 Is+ 0:00.08 /usr/libexec/getty ...
That process will fight with the X server for keyboard input. The X server
is supposed to run on ttyE4 by default (X gets a "vt5" arg), I'm not sure
what went wrong in your case.
Martin
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, Martin Husemann <martin@duskware.de>
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 14:54:31 +0000
Date: Mon, 14 Feb 2011 15:20:19 +0100
From: Martin Husemann <martin@duskware.de>
On Mon, Feb 14, 2011 at 01:51:48PM +0000, Taylor R Campbell wrote:
> (--) Using wscons driver on /dev/ttyE1 in pcvt compatibility mode (ver=
sion 3.32)
ttyE1 is likely the problem, check if you have a getty process running
on ttyE1 (I suppose you have), I certainly do on most machines:
375 ttyE1 Is+ 0:00.08 /usr/libexec/getty ...
I have no getty processes running. It may be worth mentioning that I
didn't install with sysinst (because other parts of sysinst are
broken, about which I suppose I ought to submit a PR), and I see that
sysinst on i386 tweaks /etc/ttys to enable ttyE[1-9].
That process will fight with the X server for keyboard input. The X serv=
er
is supposed to run on ttyE4 by default (X gets a "vt5" arg), I'm not sure
what went wrong in your case.
Keyboard input isn't the problem. If I have a terminal in focus when
the display freezes, I can still type into the terminal and observe
its effects. (I typed `touch frobnozzle', and, sure enough, a file
called frobnozzle appeared in my home directory.)
I turned on ttyE[1-3] in /etc/ttys, shut down to single-user mode and
came back to multi-user mode, and tried running X again. Xorg.log.0
says ttyE4, the mouse cursor is all wonky (it twitches all the time,
and if I touch the track pad to move it, it jumps to the bottom
right-hand corner of the screen before moving), and the display
freezes after thirty seconds or so again.
I rebooted the machine and tried running X again, which took ttyE4
again. The mouse cursor is no longer all wonky, but the display still
freezes after thirty seconds.
Responsible-Changed-From-To: kern-bug-people->xsrc-manager
Responsible-Changed-By: martin@NetBSD.org
Responsible-Changed-When: Mon, 14 Feb 2011 15:06:46 +0000
Responsible-Changed-Why:
Over to the X people
From: Martin Husemann <martin@duskware.de>
To: Taylor R Campbell <campbell+netbsd@mumble.net>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 16:05:12 +0100
On Mon, Feb 14, 2011 at 02:54:31PM +0000, Taylor R Campbell wrote:
> Keyboard input isn't the problem. If I have a terminal in focus when
> the display freezes, I can still type into the terminal and observe
> its effects. (I typed `touch frobnozzle', and, sure enough, a file
> called frobnozzle appeared in my home directory.)
Ok - so this is clearly an X server problem.
Martin
(And yes, you should send-pr the sysinst problems)
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 15:20:26 +0000
Date: Mon, 14 Feb 2011 16:05:12 +0100
From: Martin Husemann <martin@duskware.de>
Ok - so this is clearly an X server problem.
OK. I submitted it under `kern' because it works under a -current
kernel but not under a 5.1(_STABLE) kernel. (Also, I'm using X.org
from pkgsrc, not xsrc, although I suppose the pkgsrc one is just a
differently packaged version of the xsrc one.)
From: Martin Husemann <martin@duskware.de>
To: Taylor R Campbell <campbell+netbsd@mumble.net>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 16:24:59 +0100
On Mon, Feb 14, 2011 at 03:20:26PM +0000, Taylor R Campbell wrote:
> OK. I submitted it under `kern' because it works under a -current
> kernel but not under a 5.1(_STABLE) kernel. (Also, I'm using X.org
> from pkgsrc, not xsrc, although I suppose the pkgsrc one is just a
> differently packaged version of the xsrc one.)
The ticket might return to category kern ;-)
Which userland did you build X against? Since you can ssh in, could you
ktrace the X server an see where it freezes?
Martin
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 16:31:05 +0000
Date: Mon, 14 Feb 2011 16:24:59 +0100
From: Martin Husemann <martin@duskware.de>
Which userland did you build X against?
I think I built X against 5.1_RC2 as of about eight months ago --
either that or 5.0_STABLE as of about a year ago. (pkg_info tells me
that the kernel I was using was NetBSD 5.1_RC2, but I think I upgraded
the kernel first and waited a long time to upgrade the userland.)
Since you can ssh in, could you ktrace the X server an see where it
freezes?
I ktraced everything (a little tricky because the Xorg executable is
setuid), and I don't see anything particularly out of the ordinary in
the ktrace during the second or two after the one that xclock freezes
at. There is an out-of-order entry here (starred), presumably because
Xorg and xclock executables are running on different cores:
1070 1 Xorg 1297699912.019030271 CALL select(0x7f,0x81bbbc0,0,0=
,0)
1241 1 xclock 1297699912.019042214 CALL read(3,0xbb683044,0x1000)
...
1241 1 xclock 1297699913.017320137 CALL writev(3,0xbfbfeb60,3)
1241 1 xclock 1297699913.017341223 RET writev 4096/0x1000
* 1070 1 Xorg 1297699912.019036662 CSW stop kernel
1070 1 Xorg 1297699913.017344581 CSW resume kernel
1070 1 Xorg 1297699913.017350811 RET select 1
(1297699912 is the second that xclock stops at.) However, I have no
reason to suspect that this is indicative of a problem. I don't see
any ioctls or mmaps or anything like that nearby -- just a bunch of
gettimeofday, clock_gettime, setitimer, select, poll, read/v, and
write/v.<><>
From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: xsrc-manager@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org,
Taylor R Campbell <campbell+netbsd@mumble.net>
Subject: re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Tue, 15 Feb 2011 05:48:58 +1100
> From: Taylor R Campbell <campbell+netbsd@mumble.net>
> To: Martin Husemann <martin@duskware.de>
> Cc: gnats-bugs@NetBSD.org
> Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
> Date: Mon, 14 Feb 2011 15:20:26 +0000
>
> Date: Mon, 14 Feb 2011 16:05:12 +0100
> From: Martin Husemann <martin@duskware.de>
>
> Ok - so this is clearly an X server problem.
>
> OK. I submitted it under `kern' because it works under a -current
> kernel but not under a 5.1(_STABLE) kernel. (Also, I'm using X.org
> from pkgsrc, not xsrc, although I suppose the pkgsrc one is just a
> differently packaged version of the xsrc one.)
can you try xsrc?
there are significant version difference between xsrc and pkgsrc.
.mrg.
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: matthew green <mrg@eterna.com.au>
Cc: gnats-bugs@NetBSD.org, xsrc-manager@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 19:43:11 +0000
Date: Tue, 15 Feb 2011 05:48:58 +1100
From: matthew green <mrg@eterna.com.au>
can you try xsrc?
there are significant version difference between xsrc and pkgsrc.
I fetched xbase.tgz and xserver.tgz from the 5.1 FTP distribution,
extracted them in /, and then used /usr/X11R7/bin/Xorg instead of
/usr/pkg-2010Q3/bin/Xorg. Same result -- it freezes on a 5 kernel
(5.1 or 5.1_STABLE) and works on a current kernel.
I notice that drm fails in 5 and works in current, which I imagine is
probably significant. Here's a diff between the respective Xorg.0.log
files, with xsrc. It looks pretty similar for pkgsrc. RIAMONODEBUG
is i386/conf/MONOLITHIC with DIAGNOSTIC, DEBUG, LOCKDEBUG, -g, FFS_EI,
and APPLE_UFS. Let me know if you want to see the whole Xorg.0.log.
--- nb51-xsrc.txt 2011-02-14 19:24:33.000000000 +0000
+++ HEAD-RIAMONODEBUG-20110201-xsrc.txt 2011-02-14 19:35:39.000000000 +0000
@@ -3,7 +3,7 @@
Release Date: 2009-7-7
X Protocol Version 11, Revision 0
Build Operating System: NetBSD/i386 -=20
-Current Operating System: NetBSD oberon.local 5.1 NetBSD 5.1 (GENERIC) #0:=
Sun Nov 7 14:39:56 UTC 2010 builds@b6.netbsd.org:/home/builds/ab/netbsd-=
5-1-RELEASE/i386/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sy=
s/arch/i386/compile/GENERIC i386
+Current Operating System: NetBSD oberon.local 5.99.44 NetBSD 5.99.44 (RIAM=
ONODEBUG) #0: Tue Feb 1 20:55:46 UTC 2011 root@smalltalk.local:/home/rias=
tradh/netbsd/current/obj/sys/arch/i386/compile/RIAMONODEBUG i386
Build Date: 09 July 2009 12:14:03AM
=20
Before reporting problems, check http://wiki.X.Org
@@ -11,7 +11,7 @@
Markers: (--) probed, (**) from config file, (=3D=3D) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 14 19:22:41 2011
+(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 14 19:33:00 2011
(II) Loader magic: 0x800
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
@@ -302,6 +302,38 @@
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd=
0000009
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
+(WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x00000202 to 0x8=
0000202
+(WW) intel(0): PIPEBSTAT before: status: VSYNC_INT_STATUS VBLANK_INT_STATUS
+(WW) intel(0): PIPEBSTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS VBL=
ANK_INT_STATUS
+(WW) intel(0): Register 0x68000 (TV_CTL) changed from 0x10000000 to 0x000c=
0000
+(WW) intel(0): Register 0x68010 (TV_CSC_Y) changed from 0x00000000 to 0x03=
32012d
+(WW) intel(0): Register 0x68014 (TV_CSC_Y2) changed from 0x00000000 to 0x0=
7d30104
+(WW) intel(0): Register 0x68018 (TV_CSC_U) changed from 0x00000000 to 0x07=
33052d
+(WW) intel(0): Register 0x6801c (TV_CSC_U2) changed from 0x00000000 to 0x0=
5c70200
+(WW) intel(0): Register 0x68020 (TV_CSC_V) changed from 0x00000000 to 0x03=
40030c
+(WW) intel(0): Register 0x68024 (TV_CSC_V2) changed from 0x00000000 to 0x0=
6d00200
+(WW) intel(0): Register 0x6802c (TV_CLR_LEVEL) changed from 0x00000000 to =
0x010b00e1
+(WW) intel(0): Register 0x68030 (TV_H_CTL_1) changed from 0x00000000 to 0x=
00400359
+(WW) intel(0): Register 0x68034 (TV_H_CTL_2) changed from 0x00000000 to 0x=
80480022
+(WW) intel(0): Register 0x68038 (TV_H_CTL_3) changed from 0x00000000 to 0x=
007c0344
+(WW) intel(0): Register 0x6803c (TV_V_CTL_1) changed from 0x00000000 to 0x=
00f01415
+(WW) intel(0): Register 0x68040 (TV_V_CTL_2) changed from 0x00000000 to 0x=
00060607
+(WW) intel(0): Register 0x68044 (TV_V_CTL_3) changed from 0x00000000 to 0x=
80120001
+(WW) intel(0): Register 0x68048 (TV_V_CTL_4) changed from 0x00000000 to 0x=
000900f0
+(WW) intel(0): Register 0x6804c (TV_V_CTL_5) changed from 0x00000000 to 0x=
000a00f0
+(WW) intel(0): Register 0x68050 (TV_V_CTL_6) changed from 0x00000000 to 0x=
000900f0
+(WW) intel(0): Register 0x68054 (TV_V_CTL_7) changed from 0x00000000 to 0x=
000a00f0
+(WW) intel(0): Register 0x68060 (TV_SC_CTL_1) changed from 0x00000000 to 0=
xc1710087
+(WW) intel(0): Register 0x68064 (TV_SC_CTL_2) changed from 0x00000000 to 0=
x6b405140
+(WW) intel(0): Register 0x68070 (TV_WIN_POS) changed from 0x00000000 to 0x=
00360024
+(WW) intel(0): Register 0x68074 (TV_WIN_SIZE) changed from 0x00000000 to 0=
x02640198
+(WW) intel(0): Register 0x68080 (TV_FILTER_CTL_1) changed from 0x00000000 =
to 0x800010bb
+(WW) intel(0): Register 0x68084 (TV_FILTER_CTL_2) changed from 0x00000000 =
to 0x00028283
+(WW) intel(0): Register 0x68088 (TV_FILTER_CTL_3) changed from 0x00000000 =
to 0x00014141
+(WW) intel(0): Register 0x68100 (TV_H_LUMA_0) changed from 0x00000000 to 0=
xb1403000
+(WW) intel(0): Register 0x681ec (TV_H_LUMA_59) changed from 0x00000000 to =
0x0000b060
+(WW) intel(0): Register 0x68200 (TV_H_CHROMA_0) changed from 0x00000000 to=
0xb1403000
+(WW) intel(0): Register 0x682ec (TV_H_CHROMA_59) changed from 0x00000000 t=
o 0x0000b060
(II) UnloadModule: "vesa"
(II) Unloading /usr/X11R7/lib/modules/drivers//vesa_drv.so
(=3D=3D) Depth 24 pixmap format is 32 bpp
@@ -321,22 +353,34 @@
(II) intel(0): I830CheckAvailableMemory: 1966080 kB available
(WW) intel(0): DRI2 requires UXA
drmOpenDevice: node name is /dev/dri/card0
-drmOpenDevice: open result is -1, (Device not configured)
-drmOpenDevice: open result is -1, (Device not configured)
-drmOpenDevice: Open failed
+drmOpenDevice: open result is 11, (OK)
drmOpenDevice: node name is /dev/dri/card0
-drmOpenDevice: open result is -1, (Device not configured)
-drmOpenDevice: open result is -1, (Device not configured)
-drmOpenDevice: Open failed
-[drm] failed to load kernel module "i915"
-(EE) [drm] drmOpen failed.
-(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
+drmOpenDevice: open result is 11, (OK)
+drmOpenByBusid: Searching for BusID pci:0000:00:02.0
+drmOpenDevice: node name is /dev/dri/card0
+drmOpenDevice: open result is 11, (OK)
+drmOpenByBusid: drmOpenMinor returns 11
+drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
+(II) [drm] DRM interface version 1.2
+(II) [drm] DRM open master succeeded.
+(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
+(II) intel(0): [drm] framebuffer mapped by ddx driver
+(II) intel(0): [drm] added 1 reserved context for kernel
+(II) intel(0): X context handle =3D 0x1
+(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(=3D=3D) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
-(II) intel(0): adjusting plane->pipe mappings to allow for framebuffer com=
pression
+(II) intel(0): [drm] Registers =3D 0x90380000
+(II) intel(0): [drm] ring buffer =3D 0x80000000
+(II) intel(0): [drm] mapped front buffer at 0x81000000, handle =3D 0x81000=
000
+(II) intel(0): [drm] mapped back buffer at 0x84000000, handle =3D 0x840000=
00
+(II) intel(0): [drm] mapped depth buffer at 0x85000000, handle =3D 0x85000=
000
+(II) intel(0): [drm] mapped classic textures at 0x86000000, handle =3D 0x8=
6000000
+(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
+(II) intel(0): [dri] visual configs initialized
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x=
0000
(WW) intel(0): remove MTRR a0000 - b0000
(II) EXA(0): Offscreen pixmap area of 31457280 bytes
@@ -347,10 +391,14 @@
(=3D=3D) intel(0): Backing store disabled
(=3D=3D) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
+(II) intel(0): [DRI] installation complete
(WW) intel(0): drmDropMaster failed: Unknown error: 4294967295
(II) intel(0): Current clock rate multiplier: 1
-(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x01000000 (pgoffset 4096)
-(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x02000000 (pgoffset 8192)
+(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x01000000 (pgoffset 4096)
+(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02000000 (pgoffset 8192)
+(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x04000000 (pgoffset 1638=
4)
+(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x05000000 (pgoffset 2048=
0)
+(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x06000000 (pgoffset 2457=
6)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x0061ffff: compressed frame buffer (6144 kB, 0x=
000000007f020000 physical
@@ -365,25 +413,29 @@
(II) intel(0): 0x00fbf000: end of stolen memory
(II) intel(0): 0x01000000-0x01ffffff: front buffer (16384 kB) X tiled
(II) intel(0): 0x02000000-0x03dfffff: exa offscreen (30720 kB)
+(II) intel(0): 0x04000000-0x04ffffff: back buffer (16384 kB) X tiled
+(II) intel(0): 0x05000000-0x05ffffff: depth buffer (16384 kB) X tiled
+(II) intel(0): 0x06000000-0x07ffffff: classic textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
-(WW) intel(0): ESR is 0x00000011, page table error, instruction error
+(WW) intel(0): ESR is 0x00000010, page table error
(WW) intel(0): PGTBL_ER is 0x00000102, host pte data, display B pte
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is off
-(II) intel(0): Display plane B is now disabled and connected to pipe A.
+(II) intel(0): Display plane A is now disabled and connected to pipe A.
(II) intel(0): Pipe B is on
-(II) intel(0): Display plane A is now enabled and connected to pipe B.
+(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TMDS-1 is connected to pipe none
(II) intel(0): Output TV is connected to pipe none
+(II) intel(0): [drm] dma control initialized, using IRQ 10
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled mess=
age.
(II) intel(0): DPMS enabled
(II) intel(0): Set up textured video
(II) intel(0): Set up overlay video
-(II) intel(0): direct rendering: Failed
+(II) intel(0): direct rendering: XF86DRI Enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
@@ -402,9 +454,19 @@
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
-(II) AIGLX: Screen 0 is not DRI capable
-(II) AIGLX: Loaded and initialized /usr/X11R7/lib/modules/dri/swrast_dri.so
-(II) GLX: Initialized DRISWRAST GL provider for screen 0
+drmOpenDevice: node name is /dev/dri/card0
+drmOpenDevice: open result is 12, (OK)
+drmOpenByBusid: Searching for BusID pci:0000:00:02.0
+drmOpenDevice: node name is /dev/dri/card0
+drmOpenDevice: open result is 12, (OK)
+drmOpenByBusid: drmOpenMinor returns 12
+drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
+(II) AIGLX: enabled GLX_SGI_make_current_read
+(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
+(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
+(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
+(II) AIGLX: Loaded and initialized /usr/X11R7/lib/modules/dri/i915_dri.so
+(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 286 x 179
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: found Device "/dev/wsmouse"
@@ -440,18 +502,25 @@
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 8=
03 809 823 -hsync -vsync (49.3 kHz)
(II) intel(0): EDID vendor "APP", prod id 40027
-(II) intel(0): xf86BindGARTMemory: bind key 6 at 0x03e00000 (pgoffset 1587=
2)
-(II) intel(0): xf86UnbindGARTMemory: unbind key 6
+(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x08000000 (pgoffset 3276=
8)
+(II) intel(0): [drm] mapped front buffer at 0x81000000, handle =3D 0x81000=
000
+(II) intel(0): xf86UnbindGARTMemory: unbind key 5
(II) intel(0): EDID vendor "APP", prod id 40027
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 8=
03 809 823 -hsync -vsync (49.3 kHz)
(II) intel(0): EDID vendor "APP", prod id 40027
-(II) intel(0): xf86BindGARTMemory: bind key 7 at 0x03e00000 (pgoffset 1587=
2)
-(II) intel(0): xf86UnbindGARTMemory: unbind key 7
+(II) intel(0): xf86BindGARTMemory: bind key 6 at 0x08000000 (pgoffset 3276=
8)
+(II) intel(0): xf86UnbindGARTMemory: unbind key 6
(II) UnloadModule: "mouse"
(II) UnloadModule: "kbd"
+(II) intel(0): xf86UnbindGARTMemory: unbind key 0
+(II) intel(0): xf86UnbindGARTMemory: unbind key 1
+(II) intel(0): xf86UnbindGARTMemory: unbind key 2
+(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4
-(II) intel(0): xf86UnbindGARTMemory: unbind key 5
(WW) intel(0): drmDropMaster failed: Unknown error: 4294967295
+(II) intel(0): [drm] removed 1 reserved context for kernel
+(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xc3750000 at 0xbb63b000
+(II) intel(0): [drm] Closed DRM master.
From: Bernd Ernesti <netbsd@lists.veego.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 20:49:40 +0100
On Mon, Feb 14, 2011 at 07:45:02PM +0000, Taylor R Campbell wrote:
[..]
> I fetched xbase.tgz and xserver.tgz from the 5.1 FTP distribution,
> extracted them in /, and then used /usr/X11R7/bin/Xorg instead of
> /usr/pkg-2010Q3/bin/Xorg. Same result -- it freezes on a 5 kernel
> (5.1 or 5.1_STABLE) and works on a current kernel.
>
> I notice that drm fails in 5 and works in current, which I imagine is
> probably significant. Here's a diff between the respective Xorg.0.log
> files, with xsrc. It looks pretty similar for pkgsrc. RIAMONODEBUG
> is i386/conf/MONOLITHIC with DIAGNOSTIC, DEBUG, LOCKDEBUG, -g, FFS_EI,
> and APPLE_UFS. Let me know if you want to see the whole Xorg.0.log.
You have a 5.1 kernel with drm enabled for the intel driver?
Bernd
From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: xsrc-manager@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org,
Taylor R Campbell <campbell+netbsd@mumble.net>
Subject: re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Tue, 15 Feb 2011 07:47:12 +1100
> You have a 5.1 kernel with drm enabled for the intel driver?
good point. 5.1 does not enable drm drivers by default like
-current does.
.mrg.
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@NetBSD.org
Cc: xsrc-manager@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, Bernd Ernesti <netbsd@lists.veego.de>
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Mon, 14 Feb 2011 20:49:46 +0000
Date: Mon, 14 Feb 2011 20:49:40 +0100
From: Bernd Ernesti <netbsd@lists.veego.de>
You have a 5.1 kernel with drm enabled for the intel driver?
No, all the 5.1ish kernels I have described so far have lacked any
drm, as far as I can tell.
I just tried explicitly loading the drm and i915drm modules into a
5.1_STABLE kernel with modload. Now if I launch X under that kernel,
from either xsrc or pkgsrc, it works. I haven't tried disabling drm
in a current kernel, since there it's not a module I can just unload.
But so far it looks like X works with drm and fails without it here.
From: Bernd Ernesti <netbsd@lists.veego.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Wed, 16 Feb 2011 21:19:56 +0100
On Mon, Feb 14, 2011 at 08:49:46PM +0000, Taylor R Campbell wrote:
> Date: Mon, 14 Feb 2011 20:49:40 +0100
> From: Bernd Ernesti <netbsd@lists.veego.de>
>
> You have a 5.1 kernel with drm enabled for the intel driver?
>
> No, all the 5.1ish kernels I have described so far have lacked any
> drm, as far as I can tell.
>
> I just tried explicitly loading the drm and i915drm modules into a
> 5.1_STABLE kernel with modload. Now if I launch X under that kernel,
> from either xsrc or pkgsrc, it works. I haven't tried disabling drm
> in a current kernel, since there it's not a module I can just unload.
> But so far it looks like X works with drm and fails without it here.
So we can close this pr?
I don't think we will enable drm in netbsd-5 in the default configuration.
Bernd
P.S. It is enough if you reply to gnats-bugs@NetBSD.org which then sends
the mail out to netbsd-bugs@NetBSD.org after it is recorded in the gnats
database
From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Wed, 16 Feb 2011 20:58:01 +0000
Date: Wed, 16 Feb 2011 21:19:56 +0100
From: Bernd Ernesti <netbsd@lists.veego.de>
On Mon, Feb 14, 2011 at 08:49:46PM +0000, Taylor R Campbell wrote:
> I just tried explicitly loading the drm and i915drm modules into a
> 5.1_STABLE kernel with modload. Now if I launch X under that kernel,
> from either xsrc or pkgsrc, it works. I haven't tried disabling drm
> in a current kernel, since there it's not a module I can just unload.
> But so far it looks like X works with drm and fails without it here.
So we can close this pr?
I don't think we will enable drm in netbsd-5 in the default configuratio=
n.
Hmm... If you don't plan to enable drm, then there's still a problem.
I just checked a current kernel with and without drm: it worked with,
and froze without, just like in 5.1. I checked both xsrc and pkgsrc.
So it seems pretty clear that X is broken without drm.
P.S. It is enough if you reply to gnats-bugs@NetBSD.org which then sends
the mail out to netbsd-bugs@NetBSD.org after it is recorded in the gnats
database
OK, sorry. I usually just reply-all, to make sure everyone interested
gets the message whether or not they are on netbsd-bugs or whatever is
the relevant mailing list. (I, for instance, am not on netbsd-bugs.)
From: Bernd Ernesti <netbsd@lists.veego.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1
Date: Wed, 16 Feb 2011 22:27:32 +0100
On Wed, Feb 16, 2011 at 09:00:07PM +0000, Taylor R Campbell wrote:
> Date: Wed, 16 Feb 2011 21:19:56 +0100
> From: Bernd Ernesti <netbsd@lists.veego.de>
>
> On Mon, Feb 14, 2011 at 08:49:46PM +0000, Taylor R Campbell wrote:
> > I just tried explicitly loading the drm and i915drm modules into a
> > 5.1_STABLE kernel with modload. Now if I launch X under that kernel,
> > from either xsrc or pkgsrc, it works. I haven't tried disabling drm
> > in a current kernel, since there it's not a module I can just unload.
> > But so far it looks like X works with drm and fails without it here.
>
> So we can close this pr?
>
> I don't think we will enable drm in netbsd-5 in the default configuratio=
> n.
>
> Hmm... If you don't plan to enable drm, then there's still a problem.
In -current it is enabled by default.
NetBSD 5.1 (netbsd-5) is a different story because not all changes from -current
are back ported so it may be not so stable if we enable it by default.
For 5.1 you can load the kmod with /boot.cfg
> I just checked a current kernel with and without drm: it worked with,
> and froze without, just like in 5.1. I checked both xsrc and pkgsrc.
> So it seems pretty clear that X is broken without drm.
For the intel gfx chipset. For others it is not so much of an issue.
Bernd
State-Changed-From-To: open->feedback
State-Changed-By: maya@NetBSD.org
State-Changed-When: Sun, 25 Nov 2018 18:17:57 +0000
State-Changed-Why:
sounds like it was fixed in -current when -current meant -6, which means all supported releases have the fix. thoughts?
State-Changed-From-To: feedback->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Sun, 25 Nov 2018 20:38:05 +0000
State-Changed-Why:
code is all different; this PR is no longer relevant
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home