Date: Fri, 5 Sep 2014 00:30:15 -0700 From: Mark Millard <markmi@dsl-only.net> To: Justin Hibbits <chmeeedalf@gmail.com> Cc: freebsd-ppc@freebsd.org Subject: Re: Xorg/xfce4 failing on Dual Processor G4 PowerMac's BUT Single Processor G4 PowerMac works (same boot SSD)... Message-ID: <7DBCD5B4-6346-44D0-81DE-60FA05E50125@dsl-only.net> In-Reply-To: <20140904200118.322b2bfb@zhabar.attlocal.net> References: <4D86DDCB-FF04-4EA2-9703-8B74BBF31C7E@dsl-only.net> <EDE36402-30CE-4747-8BDD-EDD82D8C308F@dsl-only.net> <D42F3E26-8D35-4C8B-A695-AA380ED888E1@dsl-only.net> <EF019CAD-6BAB-431D-A239-0644C0634C24@dsl-only.net> <540386C6.4060004@freebsd.org> <7AFF7E0F-6BB0-4972-A629-61910CE001C2@dsl-only.net> <540393F3.5060508@freebsd.org> <D53F6E61-13E3-4473-ABAD-F72BD86E1083@dsl-only.net> <2B74B670-7463-47D1-B0AF-BDBFEE8823A4@dsl-only.net> <1B729E38-6495-4240-B9E2-A48238E4E830@dsl-only.net> <D960F3AF-7498-4222-96E9-654E9B672EF7@dsl-only.net> <38A1300F-E5A4-4A71-A9CF-A7BED66E0BDF@dsl-only.net> <5408976A.5080106@freebsd.org> <6DE6C98D-F553-4F59-A72A-AEA881DC1C65@dsl-only.net> <3D7C705D-5792-43FA-835C-9FD88AEAE07E@dsl-only.net> <20140904200118.322b2bfb@zhabar.attlocal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the future MFC'd updates. I see that as of yesterday (Sept-3) powerpc/GENERIC and = powerpc64/GENERIC64 builds are again updating in places like (now) = http://ftp.freebsd.org/pub/FreeBSD/snapshots/powerpc/powerpc*/10.1-PRERELE= ASE/ . Before that the most recent had been from July-13 or so. So I'm fine with waiting from that point of view. It now appears that = I'll be able to pick up the update when it shows up in 10.1-????? . I've = not done anything with head/current yet. I'll probably try to at least = track = http://ftp.freebsd.org/pub/FreeBSD/snapshots/powerpc/powerpc*/10.1-*/ = (with some lag). (My FreeBSD explorations/experiments are a background = task in general and I may end up having to juggle disks, repartition, or = do other extra things first as well.) But Nathan W. may well want experiments in time frames attempting to = given him time before 10.1-RELEASE --especially if I have access to = hardware combinations that he does not or for which "his" similar = machines have other far more dedicated uses to avoid interrupting. I'm = free to do whatever I want with the ones around here. I am happy to see what I can do that Nathan thinks might help --but I = can not promise specific time frames either. And it is easy to send me = off doing something that I've not done before with FreeBSD where I end = up having research-time/learning-curve-time involved. And such efforts = always have questions of completeness for what is found/learned. Not being able to do things under powerpc/GENERIC that I can do under = powerpc64/GENERIC64 is making this investigation more difficult because = the original Xorg problems are only seen under powerpc/GENERIC --and so = far only on dual-processor G4 PowerMacs. I had hoped to have Xorg run = under gdb with debug symbols around (world, kernel, and ports) on those = G4 PowerMacs. But running Xorg under gdb turned out to work only under = powerpc64/GENERIC64 where I can not see the original Xorg problem (so = far). That illustrates that I learn more about the status of powerpc/GENERIC = and powerpc64/GENERIC64 10.x FreeBSD as I go: I would not have guessed = the gdb behavioral difference as likely. Hopefully I'll get the PowerMac SSD's (powerpc/GENERIC and = powerpc64/GENERIC64) synchronized to the two = http://ftp.freebsd.org/pub/FreeBSD/snapshots/powerpc/powerpc*/10.1-PRERELE= ASE/ areas before the weekend is over. I may start retesting without = debug symbols since rebuilding to have them takes a while. (And unless = gdb Xorg can work on a G4 the symbols would be of little immediate use.) =3D=3D=3D Mark Millard markmi at dsl-only.net On Sep 4, 2014, at 8:01 PM, Justin Hibbits <chmeeedalf@gmail.com> wrote: I was reminded that there are a couple patches I've neglected to MFC related to signal handling that might solve this problem. I hope to get them in over the next couple days, so you can expect them in the 10.1 betas. If you don't want to wait for that, could you try head? Thanks, Justin On Thu, 4 Sep 2014 18:46:29 -0700 Mark Millard <markmi@dsl-only.net> wrote: > The radeon G4 contexts do not report "failed to set mtrr: File > exists": They seem to be silent about Xorg quitting early as far as > error messages or warnings go (booted from that same SSD with > xorg.conf for the radeon context). Again Xorg.0.log does not look > interesting and stops before the problem. A script logfile shows: >=20 >> root@FBSDG4S0:~ # startxfce4 -- -logverbose 9^M >> /usr/local/bin/startxfce4: Starting X server >>=20 >>=20 >> X.Org X Server 1.12.4 >> Release Date: 2012-08-27 >> X Protocol Version 11, Revision 0 >> Build Operating System: FreeBSD 10.0-STABLE powerpc=20 >> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD >> 10.0-STABLE #0: T hu Sep 4 00:50:31 PDT 2014 >> root@FBSDG4S0:/usr/obj/usr/src/sys/GENERIC power pc >> Build Date: 04 September 2014 06:13:34AM >>=20 >> Current version of pixman: 0.32.4 >> Before reporting problems, check http://wiki.x.org >> to make sure that you have the latest version. >> 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: Thu Sep 4 >> 18:20:03 2014 (=3D=3D) Using config file: "/etc/X11/xorg.conf" >> XRANDR name: DVI-1 >> Connector: DVI-I >> CRT2: INTERNAL_DAC2 >> DFP1: INTERNAL_TMDS1 >> DDC reg: 0x64 >> XRANDR name: DVI-0 >> Connector: DVI-I >> CRT1: INTERNAL_DAC1 >> DFP2: INTERNAL_DVO1 >> DDC reg: 0x60 >> XRANDR name: S-video >> Connector: S-video >> TV1: INTERNAL_DAC2 >> DDC reg: 0x0 >> finished output detect: 0 >> Unhandled monitor type 0 >> finished output detect: 1 >> finished output detect: 2 >> finished all detect >> Unhandled monitor type 0 >> Entering TV Save >> Save TV timing tables >> saveTimingTables: reading timing tables >> TV Save done >> disable FP1 >> disable FP1 >> disable TV >> disable FP1 >> init memmap >> init common >> init crtc1 >> init pll1 >> freq: 117130000 >> best_freq: 117132353 >> best_feedback_div: 295 >> best_frac_feedback_div: 0 >> best_ref_div: 34 >> best_post_div: 2 >> restore memmap >> restore common >> restore crtc1 >> restore pll1 >> finished PLL1 >> set RMX >> set FP1 >> enable FP1 >> disable TV >> xfce4-session: Fatal IO error 35 (Resource temporarily unavailable) >> on X server :0. xfwm4: Fatal IO error 35 (Resource temporarily >> unavailable) on X server :0.0. xinit: connection to X server lost >=20 >=20 > =3D=3D=3D > Mark Millard > markmi@dsl-only.net >=20 > On Sep 4, 2014, at 6:00 PM, Mark Millard <markmi@dsl-only.net> wrote: >=20 > The below includes it reporting getting a "failed to set mtrr: File > exists" notice. (A Intel P6+ concept?) >=20 >=20 > I have since rebuilt (buildworld, kernel, installworld; portmaster > -af) from the same /usr/src/... and /usr/ports/... on that same SSD > based on /etc/make.conf having: >=20 > WITH_DEBUG_FILES=3D > WITHOUT_CLANG=3D # because otherwise it leads to buildworld failures > with the above enabled WITH_DEBUG=3D >=20 > Unfortunately uname -a loses the r268571 reference in the process, > leaving less of a clue what the build is based on. >=20 > In this context the script logfile for running on a PowerMac G4 ends > up recording "failed to set mtrr: File exists": >=20 >> root@FBSDG4S0:~ # startxfce4 -- -logverbose 9^M >> /usr/local/bin/startxfce4: Starting X server >>=20 >>=20 >> X.Org X Server 1.12.4 >> Release Date: 2012-08-27 >> X Protocol Version 11, Revision 0 >> Build Operating System: FreeBSD 10.0-STABLE powerpc=20 >> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD >> 10.0-STABLE #0: Thu Sep 4 00:50:31 PDT 2014 >> root@FBSDG4S0:/usr/obj/usr/src/sys/GENERIC powerpc Build Date: 04 >> September 2014 06:13:34AM Current version of pixman: 0.32.4 >> Before reporting problems, check http://wiki.x.org >> to make sure that you have the latest version. >> 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: Thu Sep 4 >> 15:14:07 2014 (=3D=3D) Using config file: "/etc/X11/xorg.conf" >> failed to set mtrr: File exists >> xfce4-session: Fatal IO error 35 (Resource temporarily unavailable) >> on X server :0. xinit: connection to X server lost >> root@FBSDG4S0:~ # xfwm4: Fatal IO error 35 (Resource temporarily >> unavailable) on X server :0.0. root@FBSDG4S0:~ #=20 >=20 > The G5 PowerMac does not display the "failed to set mtrr: File > exists" message when booted from the same boot SSD and startxfce4 -- > -logverbose 9 is used (but with xorg.conf's BusID changed to match > the PowerMac7,11's BusID). The G5 context works fine. (I've not tried > the single processor G4 context yet.) >=20 > Note: I'm using the G4 NVIDIA PowerMac for most G4 expirements > because it allows me to Option-Fn to get to VTn and see thing there > and so I can avoid reboots. >=20 >=20 > The last thing that dmesg -a shows after the G4 startxfce4 -- > -logverbose 9 is my logging in as root: >=20 >> $ dmesg -a | tail >> Configuring syscons: blanktime. >> Performing sanity check on sshd configuration. >> Starting sshd. >> Starting sendmail_submit. >> Starting sendmail_msp_queue. >> Starting cron. >> Starting background file system checks in 60 seconds. >>=20 >> Thu Sep 4 14:21:42 PDT 2014 >> Sep 4 14:21:48 FBSDG4S0 login: ROOT LOGIN (root) ON ttyv0 >=20 > I do not see anything earlier that looks to be of interest. About the > only thing remotely error-like are some examples of "hid_get_item: > Number of items truncated to 255". >=20 >=20 > /var/log/Xorg.0.log's ends in: >=20 >> [ 182.354] (II) Module mouse: vendor=3D"X.Org Foundation" >> [ 182.354] compiled for 1.12.4, module version =3D 1.9.0 >> [ 182.354] Module class: X.Org XInput Driver >> [ 182.354] ABI class: X.Org XInput driver, version 16.0 >> [ 182.354] (II) Using input driver 'mouse' for 'Apple Optical USB >> Mouse' [ 182.354] (**) Apple Optical USB Mouse: always reports >> core events [ 182.354] (**) Option "Device" "/dev/sysmouse" >> [ 182.354] (=3D=3D) Apple Optical USB Mouse: Protocol: "Auto" >> [ 182.354] (**) Apple Optical USB Mouse: always reports core >> events [ 182.355] (=3D=3D) Apple Optical USB Mouse: = Emulate3Buttons, >> Emulate3Timeout: 50 [ 182.355] (**) Apple Optical USB Mouse: >> ZAxisMapping: buttons 4 and 5 [ 182.355] (**) Apple Optical USB >> Mouse: Buttons: 5 [ 182.355] (**) Option "config_info" >> "hal:/org/freedesktop/Hal/devices/usb_device_5ac_304_noserial_if0" [ = 182.355] >> (II) XINPUT: Adding extended input device "Apple Optical USB >> Mouse" (type: MOUSE, id 7) [ 182.356] (**) Apple Optical USB >> Mouse: (accel) keeping acceleration scheme 1 [ 182.356] (**) >> Apple Optical USB Mouse: (accel) acceleration profile 0 >> [ 182.356] (**) Apple Optical USB Mouse: (accel) acceleration >> factor: 2.000 [ 182.356] (**) Apple Optical USB Mouse: (accel) >> acceleration threshold: 4 [ 182.356] (II) Apple Optical USB >> Mouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 182.356] (II) >> Apple Optical USB Mouse: SetupAuto: protocol is SysMouse >=20 > I.e., the Xorg quit is silent. Again I do not see anything earlier > that looks to be of interest. >=20 >=20 >=20 > Xorg is suddenly, silently quitting. And it is leaving all associated > log files with older modification date/times/content from what I can > tell. No core file either. "failed to set mtrr: File exists" may > explain this. I've not started investigating it yet. >=20 >=20 >=20 > Side notes: >=20 > I've not investigated yet if there is a way around gdb Xorg's run :0 > under powerpc/GENERIC getting: >=20 >> cannot get thread event message: generic error >=20 >=20 > and gdb's cont then getting: >=20 >> suspend error: generic error >=20 >=20 > I've also seen for other things I've tried with Xorg involved: >=20 >> cannot find new threads: generic error >=20 >=20 > and >=20 >> no thread to satisfy query >=20 >=20 > On the G5 PowerMac's using powerpc64/GENERIC64 boot SSD's I have no > such problems with threading for gdb Xorg: only the powerpc/GENERIC > boot SSD's have this problem and the gdb thread issues happen on G4's > and G5's when booted from powerpc/GENERIC boot SSD's. >=20 >=20 >=20 > =3D=3D=3D > Mark Millard > markmi@dsl-only.net >=20 > On Sep 4, 2014, at 9:46 AM, Nathan Whitehorn <nwhitehorn@freebsd.org> > wrote: >=20 > Anything in dmesg or in /var/log/Xorg.0.log? What happens if you set > logverbose 9? -Nathan >=20 > On 08/31/14 17:27, Mark Millard wrote: >> As an example of how sudden and arbitrary the silent-quit of the X >> server is: >>=20 >> The partial display update currently on my ADC display has >> approximating the top 1/2 updated and the bottom half not updated >> (still black). >>=20 >> But the boundary is somewhat interesting: The last updated >> raster/pixel line has its left side updated (a uniform grey desktop >> color) and its right side not updated (still black). >>=20 >> So the silent abort stopped the update mid-raster/pixel line. >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >>=20 >> On Aug 31, 2014, at 4:49 PM, Mark Millard <markmi@dsl-only.net> >> wrote: >>=20 >> [E-mail history trimmed this time.] >>=20 >> I used script to log my startxfce4 command and what it produces. >> With only the ADC connected this results in various "Unhandled >> monitor type 0" notices as part of normal operation. >>=20 >> The script output shows that the X server quit. There is no core >> file left in the directory. >>=20 >> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X >> server :0. xfwm4: Fatal IO error 35 (Resource temporarily >> unavailable) on X server :0.0. xinit: connection to X server lost >> xfdesktop: Fatal IO error 35 (Resource temporarily unavailable) on >> X server :0.0. >>=20 >> (xfsettingsd:984): GVFS-RemoteVolumeMonitor-WARNING **: invoking >> IsSupported() failed for remote volume monitor with dbus name >> org.gtk.Private.GPhoto2VolumeMonitor: >> org.freedesktop.DBus.Error.Disconnected: Connection was >> disconnected before a reply was received root@FBSDG4S0:~ # >> xfsettingsd: Fatal IO error 2 (No such file or directory) on X >> server :0.0. >>=20 >> The full script file contents are: >>=20 >> Script started on Sun Aug 31 16:34:12 2014 >> You have mail. >> root@FBSDG4S0:~ # startxfce4^M >> /usr/local/bin/startxfce4: Starting X server >>=20 >>=20 >> X.Org X Server 1.12.4 >> Release Date: 2012-08-27 >> X Protocol Version 11, Revision 0 >> Build Operating System: FreeBSD 10.0-STABLE powerpc=20 >> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD >> 10.0-STABLE #0 r268571: Sun Jul 13 05:15:31 UTC 2014 >> root@grind.freebsd.org:/usr/obj/powerpc.powerpc/usr/src/sys/GENERIC >> powerpc Build Date: 21 July 2014 07:18:49PM Current version of >> pixman: 0.32.4 Before reporting problems, check http://wiki.x.org >> to make sure that you have the latest version. >> 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: Sun Aug 31 >> 16:34:23 2014 (=3D=3D) Using config file: "/etc/X11/xorg.conf" >> XRANDR name: DVI-1 >> Connector: DVI-I >> CRT2: INTERNAL_DAC2 >> DFP1: INTERNAL_TMDS1 >> DDC reg: 0x64 >> XRANDR name: DVI-0 >> Connector: DVI-I >> CRT1: INTERNAL_DAC1 >> DFP2: INTERNAL_DVO1 >> DDC reg: 0x60 >> XRANDR name: S-video >> Connector: S-video >> TV1: INTERNAL_DAC2 >> DDC reg: 0x0 >> finished output detect: 0 >> Unhandled monitor type 0 >> finished output detect: 1 >> finished output detect: 2 >> finished all detect >> Unhandled monitor type 0 >> Entering TV Save >> Save TV timing tables >> saveTimingTables: reading timing tables >> TV Save done >> disable FP1 >> disable FP1 >> disable TV >> disable FP1 >> init memmap >> init common >> init crtc1 >> init pll1 >> freq: 117130000 >> best_freq: 117132353 >> best_feedback_div: 295 >> best_frac_feedback_div: 0 >> best_ref_div: 34 >> best_post_div: 2 >> restore memmap >> restore common >> restore crtc1 >> restore pll1 >> finished PLL1 >> set RMX >> set FP1 >> enable FP1 >> disable TV >> Unhandled monitor type 0 >> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X >> server :0. xfwm4: Fatal IO error 35 (Resource temporarily >> unavailable) on X server :0.0. xinit: connection to X server lost >> xfdesktop: Fatal IO error 35 (Resource temporarily unavailable) on >> X server :0.0. >>=20 >> (xfsettingsd:984): GVFS-RemoteVolumeMonitor-WARNING **: invoking >> IsSupported() failed for remote volume monitor with dbus name >> org.gtk.Private.GPhoto2VolumeMonitor: >> org.freedesktop.DBus.Error.Disconnected: Connection was >> disconnected before a reply was received root@FBSDG4S0:~ # >> xfsettingsd: Fatal IO error 2 (No such file or directory) on X >> server :0.0. >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >>=20 >>=20 >>=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7DBCD5B4-6346-44D0-81DE-60FA05E50125>