Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

Hi! > > Thanks for the tips. Unfortunately running just the single test > > without any other load on the system still crashes it and system load > > was otherwise zero, so it is not due to slowness. > > Single-core performance on SPARC is rather poor, especially on older > SPARC systems like this

Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

Hi Otto, On Fri, 2024-07-05 at 23:00 -0700, Otto Kekäläinen wrote: > Thanks for the tips. Unfortunately running just the single test > without any other load on the system still crashes it and system load > was otherwise zero, so it is not due to slowness. Single-core performance on SPARC is rath

Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

Thanks for the tips. Unfortunately running just the single test without any other load on the system still crashes it and system load was otherwise zero, so it is not due to slowness. I also tested explicit debug run and various ways to invoke gdb, but --debug didn't yield any new info and all gdb

Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

./sql/ha_partition.cc:5657 is coping over a blob of memory. Could it just be slow? Does running main.partition on its own generate the same result? Alternately one of the loop constructs around it got some incorrect values. Examine local variables (info locals) around what was executing on timeo

Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

I built the binary in debug mode and that yielded a stacktrace: *** main.partition w38 [ retry-fail ] Test ended at 2024-07-06 01:14:43 CURRENT_TEST: main.partition mysqltest: At line 3010: query 'select id from t1 where data = 'a

Re: Bug#1074558: mariadb: FTBFS on sparc64: Multiple tests crash / time out

arc64 hackers interested in taking a look? > > > > The build itself passed and most of the post-build passes, but some > > tests cause the database to crash. Stack traces are visible in the > > logs: > > > > https://buildd.debian.org/status/fetch.php?pk

Re: mariadb: FTBFS on sparc64: Multiple tests crash / time out

d passes, but some > tests cause the database to crash. Stack traces are visible in the > logs: > > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A11.4.2-2&stamp=1719891893&raw=0 > https://buildd.debian.org/status/logs.php?pkg=mariadb&a

mariadb: FTBFS on sparc64: Multiple tests crash / time out

Hi! I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed on sparc64. Are there any sparc64 hackers interested in taking a look? The build itself passed and most of the post-build passes, but some tests cause the database to crash. Stack traces are visible in the logs: https

Re: ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

