Re: Bug#814702: ghostscript: FTBFS on sparc64 due to mismatched symbols file
The memory hdr_id is disabled on SPARC because it relies on memory accesses that aren't sufficiently aligned for SPARC - IIRC, it's aligned to sizeof(void *) which doesn't work fully on SPARC systems, but I could be wrong (I'm not looking at the sources right now). If the failure is due to it being enable on x86 (and most other platforms) and not on SPARC, either Debian could opt to disable the hdr_id stuff for all platforms, or I can look into making it work correctly on SPARC. I have to confess, even though I added it to Ghostcript, I was at the the time, and still am, unconvinced of its utility Chris On 14/02/16 11:25, John Paul Adrian Glaubitz wrote: Source: ghostscript Version: 9.16~dfsg-2.1 Severity: normal User: debian-sparc@lists.debian.org Usertags: sparc64 Hello! ghostscript currently fails to build from source on sparc64 due to a mismatched symbols file: dpkg-gensymbols: warning: debian/libgs9/DEBIAN/symbols doesn't match completely debian/libgs9.symbols --- debian/libgs9.symbols (libgs9_9.16~dfsg-2.1_sparc64) +++ dpkg-gensymbolsIeNygU 2016-02-04 01:22:29.643520921 + @@ -3332,7 +3332,7 @@ gxht_thresh_planes@Base 9.05~ hc_put_code_proc@Base 8.61.dfsg.1 hc_put_last_bits_proc@Base 8.61.dfsg.1 - hdr_id@Base 9.10~dfsg +#MISSING: 9.16~dfsg-2.1# hdr_id@Base 9.10~dfsg height@Base 8.61.dfsg.1 ht_order_procs_table@Base 8.61.dfsg.1 #MISSING: 9.00~dfsg-1# iWrite2@Base 8.61.dfsg.1 @@ -4004,6 +4004,7 @@ pixel_image_params@Base 8.61.dfsg.1 pixmap_high_level_pattern@Base 9.10~dfsg plane_device_init@Base 8.61.dfsg.1 + png_push_fill_buffer@Base 9.16~dfsg-2.1 pop_estack@Base 8.61.dfsg.1 pprintd1@Base 8.61.dfsg.1 pprintd2@Base 8.61.dfsg.1 dh_makeshlibs: failing due to earlier errors The simple and obvious fix would be to mark the "hdr_id" symbol on sparc64 as missing which I have already done for the package in the 'unreleased' suite, (arch!=sparc64) hdr_id@Base 9.10~dfsg which works fine. However, I think it would be better to figure out first why this particular symbol is missing on sparc64 and whether this poses any problem. So far, the patched version seems to work without issues and we therefore might just go ahead and patch the symbols file as suggested, but it would be still be good if someone could have a deeper look at this. Maybe it's any of the (transitive) build dependencies of ghostscript which need to be rebuilt? Cheers, Adrian
Re: bus error in ps2pdf
On 17/02/11 18:20, Julien Cristau wrote: On Thu, Feb 17, 2011 at 18:12:25 +, c...@spamcop.net wrote: I now have access to a Debian Sparc box, and I can reproduce the problem. The crash happens in the pthreads library, and I find it confusing that this should happen on Linux/Sparc, but no other platforms (that I'm aware of). Looking at the code, there's nothing immediately obvious, unless there is a bug packing unions into structs, causing a pointer alignment problem. Actually, that does seem to be the problem: the second union does not sit on a 64 bit aligned boundary. Yes, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613642#17 Ah, cool. Very strange: that stuff doesn't seem to have changed since 8.71. Anyway, if you want to raise a bug over at bugs.ghostscript.com with the results of your investigation and assign it to me (chris.liddell (at) artifex.com), I'll make sure it gets addressed in our repos. As I said, in the immediate term, disabling the threading is a low risk, (currently) low impact workaround for this. Cheers, Chris -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5d6ffa.2090...@spamcop.net
Re: Debian-Sparc on a Sun Ultra10
I had the same problem on my Blade 1000, and Jurij kindly pointed my at the solution, so I'll quote: This is a known problem. Kernel 2.6.30 incorrectly reported machine type to the installer, so SILO was installing incorrect bootloader (intended for 32-bit machines) during the installation, causing this boot failure. See the following message: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570264#10 which includes a workaround for it. It will get fixed automatically once we get newer kernel for the installer images, daily images might already have 2.6.32, which should work out of the box. HTH, Chris On 31/03/2010 10:53, philo wrote: hi |Fast Data Access MMU MISS i have a same problem, it 's about silo error, it work on 32bit, i don't know how to activate 64bit. see you philo | M. S a écrit : Hello, i have a Sun Ultra 10, 440mhz UltraSparc IIi CPU + 1gb Ram + 60gb IDE-HDD. After the Install via Netboot, i type boot disk, and i became this Error: |Booting with command: boot disk Boot device: disk Fast Data Access MMU MISS ok Solaris 10 works fine, i think the Hardware is okay, but i dont know how i can start Debiansparc. What i have to do to start Debian-Sparc. So Long M | No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.791 / Virus Database: 271.1.1/2780 - Release Date: 03/30/10 19:32:00 -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bb32784.5080...@spamcop.net
Re: dazed and confused: install issue on Blade 1000
Hi Dirk, I didn't get any errors in the Xorg.0.log, but your suggestion worked, so I now have X working. I haven't got the resolution I want, but I can play with that. Onto the next problem: noisy fans... Thanks for the help - *much* appreciated. Chris On 22/03/2010 15:04, Dirk Dettmann Mailinglisten wrote: Hi Chris, as fas as I know the PGX64 is identical to a ATI 3D Rage XL. I had the same difficulties you mentioned with my Blade 150 and the onboard graphic (yes, it's the same one). In my special case there was no modul mach64 because of security reasons in the debian netinstall kernel. I found a FATAL: Module mach64 not found. in /var/log/Xorg.0.log. I solved this by getting the sources form http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 building an new kernel with mach64 support an installing it on the blade 150. My xorg.conf is the following one: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath built-ins EndSection Section Module Load extmod Load dri2 Load dbe Load record Load dri Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/input/mice Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync 30-65 VertRefresh 50-75 Option DPMS EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option probe_sparse# [bool] #Option accel # [bool] #Option crt_display # [bool] #Option composite_sync # [bool] #Option hw_cursor # [bool] #Option force_pci_mode # [bool] #Option dma_mode# str #Option agp_mode# i #Option agp_size# i #Option local_textures # [bool] #Option buffer_size # i #Option mmio_cache # [bool] #Option test_mmio_cache # [bool] #Option panel_display # [bool] #Option reference_clock # freq #Option shadow_fb # [bool] #Option sw_cursor # [bool] #Option AccelMethod # str #Option RenderAccel # [bool] Identifier Card0 Driver mach64 VendorName ATI Technologies Inc BoardName Rage XL BusID PCI:0:19:0 Option reference_clock 29.500 MHz EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth24 SubSection Display Viewport 0 0 Depth 24 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection gdm is up and running. I just made the installation yesterday, but it seems running stable. Have a nice day Dirk No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.791 / Virus Database: 271.1.1/2762 - Release Date: 03/21/10 19:33:00 -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ba94bbc.2050...@spamcop.net
dazed and confused: install issue on Blade 1000
Hi, I've been trying to get Debian (most recently, the weekly testing release) installed on my Blade 1000. Now the install apparently goes fine, no errors or such. But when install complete, the machine reboots and throws a fast data access mmu miss error, and this is before even the S of SILO appears. This is installing on an as nearly blank HDD as I can manage, without actually buying a new HDD (I blanked the entire device with dd), and using the default guided partitioning scheme. Any suggestions? It's quite frustrating that everything seems to go so smoothly, only to conk out at the (almost) final step. Thanks, Chris -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b91407e.3060...@spamcop.net