Le lun. 3 sept. 2018 à 20:34, Chris Ross a écrit : > :-( I'm sorry to hear about this. I'd been happy to think that if I backed > off of worrying about a mirrored /boot, and just used a RAID1 as you did, So far I don't even use RAID1 - ZFS is on a single disk, with /dev/sdd1 as the boot partiti

Re: ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

On Sun, Sep 02, 2018 at 10:54:31AM +0200, Romain Dolbeau wrote: > Any suggestion or idea welcome... > > BTW, did anyone else succeeded in having ZFS root on sparc64? :-( I'm sorry to hear about this. I'd been happy to think that if I backed off of worrying about a mirrored /boot, and just used

ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

2018-07-20 23:52 GMT+02:00 Romain Dolbeau : > I don't think I did anything special beyond > slightly fixing the grub.cfg by adding the pool name... Last week-end (25/26 august), I dist-upgraded my ZFS root install... unfortunately, I haven't been able to boot it since :-( I got an upgraded kernel

Re: Installed kernel crash on T5120

On Fri, Jul 20, 2018 at 11:52:19PM +0200, Romain Dolbeau wrote: > fdisk, force of habits... lol. Never would've guessed that was an option. Well, that looks more like yours: Device Start End Sectors Size Id Type Flags /dev/sda1 0979964979965 478.5M 1 Boot

Re: Installed kernel crash on T5120

2018-07-20 23:22 GMT+02:00 Chris Ross : > Interesting. What tool is showing that? fdisk, force of habits... > I have been using parted, which > shows (for my first ZFS disk): > > Number Start EndSize File system Flags > 1 0.00B 502MB 502MB ext2 boot > 2 502MB 147

Re: Installed kernel crash on T5120

On Fri, Jul 20, 2018 at 08:47:05AM +0200, Romain Dolbeau wrote: > t5120:~$ dpkg -l '*grub*' | grep ^ii > ii grub-common 2.02+dfsg1-4 sparc64 GRand Unified > Bootloader (common files) > ii grub-ieee1275 2.02+dfsg1-4 sparc64 GRand Unified > Bootloader, version 2 (Open Firmware v

Re: Installed kernel crash on T5120

2018-07-19 23:51 GMT+02:00 Chris Ross : > Can you confirm the version of grub that you've used to grub-install onto > your disk, t5120:~$ dpkg -l '*grub*' | grep ^ii ii grub-common 2.02+dfsg1-4 sparc64 GRand Unified Bootloader (common files) ii grub-ieee1275 2.02+dfsg1-4 sparc64

Re: Installed kernel crash on T5120

On Wed, Jul 18, 2018 at 07:34:31AM +0200, Romain Dolbeau wrote: > 2018-07-18 4:29 GMT+02:00 Chris Ross : > > Interesting to note, thank you. > > If you have a full build of zfs from source, you can try > "zfs/cmd/raidz_test/raidz_test -B". > > > I wonder why > > my grub-install onto my sda1 isn't

Re: Installed kernel crash on T5120

2018-07-18 16:57 GMT+02:00 John Paul Adrian Glaubitz : > Some essential packages like glibc will shortly disrupt the functionality > of debootstrap. It resumes working once the FTP servers are in sync > again. What was weird is that debootstrap kept trying for a -9, while I could see and download

Re: Installed kernel crash on T5120

On 07/18/2018 04:57 PM, John Paul Adrian Glaubitz wrote: >> So I guess the kernel still alive ... (no ping though, and >> non-responsive console). > > Did you enable the console on the command line? Try adding "console=ttyS0" > or whatever the name of the serial console on your SPARC machine is.

Re: Installed kernel crash on T5120

On 07/18/2018 04:50 PM, Romain Dolbeau wrote: > debootstrap would then fails, trying to download some packages > upgraded during the night... after a while and multiple attempts it > worked. Dunno why. Some essential packages like glibc will shortly disrupt the functionality of debootstrap. It res

Re: Installed kernel crash on T5120

2018-07-18 7:34 GMT+02:00 Romain Dolbeau : > That's where I am a right now. I'll try to rebuild Debian ZFS in the chroot > instead of the installed Debian next... Ended up doing 'mkdir' of the missing directory during build, solved the problem. Then the new ZFS, being older, didn't import the poo

Re: Installed kernel crash on T5120

2018-07-18 4:29 GMT+02:00 Chris Ross : > Interesting to note, thank you. If you have a full build of zfs from source, you can try "zfs/cmd/raidz_test/raidz_test -B". > I wonder why > my grub-install onto my sda1 isn't working, and yours onto your sdd1 is. Barely so far. After a couple of trials

Re: Installed kernel crash on T5120

On Tue, Jul 17, 2018 at 03:04:18PM +0200, Romain Dolbeau wrote: > Well I have ZFS up and running from Git - it has become surprisingly > easy over the years. > BTW, from the archive, I see you were intent on RAIDZ. I love RAIDZ, > but after running the raidz benchmark, I strongly advise against > a

Re: Installed kernel crash on T5120

2018-07-17 5:08 GMT+02:00 Chris Ross : > I hope that you are able to make progress and that > I can learn from it as well. :-) Well I have ZFS up and running from Git - it has become surprisingly easy over the years. BTW, from the archive, I see you were intent on RAIDZ. I love RAIDZ, but after r

Re: Installed kernel crash on T5120

On Mon, Jul 16, 2018 at 09:32:57PM +0200, Romain Dolbeau wrote: > Next step - ZFS followed by trying to deboostrap a new install in a ZFS root > :-) Thank you for your email, too. I have a T5120 that I was able to get ZFS on, with help from this list. But I am having GRUB problems myself, as no

Re: Installed kernel crash on T5120

2018-07-16 20:50 GMT+02:00 John Paul Adrian Glaubitz : > If you have 2.0.4-12 and not 2.0.4-12+sparc64, your klibc is broken. You > can either boot into rescue mode, then chroot into the installed system > and dist-upgrade the machine and then run update-initramfs -k all -u or > reinstall the machi

Re: Installed kernel crash on T5120

Hi Romain! On 07/16/2018 08:33 PM, Romain Dolbeau wrote: > Now grub loads fine, I see the grub menu, pick the default choice, and > this happen: > > # > Loading Linux 4.16.0-1-sparc64-smp ... > Segmentation fault > /dev/sdc2: clean, 38180/6938624 files, 827057/27744254 blocks > Segmentation f

Installed kernel crash on T5120

Hello all, Trying to install Sid sparc64 on a T5120. I have a cdrom with the 2018-05-18 ISO from . I'm installing on the third hard drive (first two are a mirrored ZFS pool for Solaris). It worked just fine installing to the whole dis

Re: Solaris crash?

Time to check hardware (memory modules) ? Google shows some references to Illumos source: http://fxr.watson.org/fxr/source/sun4u/cpu/spitfire.c?v=OPENSOLARIS * [AFT0] - Tag for log messages that are associated with corrected ECC errors. 360 * This includes both corrected ECC memor

Solaris crash?

I did let Solaris chew on the DVD and after some minutes it printed the copyrights, but after that it begun to endlessly omit this line on the console: [AFT0] Softerror: mem_ce_simm[] out of space.

SunFire V245 Crash

Hi, We have a Sun Fire V245 that craches at random times after an upgrade to a new kernel, it sends an error message: 35403.390136] ERROR(0): Cheetah error trap taken afsr[1202] afar[000144fbb100] TL1(0) [35403.390158] ERROR(1): Cheetah error trap taken afsr[00108000

Re: system crash / init: Id 2 respawning too fast: disabled for 5 minutes

On Fri, Apr 28, 2006 at 04:30:27PM +0200, Marcus Schopen wrote: > Hi, > > my little ultra 1 (sarge) crash tonight. Last message in syslog is: > > Apr 28 01:21:57 oola init: Id "2" respawning too fast: disabled for 5 minutes > [...more of same...] > > /etc/ini

Re: system crash / init: Id 2 respawning too fast: disabled for 5 minutes

On Fri, 28 Apr 2006, Marcus Schopen wrote: Hi, my little ultra 1 (sarge) crash tonight. Last message in syslog is: Apr 28 01:21:57 oola init: Id "2" respawning too fast: disabled for 5 minutes Apr 28 01:21:57 oola init: Id "1" respawning too fast: disabled for 5 minutes

system crash / init: Id 2 respawning too fast: disabled for 5 minutes

Hi, my little ultra 1 (sarge) crash tonight. Last message in syslog is: Apr 28 01:21:57 oola init: Id "2" respawning too fast: disabled for 5 minutes Apr 28 01:21:57 oola init: Id "1" respawning too fast: disabled for 5 minutes Apr 28 01:21:57 oola init: Id "5" res

Re: random crash

> "Clint" == Clint Adams <[EMAIL PROTECTED]> writes: Clint> Do you think you could get the exact oops message the next Clint> time this happens? Hello, I think so because i will be at home the next weeks. I will send you the oops ASAP. I will check the hardware using openboot this we

RE: Setting time time causes system crash

T105 -Original Message- From: Clint Adams [mailto:[EMAIL PROTECTED] Sent: Thursday, December 15, 2005 10:25 AM To: Steve Discher Cc: debian-sparc@lists.debian.org Subject: Re: Setting time time causes system crash > I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Ne

RE: Setting time time causes system crash

Work Around: I set the time using ntpd (ntpd -g 1) in 1 second steps and it updated progressively to the correct time without a crash. I suspect that when I tried to update it in one step of more than 42000 seconds that caused the crash. FYI: Offsets greater than 1000 seconds cause ntpd

Re: Setting time time causes system crash

On Thursday 15 December 2005 16:48, Steve Discher wrote: > I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra > T1. If I set the system time using a time server via ntp or directly > from the command line it causes the system to lock up. There are not > entries in the system l

Re: Setting time time causes system crash

> I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra T1. Is this a t105 and not a T1 AC200? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: random crash

> It happened with 2.6.8 and 2.4.27... I have an oops but i don't know > exactly because i haven't physical access to the box (my mother told me > the message which was on the screen). Do you think you could get the exact oops message the next time this happens? -- To UNSUBSCRIBE, email to [EMA

Setting time time causes system crash

I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra T1. If I set the system time using a time server via ntp or directly from the command line it causes the system to lock up. There are not entries in the system log to evidence the cause. Any ideas? hwclock --hctosys and h

Re: random crash

o to check hardware (i think that this kind of crash comes from memory, it isn't ?), so how to use openboot to check the hardware and to be sure ? Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: random crash

> "Clint" == Clint Adams <[EMAIL PROTECTED]> writes: Clint> What is this odd error message? Did it happen with 2.4.27 or Clint> 2.6.8? It happened with 2.6.8 and 2.4.27... I have an oops but i don't know exactly because i haven't physical access to the box (my mother told me the mess

Re: random crash

> and installed Linux kernel 2.4.27 with SMP support. However, one week > after the startup of the server, the box crashs with a odd error message > and i must reboot it. I tested it with Linux kernel 2.6.8. What is this odd error message? Did it happen with 2.4.27 or 2.6.8? -- To UNSUBSCRIBE,

Re: random crash

use the reboot the Emmanuel> machine and go into OpenBoot from remote. Hello, Ok, then i will use a serial console ASAP. However, what could i do to check hardware (i think that this kind of crash comes from memory, it isn't ?), so how to use openboot to check the hardware and to

random crash

must reboot it. I tested it with Linux kernel 2.6.8. I would like to know how i could identify what is causing a crash randomly. What should i do ? Should i use OpenBoot (and how ?) or is there linux specific tools to do that (i have only physical access to the box the weekend) ? Regards

kernel oops / crash [was Re: Auto reboot after a poweroutage]

I was attempting to reply to this, to mention that this could likely be changed from within Linux, with openpromfs. However, when I tried to change /proc/openprom/options/auto-boot?, I received the following oops' (this happened twice): -- Handy Cut Line --

Re: Xserver crash Enterprise 250 Raptor Video

s out. --- Bob Meader <[EMAIL PROTECTED]> wrote: > I have an odd xserver crash problem on a E250 with > Raptor/GFX display. If Xwindows runs under control > with xdm,gdm or kdm the xserver will crash hard > after running an application. The KDE session > does completely sta

Xserver crash Enterprise 250 Raptor Video

I have an odd xserver crash problem on a E250 with Raptor/GFX display. If Xwindows runs under control with xdm,gdm or kdm the xserver will crash hard after running an application. The KDE session does completely startup so have "start" panel. I will lockup after variety of mouse/keybo

Re: crash on cd boot

Title: Re: crash on cd boot I have the exact same problem.  Any information would be greatly appreciated! Thanks, Casey Johle

crash on cd boot

using the net install sparc debian cds i'm getting this error when trying to run either linux or rescue Loading initial ramdisk... Illegal Instruction and then drops me back into the ok prompt. any ideas? __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use

Re: SparcStation4 reconstructable crash

d in the > logs, didn't find anything. I put it up again and 2 days later (5th crash) > I said to myself "this computer has faulty hardware" and I replaced it > with another SparcStation4 with identical hardwaresetup. > > With my wrong intuition that Woody is bad I ins

SparcStation4 reconstructable crash

ed to bother me. 3 crashes in two weeks. New to Debian I figured that Woody is bad so I installed Potato. It ran fine for a whole week then same error. I looked in the logs, didn't find anything. I put it up again and 2 days later (5th crash) I said to myself "this computer has faulty

Re: XFree86 4.1.0-5 crash problem

Hi, Originally I upgraded the xserver-xfree86 package from 4.0.3-5 into 4.1.0-5 just as normal upgrade after update. Then I realized that the new package wasn't working for me on Ultra 10 with Creator 3D card, woody distribution. So I had to compile down the xfree86 sources 4.0.3-4 version. Gab

Re: XFree86 4.1.0-5 crash problem

On Fri, Sep 21, 2001 at 11:07:01AM +0200, Gabor Zoltan Csejtey wrote: > I finally managed to find the sources for xfree86_4.0.3.orig.tar.gz > version xfree86_4.0.3-4.1.diff.gz. I compiled them and installed the > xserver-xfree86 package: > hi xserver-xfree8 4.0.3-4.1 the XFree86 X server >

Re: XFree86 4.1.0-5 crash problem

Hi, I finally managed to find the sources for xfree86_4.0.3.orig.tar.gz version xfree86_4.0.3-4.1.diff.gz. I compiled them and installed the xserver-xfree86 package: hi xserver-xfree8 4.0.3-4.1 the XFree86 X server Is there a known issue between xserver-xfree86_4.0.3-4.1 and xserver-xfr

Re: XFree86 4.1.0-5 crash problem

Hi, Here they are. I tried different versions of XF86Configs. I forgot to mention that using XFree86 -configure found the ATI 3D Rage Mach64 GT video too which may work and I haven't tried yet. But removing the reference to the driver ati from the config file I got the same message. Gabor

Re: XFree86 4.1.0-5 crash problem

On Tue, Sep 18, 2001 at 12:00:45PM +0200, [EMAIL PROTECTED] wrote: > (EE) Screen(s) found, but none have a usable configuration. > > Fatal server error: > > I'm using the same XF86Config-4 which was working before. > I searched for the old packages of xserver-xfree86 but I couldn't > find them o

XFree86 4.1.0-5 crash problem

Hi, I upgraded to testing from poatato some months ago. I upgraded xserver-xfree86 4.1.0-5 from the previous version 4.0.3 as I recall the numbers. X was working with 4.0.3 release but withe new release when I start startx or xdm or Xfree86 I get the message at the and of XFree86.0.log I have a

Re: Crash

On Tue, 8 May 2001, Anton Blanchard wrote: > > data_access_exception: Shit SFSR[00801009] SFAR[fe320048], > > going. > > You need to pass this through ksymoops to be useful. What kernel > version are you using? 2.2.18pre?? Can't check at this moment because of installing a smal

Re: Crash

Hi, On Mon, 7 May 2001, Andreas Tille wrote: > data_access_exception: Shit SFSR[00801009] SFAR[fe320048], > going. > \|/ \|/ > "@'/ .. \`@" > /_| \__/ |_\ > \__U_/ > swapper(0): Dax I think this means the task sched

Re: Crash

> data_access_exception: Shit SFSR[00801009] SFAR[fe320048], > going. You need to pass this through ksymoops to be useful. What kernel version are you using? Anton

Crash

Hello, I did further investigation in the E250 server crash problem. I tried to report here sometimes but got now real help on the topic - so I tried again. Short summary: I observe randomly crashes of the E250 box. After a crash serial console seems to be dead. Sun support only tasks

Re: Machine Crash

Hello, On Tue, 20 Feb 2001 08:27:02 Clean wrote: > My SUN UltraII enterprise 250 Server crash witout any message and no signal. > It's like the kernel enter an infinite loop, by I don't know what's the > problem because it crash randomly. Which linux Kernel is on your

Machine Crash

My SUN UltraII enterprise 250 Server crash witout any message and no signal. It's like the kernel enter an infinite loop, by I don't know what's the problem because it crash randomly. Have you any idea? Best Regard's Fran Couñago TLR Soft. S.L. 902 12 10 74 E-mail: [EMAIL PROTECTED]