Steve Vai froze my machine ... but most probably an amdgpu issue
On Wed, Feb 24, 2021 at 06:23:07AM +0900, rgc wrote: > On Fri, Feb 19, 2021 at 06:26:40AM +0900, rgc wrote: > > On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote: > > shimer/flicker happened again once on 338. > zzz and wake-up again seems to restore things back to normal. > > updated to the following in the last few days > and haven't encountered shimer/flicker or the original issue (X crash) > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #344: Fri Feb 19 10:01:51 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #350: Sun Feb 21 11:04:59 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP just sharing some information for those tracking down amdgpu issues no issues until today machine has been suspened several times thru the course of the week (last update was 03/31 with #436, shown below) watching Steve Vai on youtube (firefox-esr) and screen froze i could ssh to the machine. top showed machine was mostly idle. OpenBSD 6.9-beta (GENERIC.MP) #436: Mon Mar 29 12:55:53 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 25417670656 (24240MB) avail mem = 24631955456 (23490MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xbd60a000 (24 entries) bios0: vendor American Megatrends Inc. version "GU502DU.305" date 01/07/2021 bios0: ASUSTeK COMPUTER INC. Zephyrus G GU502DU_GA502DU acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT ECDT SSDT MCFG MSDM SSDT HPET UEFI VFCT TPM2 IVRS SSDT CRAT CDIT BGRT SSDT SSDT SSDT SSDT SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) GP18(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >8< snipped >8< last log below, before i finally rebooted the system [drm] *ERROR* Error in DP aux read transaction, not writing source specific data [drm] *ERROR* ring sdma0 timeout, signaled seq=26973, emitted seq=26973 [drm] *ERROR* Process information: process pid 0 thread pid 0 fetching new snapshots now. and will continue to watch Steve Vai (it's a Friday night in Japan) rgc ~
macppc beta-69 #856 xenodm crash
below is dmesg.boot and xenodm.log [ using 1321588 bytes of bsd ELF symbol table ] console out [ATY,Jasper_A] console in [keyboard], using USB using parent ATY,JasperParent:: memaddr b800, size 800 : consaddr b8008000 : ioaddr b002, size 2: width 1440 linebytes 1536 height 960 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.9-beta (GENERIC) #856: Sat Mar 13 01:57:17 MST 2021 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1023451136 (976MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root: model PowerBook5,8 cpu0 at mainbus0: 7447A (Revision 0x105): 1666 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 512MB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM spdmem1 at mem0: 512MB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM memc0 at mainbus0: uni-n rev 0xd9 "hw-clock" at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 adt0 at iic0 addr 0x2e: adt7467 rev 0x71 lmtemp0 at iic0 addr 0x49: ds1775 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 "Apple Intrepid 2 AGP" rev 0x00 agp at pchb0 not configured radeondrm0 at pci0 dev 16 function 0 "ATI Radeon Mobility M10" rev 0x00 drm0 at radeondrm0 radeondrm0: irq 48 mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 macobio0 at pci1 dev 23 function 0 "Apple Intrepid" rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 "modem-reset" at macgpio0 offset 0x1d not configured "accelerometer-1" at macgpio0 offset 0x13 not configured "accelerometer-2" at macgpio0 offset 0x14 not configured "amp-mute" at macgpio0 offset 0x20 not configured "dig-hw-reset" at macgpio0 offset 0x26 not configured "codec-error-irq" at macgpio0 offset 0x18 not configured "combo-in-sense" at macgpio0 offset 0xb not configured "combo-out-sense" at macgpio0 offset 0x12 not configured "codec-input-data-mux" at macgpio0 offset 0x23 not configured "codec-clock-mux" at macgpio0 offset 0x29 not configured "hw-reset" at macgpio0 offset 0x1a not configured "linein-detect" at macgpio0 offset 0xc not configured "lineout-detect" at macgpio0 offset 0x17 not configured "lineout-mute" at macgpio0 offset 0x1f not configured dfs0 at macgpio0 offset 0x1b: speeds: 1666, 833 MHz macgpio1 at macgpio0 offset 0x9: irq 47 "programmer-switch" at macgpio0 offset 0x11 not configured "escc-legacy" at macobio0 offset 0x12000 not configured zs0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zs0 channel 0 zstty1 at zs0 channel 1 onyx0 at macobio0 offset 0x0: irq 30,1,2 "timer" at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 apm0 at adb0: battery flags 0x7, 85% charged piic0 at adb0 iic1 at piic0 "backlight" at macobio0 offset 0xf300 not configured kiic1 at macobio0 offset 0x18000 iic2 at kiic1 "pcm3052" at iic2 addr 0x46 not configured "cs8416" at iic2 addr 0x10 not configured audio0 at onyx0 bwi0 at pci1 dev 17 function 0 "Broadcom BCM4318" rev 0x02: irq 52, address 00:14:51:7e:3b:4c cbb0 at pci1 dev 20 function 0 "TI PCI1510 CardBus" rev 0x00: irq 53 ohci0 at pci1 dev 21 function 0 "NEC USB" rev 0x43: irq 54, version 1.0 ohci1 at pci1 dev 21 function 1 "NEC USB" rev 0x43: irq 54, version 1.0 ehci0 at pci1 dev 21 function 2 "NEC USB" rev 0x04: irq 54 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 configuration 1 interface 0 "NEC OHCI root hub" rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 configuration 1 interface 0 "NEC OHCI root hub" rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north pci2 at mpcpcibr2 bus 0 kauaiata0 at pci2 dev 13 function 0 "Apple Intrepid 2 ATA" rev 0x00 wdc0 at kauaiata0 irq 39: DMA wd0 at wdc0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 244198MB, 500118192 sectors wd0(wdc0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 "Apple Intrepid 2 FireWire" rev 0x00 at pci2 dev 14 function 0 not configured gem0 at pci2 dev 15 function 0 "Apple Intrepid 2 GMAC" rev 0x00: irq 41, address 00:14:51:1d:d1:5e brgphy0 at gem0 phy 0: BCM5462 10/100/1000baseT PHY, rev. 3 wdc1 at pcmcia0 function 0 "SanDisk, SDCFXS-032G, " port 0x0/16 wd1 at wdc1 channel 0 drive 0: wd1: 1-sector PIO, LBA48, 30535MB, 62537328 sectors wd1(wdc1:0:0): using BIOS timings uhidev0 at uhub1 port 2 configuration 1 interface 0 "Apple Computer HID-proxy" rev 2.00/19.65 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0 mux 1 uhidev1 at uhub1 port 2 configuration 1 interface 1 "Apple Computer
Re: amdgpu unstable atm
On Fri, Feb 19, 2021 at 06:26:40AM +0900, rgc wrote: > On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote: > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST > > 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST > > 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > #323 was used over the weekend (2 days) no issues > > > > #328 is running now. playing with vowpal_wabbit (a one-off compile) > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #334: Sun Feb 14 11:49:39 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #338: Tue Feb 16 10:01:46 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > ran 334 until yesterday, did a 500Gb dd of the other drive. no hiccups. > > now running 338. installed 2 nights ago. running a vmm, spyder3, firefox-esr > no > issues. until the morning. i had it powered on overnight, xautolock-ed. > when the machine woke up display was "shimering/flickering". rather than > 'reboot', i did a 'zzz' and woke it up again. shimer/flicker was gone. > first time i got this shimer/flicker on any laptop that i use. > > today i didnt hibernate or suspend but this shimer/flicker has not occured > again > after unlocking xautolock. shimer/flicker happened again once on 338. zzz and wake-up again seems to restore things back to normal. updated to the following in the last few days and haven't encountered shimer/flicker or the original issue (X crash) kern.version=OpenBSD 6.9-beta (GENERIC.MP) #344: Fri Feb 19 10:01:51 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP kern.version=OpenBSD 6.9-beta (GENERIC.MP) #350: Sun Feb 21 11:04:59 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP ~ rgc
Re: amdgpu unstable atm
On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote: > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > #323 was used over the weekend (2 days) no issues > > #328 is running now. playing with vowpal_wabbit (a one-off compile) kern.version=OpenBSD 6.9-beta (GENERIC.MP) #334: Sun Feb 14 11:49:39 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP kern.version=OpenBSD 6.9-beta (GENERIC.MP) #338: Tue Feb 16 10:01:46 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP ran 334 until yesterday, did a 500Gb dd of the other drive. no hiccups. now running 338. installed 2 nights ago. running a vmm, spyder3, firefox-esr no issues. until the morning. i had it powered on overnight, xautolock-ed. when the machine woke up display was "shimering/flickering". rather than 'reboot', i did a 'zzz' and woke it up again. shimer/flicker was gone. first time i got this shimer/flicker on any laptop that i use. today i didnt hibernate or suspend but this shimer/flicker has not occured again after unlocking xautolock. ~ rgc
Re: amdgpu unstable atm
On Wed, Feb 10, 2021 at 06:46:55PM +0900, rgc wrote: > > sysupgraded this morning > logged in xenodm, running stterm, tmux, spyder3, firefox-esr > left it as-is ... went to work. > checked it later in the day, saw the console login prompt, pressing a key > shutdown the system. hmmn. this is probably a user error because i had the same thing happen today thinking i had the machine suspended (via zzz) i pressed the power button and the machine powered off. but i can't remember if i pressed the power button on that day. kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP #323 was used over the weekend (2 days) no issues #328 is running now. playing with vowpal_wabbit (a one-off compile) ~ rgc
Re: amdgpu unstable atm
On Mon, Feb 01, 2021 at 08:05:45PM +0900, rgc wrote: > misc@ > > it's been a few days > some crashes still occured .. > one time i've already killed firefox-esr and was just using stterm when X > crashed. > > in the meantime, i've done a BIOS update. > i have SVM (AMDs vmm support) enabled which automatically shares 1Gb to iGPU. > and running pkg_add -u and sysupgrade every other day. > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #302: Sat Jan 30 21:51:53 MST > 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > running spyder3 and firefox-esr at the same time, no issues so far misc@ now running 6.9-beta kern.version=OpenBSD 6.9-beta (GENERIC.MP) #321: Mon Feb 8 14:21:26 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP sysupgraded this morning logged in xenodm, running stterm, tmux, spyder3, firefox-esr left it as-is ... went to work. checked it later in the day, saw the console login prompt, pressing a key shutdown the system. hmmn. i was downstairs (WFH nowadays) so i would have known if there was a power failure. as i type this i am sysupgrading ~ rgc
Re: amdgpu unstable atm
On Mon, Jan 25, 2021 at 05:33:22PM +0900, rgc wrote: > misc@ > > pkg_add -u; sysupgrade -ks this morning > i see firefox-esr pull a new gtk (iirc) build ... quirks-3.517 > on firefox is visualsource.net playing commit videos > seems to be working good now ... and it seems firefox is more snappier > > i still see these on xconsole > > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > > data > > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > > data > but no hangs or crashes at the moment. > > ~ rgc > misc@ it's been a few days some crashes still occured .. one time i've already killed firefox-esr and was just using stterm when X crashed. in the meantime, i've done a BIOS update. i have SVM (AMDs vmm support) enabled which automatically shares 1Gb to iGPU. and running pkg_add -u and sysupgrade every other day. kern.version=OpenBSD 6.8-current (GENERIC.MP) #302: Sat Jan 30 21:51:53 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP running spyder3 and firefox-esr at the same time, no issues so far ~ rgc
Re: amdgpu unstable atm
On Sun, Jan 24, 2021 at 07:19:36AM +0900, rgc wrote: > On Sat, Jan 23, 2021 at 08:49:13PM +0900, rgc wrote: > > On Fri, Jan 22, 2021 at 08:33:37PM +0900, rgc wrote: > > > misc@ > > > > > > sharing some information for the devs > > > > > > just did a sysupgrade of a -current amd64 machine > > > X (only, sent me back to login screen of xenodm) crashed 2x already > > > running only dwm and firefox-esr > > > > > > machine is: > > > hw.vendor=ASUSTeK COMPUTER INC. > > > hw.product=Zephyrus G GU502DU_GA502DU > > > > > > iGPU is: > > > amdgpu0: PICASSO 10 CU rev 0x01 > > > > > > dmesg error: > > > [drm] *ERROR* ring sdma0 timeout, signaled seq=402, emitted seq=402 > > > [drm] *ERROR* Process information: process pid 0 thread Xorg pid 50457 > > > [drm] *ERROR* ring gfx timeout, but soft recovered > > > [drm] *ERROR* Error in DP aux read transaction, not writing source > > > specific data > > > [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197 > > > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > > [drm] *ERROR* Error in DP aux read transaction, not writing source > > > specific data > > > > > > others: > > > amdgpu-firmware-20201218 firmware binary images for amdgpu(4) driver > > > > > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #286: Thu Jan 21 09:31:59 > > > MST 2021 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > > > ~ rgc > > > > > > > no crashes yet with: > > > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #288: Fri Jan 22 13:36:58 MST > > 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > ~ rgc > > > > misc@ > > kept the machine running overnight > stterm and firefox-esr (static websites) running. looked good. > > this morning i went to github to cleanup some personal projects > after a few minutes, firefox-esr stopped responding. > can not switch to stterm on another pane (ALT-1) > > network connectivity was still OK. > last messages on dmesg: > > wsdisplay0: screen 1-5 added (std, vt100 emulation) > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data > > remotely, i tried killing process one by one. firefox-esr, xenodm, lastly X > itself. > got a blank screen on the Asus, but i could get the console. started xenodm > and > now working again. > > ~ rgc > misc@ pkg_add -u; sysupgrade -ks this morning i see firefox-esr pull a new gtk (iirc) build ... quirks-3.517 on firefox is visualsource.net playing commit videos seems to be working good now ... and it seems firefox is more snappier i still see these on xconsole > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data but no hangs or crashes at the moment. ~ rgc
Re: amdgpu unstable atm
On Sat, Jan 23, 2021 at 08:49:13PM +0900, rgc wrote: > On Fri, Jan 22, 2021 at 08:33:37PM +0900, rgc wrote: > > misc@ > > > > sharing some information for the devs > > > > just did a sysupgrade of a -current amd64 machine > > X (only, sent me back to login screen of xenodm) crashed 2x already > > running only dwm and firefox-esr > > > > machine is: > > hw.vendor=ASUSTeK COMPUTER INC. > > hw.product=Zephyrus G GU502DU_GA502DU > > > > iGPU is: > > amdgpu0: PICASSO 10 CU rev 0x01 > > > > dmesg error: > > [drm] *ERROR* ring sdma0 timeout, signaled seq=402, emitted seq=402 > > [drm] *ERROR* Process information: process pid 0 thread Xorg pid 50457 > > [drm] *ERROR* ring gfx timeout, but soft recovered > > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > > data > > [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197 > > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > > data > > > > others: > > amdgpu-firmware-20201218 firmware binary images for amdgpu(4) driver > > > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #286: Thu Jan 21 09:31:59 MST > > 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > ~ rgc > > > > no crashes yet with: > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #288: Fri Jan 22 13:36:58 MST > 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > ~ rgc > misc@ kept the machine running overnight stterm and firefox-esr (static websites) running. looked good. this morning i went to github to cleanup some personal projects after a few minutes, firefox-esr stopped responding. can not switch to stterm on another pane (ALT-1) network connectivity was still OK. last messages on dmesg: wsdisplay0: screen 1-5 added (std, vt100 emulation) [drm] *ERROR* Error in DP aux read transaction, not writing source specific data [drm] *ERROR* Error in DP aux read transaction, not writing source specific data remotely, i tried killing process one by one. firefox-esr, xenodm, lastly X itself. got a blank screen on the Asus, but i could get the console. started xenodm and now working again. ~ rgc
Re: amdgpu unstable atm
On Fri, Jan 22, 2021 at 08:33:37PM +0900, rgc wrote: > misc@ > > sharing some information for the devs > > just did a sysupgrade of a -current amd64 machine > X (only, sent me back to login screen of xenodm) crashed 2x already > running only dwm and firefox-esr > > machine is: > hw.vendor=ASUSTeK COMPUTER INC. > hw.product=Zephyrus G GU502DU_GA502DU > > iGPU is: > amdgpu0: PICASSO 10 CU rev 0x01 > > dmesg error: > [drm] *ERROR* ring sdma0 timeout, signaled seq=402, emitted seq=402 > [drm] *ERROR* Process information: process pid 0 thread Xorg pid 50457 > [drm] *ERROR* ring gfx timeout, but soft recovered > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data > [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > [drm] *ERROR* Error in DP aux read transaction, not writing source specific > data > > others: > amdgpu-firmware-20201218 firmware binary images for amdgpu(4) driver > > kern.version=OpenBSD 6.8-current (GENERIC.MP) #286: Thu Jan 21 09:31:59 MST > 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > ~ rgc > no crashes yet with: kern.version=OpenBSD 6.8-current (GENERIC.MP) #288: Fri Jan 22 13:36:58 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP ~ rgc
amdgpu unstable atm
misc@ sharing some information for the devs just did a sysupgrade of a -current amd64 machine X (only, sent me back to login screen of xenodm) crashed 2x already running only dwm and firefox-esr machine is: hw.vendor=ASUSTeK COMPUTER INC. hw.product=Zephyrus G GU502DU_GA502DU iGPU is: amdgpu0: PICASSO 10 CU rev 0x01 dmesg error: [drm] *ERROR* ring sdma0 timeout, signaled seq=402, emitted seq=402 [drm] *ERROR* Process information: process pid 0 thread Xorg pid 50457 [drm] *ERROR* ring gfx timeout, but soft recovered [drm] *ERROR* Error in DP aux read transaction, not writing source specific data [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197 [drm] *ERROR* Process information: process pid 0 thread pid 0 [drm] *ERROR* Error in DP aux read transaction, not writing source specific data others: amdgpu-firmware-20201218 firmware binary images for amdgpu(4) driver kern.version=OpenBSD 6.8-current (GENERIC.MP) #286: Thu Jan 21 09:31:59 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP ~ rgc
kbd mapping issue
misc@ i use jp.swapctrlcaps as my keyboard mapping in amd64 and macppc OpenBSD 6.8 -snapshot via /etc/kbdtype. i use amd64 (GENERIC.MP #266) more often so i observed this weirdness in amd64. after several days, the kbd mapping goes weird for the swapped keys. normal jp.swapctrlcaps caps -> ctrl ctrl -> caps (changes LED status too) when issue occurs caps -> does nothing ctrl -> ctrl when the issue occurs i try changing kbd keymaps (jp, or en) but there is no change in behavior. reboot fixes things. amd64 is normal use laptop ... dwm, tmux, ssh, firefox-esr. i noticed this too on a previous snapshot (before #266). today i just upgraded my -snapshot to #232. the issue has not occured on macppc (now #827) ... i just use this Powerbook for dwm, tmux, ssh, fetchmail, mutt, cvs repo sync. rgc ~
Re: misc panics
On Mon, Dec 28, 2020 at 10:39:56AM +0100, Otto Moerbeek wrote: > On Mon, Dec 28, 2020 at 10:25:08AM +0100, Bastien Durel wrote: > > > Le lundi 28 d?cembre 2020 ? 09:17 +, Stuart Henderson a ?crit?: > > > > So hardware failure confirmed :/ Do you think I can change the RAM > > > > or > > > > it's more likely a CPU/Chipset failure ? > > > > > > > > Thanks, > > > > > > > > > > If you have multiple sticks of RAM, try removing some. > > I have only one > > trying to reaset it is worth a try. > > -Otto > or doing the eraser magick you clean the contacts (remove oxidation) of the RAM module (the side that sticks in the motherboard) by rubbing a pencil eraser on the contacts of the RAM module. - rgc
OpenBSD on ASRock 4x4 or Seed Studio Odyssey
hello misc@ anybody running OpenBSD on the ASRock 4x4 (Ryzen) or Seed Studio Odyssey (Intel Celeron J4105)? what are your experiences? https://www.asrockind.com/en-gb/4X4%20BOX-R1000V https://www.seeedstudio.com/Odyssey-Blue-Mini-PC-TELEC-p-4738.html headless? ASRock has an RS232 header but i'll probably need to wire up a DB9 and drill a hole on the case. the Odyssey probably can't do headless (?). UARTs are connected to the RPI-header and Arduino-header. weird setup. can we access the RPI header from OpenBSD's GPIO subsystem? rgc
Re: octave 5.2 weirdness
some details: kern.version=OpenBSD 6.8-current (GENERIC) #793: Thu Oct 15 21:30:08 MDT 2020 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC quirks-3.413 signed on 2020-09-09T17:52:01Z i am ssh-ed to the macppc machine from a Linux machine. suspending is weird, and catching CTRL-C drops to shell octave:1> ^Z^Z[3] + Suspendedoctave rgc:/home/rgc/:162$ fg octave [3] + Suspendedoctave rgc:/home/rgc/.octave:163$ fg octave octave:1> terminating with uncaught exception of type octave::interrupt_exception fatal: caught signal Abort trap -- stopping myself... Abort trap (core dumped) rgc:/home/rgc/:164$ on i386: kern.version=OpenBSD 6.8-current (GENERIC.MP) #456: Fri Oct 16 12:53:14 MDT 2020 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP - the tar issue occurs. - dropping to shell when giving incorrect commands does not occur - suspend seems ok - CTRL-C drops to shell octave:1> pkg install -forge io warning: creating installation directory /home/rgc/octave warning: called from install at line 30 column 5 pkg at line 441 column 9 unpack: unarchiving program exited with status: 1 tar: input compressed with gzip; use the -z option to decompress it error: called from unpack at line 274 column 5 untar at line 48 column 5 install at line 87 column 9 pkg at line 441 column 9 octave:1> pc error: 'pc' undefined near line 1 column 1 octave:1> ^Z[1] + Suspended octave rgc:/home/rgc:2$ fg octave terminating with uncaught exception of type octave::interrupt_exception fatal: caught signal Abort trap -- stopping myself... Abort trap (core dumped) regards, On Sat, Oct 17, 2020 at 10:27:18PM +0900, rgc wrote: > steven@ misc@ > > just a heads up for octave > > recently installed it for learning > > > 1 giving a wrong command drops me to the shell > > octave:1> pc > error: 'pc' undefined near line 1 column 1 > rgc:/home/rgc:107$ > > or > > octave:1> pkg > /tmp/octave-help-hUhbm7:119: Unknown command `codequoteundirected'. > warning: print_usage: Texinfo formatting filter exited abnormally > warning: called from > print_usage at line 74 column 5 > pkg at line 323 column 5 > warning: print_usage: raw Texinfo source of help text follows... > error: Invalid call to pkg. Correct usage is: > > on > > -- pkg COMMAND PKG_NAME > -- pkg COMMAND OPTION PKG_NAME > -- [OUT1, ...] = pkg (COMMAND, ... ) > > Additional help for built-in functions and operators is > available in the online version of the manual. Use the command > 'doc ' to search the manual index. > > Help and information about Octave is also available on the WWW > at https://www.octave.org and via the h...@octave.org > mailing list. > > > 2 is probably an issue with tar usage ... OpenBSD tar explicitly needs 'z' > to extract gzed tarballs > > octave:1> pkg install -forge communications > warning: creating installation directory /home/rgc/octave > warning: called from > install at line 30 column 5 > pkg at line 441 column 9 > unpack: unarchiving program exited with status: 1 > tar: input compressed with gzip; use the -z option to decompress it > error: called from > unpack at line 274 column 5 > untar at line 48 column 5 > install at line 87 column 9 > pkg at line 441 column 9 > octave:1> > > > both issues don't occur on octave in Linux (Ubuntu 20.04). > > regards, >
octave 5.2 weirdness
steven@ misc@ just a heads up for octave recently installed it for learning 1 giving a wrong command drops me to the shell octave:1> pc error: 'pc' undefined near line 1 column 1 rgc:/home/rgc:107$ or octave:1> pkg /tmp/octave-help-hUhbm7:119: Unknown command `codequoteundirected'. warning: print_usage: Texinfo formatting filter exited abnormally warning: called from print_usage at line 74 column 5 pkg at line 323 column 5 warning: print_usage: raw Texinfo source of help text follows... error: Invalid call to pkg. Correct usage is: on -- pkg COMMAND PKG_NAME -- pkg COMMAND OPTION PKG_NAME -- [OUT1, ...] = pkg (COMMAND, ... ) Additional help for built-in functions and operators is available in the online version of the manual. Use the command 'doc ' to search the manual index. Help and information about Octave is also available on the WWW at https://www.octave.org and via the h...@octave.org mailing list. 2 is probably an issue with tar usage ... OpenBSD tar explicitly needs 'z' to extract gzed tarballs octave:1> pkg install -forge communications warning: creating installation directory /home/rgc/octave warning: called from install at line 30 column 5 pkg at line 441 column 9 unpack: unarchiving program exited with status: 1 tar: input compressed with gzip; use the -z option to decompress it error: called from unpack at line 274 column 5 untar at line 48 column 5 install at line 87 column 9 pkg at line 441 column 9 octave:1> both issues don't occur on octave in Linux (Ubuntu 20.04). regards,
Re: reposync to JP mirror silently fails
Suzuki-sama otsukaresamadesu (sorry i could type kana, my macppc is not setup good enough) First of all, I am very thankful that I (we) could use your server for CVS reposysnc. It is great service to the community. Personally, I was not inconvenienced so please don't apologize. Thank you very much for the quick reply. I can verify that reposync is running fine again. yorosikuonegaiitashimasu On Fri, Oct 16, 2020 at 09:57:54AM +0900, SUZUKI Hitoshi wrote: > RGC, > thank you for letting me know the situation. > And sorry for the inconvinience. > > The service was not usabele after Sept. 14th > because I could not catch the update of reposync package, > > Now I've added the info. to /var/db/reposync/known_hosts, > so everything back is back to normal. > > > On 20/10/16 05:44, rgc wrote: > > misc@ > > > > just a heads up > > > > > > i usually reposync to 'rsync://anoncvs.au.openbsd.org/cvs/' but the past > > few months > > i noticed reposync is not pulling any changes from this mirror. > > > > maybe it is not syncing correctly to the main server. > > > > i temporarily moved to a different mirror. > > > > -- > SUZUKI Hitoshi s...@nagasaki-u.ac.jp > Faculty of Economics, Nagasaki Univ.
reposync to JP mirror silently fails
misc@ just a heads up i usually reposync to 'rsync://anoncvs.au.openbsd.org/cvs/' but the past few months i noticed reposync is not pulling any changes from this mirror. maybe it is not syncing correctly to the main server. i temporarily moved to a different mirror.
Re: sysupgrade with sysmerge failure
On Mon, Jun 01, 2020 at 10:47:02PM -0700, Sean Kamath wrote: > I didn???t see any place in sysmerge that used mail, and did not receive any > mail for the failed sysmerge. > But I see in /etc/rc that it does mail the output of sysmerge to the root > user. Guess I got other issues. did you already check /etc/mail/aliases and verified contents of /root/.forward? > > Thanks, > Sean > > >
Re: macbook only sees 1GB of a 2GB RAM module
On Sat, May 30, 2020 at 07:23:58PM +0200, Jan Stary wrote: > This is current/amd64 on a macbook2,1 (dmesg below). > It has two RAM slots, each holding a 2GB module: if you like using older Apple HW then https://everymac.com/ is a very good resource. searching Macbook2,1 reveals the HW issue. this specific limitation https://everymac.com/systems/apple/macbook_pro/faq/macbook-pro-core-2-duo-3-gb-memory-limitation-details.html > > spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL6 SO-DIMM > spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM non-parity PC2-6400CL6 SO-DIMM > > But of one of the 2GB, only 1GB is seen: > > real mem = 3171909632 (3024MB) > > I have tried swapping the mdules, it only happens > in one of the two slots. If I put a 1GB module in there, > the available memory is the same (in the other slot, > 2GB is 2GB and 1GB is 1GB). > > Why is this? Does it have anthing to do with > the memory map conflicts I see in the dmesg? > ~rgc
Re: clang analyzer
On Mon, May 25, 2020 at 02:34:53AM +0300, Gregory Edigarov wrote: > Hello, > > clang --analyze main.c > error: action RunAnalysis not compiled in > > I find it strange.?? Is there any particular reason for not including it? > > Is there any procedure I can use to get a "full" clang? $ which clang Also, have you tried the ports version? $ pkg_info -q llvm > > Thank you. > > -- > > With best regards, > > ?? Gregory Edigarov > >
Re: macppc wsconsctl screen brightness
On Wed, May 06, 2020 at 06:51:21PM +0900, rgc wrote: > macppc.html shows i can do this via "wsconsctl -w XXX". > ** note that wsconsctl doesn't have a "-w" option so macppc.html might need > to be updated ** sent a patch to remove the "-w" in the HTML file wsconsctl code show the "w" option is for compatibility use and does really nothing. > brightness setting still works via ADB keyboard on my PowerBook6,7 (iBook G4) > but setting display.brightness from command line does nothing on this device > and on another device (PowerBook G4). both are radeondrm perusing the code ... it seems setting the brightness is only possible on vgafb. ~ rgc
macppc wsconsctl screen brightness
misc@ i've been following 67-beta ... and just noticed this since #711. it is possible this issue occured earlier. i have no idea if display.brightness worked on 6.6-stable macppc.html shows i can do this via "wsconsctl -w XXX". ** note that wsconsctl doesn't have a "-w" option so macppc.html might need to be updated ** brightness setting still works via ADB keyboard on my PowerBook6,7 (iBook G4) but setting display.brightness from command line does nothing on this device and on another device (PowerBook G4). both are radeondrm rgc:/home/rgc/openbsd/www:29$ sysctl kern.version kern.version=OpenBSD 6.7 (GENERIC) #712: Tue May 5 10:40:23 MDT 2020 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC rgc:/home/rgc/openbsd/www:26$ doas wsconsctl display.brightness=50 rgc:/home/rgc/openbsd/www:27$ doas wsconsctl -a keyboard.type=usb keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard.map. keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=0 keyboard.encoding=us.swapctrlcaps keyboard1.type=usb keyboard1.bell.pitch=400 keyboard1.bell.period=100 keyboard1.bell.volume=50 keyboard1.bell.pitch.default=400 keyboard1.bell.period.default=100 keyboard1.bell.volume.default=50 wsconsctl: Use explicit arg to view keyboard1.map. keyboard1.repeat.del1=400 keyboard1.repeat.deln=100 keyboard1.repeat.del1.default=400 keyboard1.repeat.deln.default=100 keyboard1.ledstate=0 keyboard1.encoding=us.swapctrlcaps mouse.type=usb mouse.rawmode=1 mouse.scale=0,0,0,0,0,0,0 mouse.reverse_scrolling=0 mouse1.type=usb mouse1.reverse_scrolling=0 display.type=radeondrm display.width=1440 display.height=960 display.depth=32 display.fontwidth=12 display.fontheight=24 display.emulations=vt100 display.screentypes=std display.focus=4 display.screen_on=250 display.screen_off=6 display.vblank=on display.kbdact=on display.msact=off display.outact=on i have an 67-beta i386 machine where wsconsctl work correctly rgc:/home/rgc:8$ doas wsconsctl display.brightness=50 display.brightness -> 50.00% ~ rgc
Re: macbook - uvideo0: can't find video interface
On Mon, Apr 27, 2020 at 05:12:59PM +0200, Jan Stary wrote: > Thanks for the clue, video0 at uvideo0 is detected again > (dmesg below; NB: a different macbook with the same symptom). > note you're now showing an amd64 kernel log your first post all the logs were i386 so your analysis (one machine crashing, one machine just hangs) might be off a bit ~ rgc
Re: macpcc sysupgrade missing files
On Tue, Apr 07, 2020 at 04:28:35PM -0600, Theo de Raadt wrote: > There is a problem with some of the mirrors. It is being looked into. thanks! i tried again 24H later using another server near me. sysupgrade got the files. drwxr-xr-x 2 root wheel512 Apr 9 04:56 ./ drwxr-xr-x 5 root wheel512 Apr 1 06:36 ../ -rw-r--r-- 1 root wheel 48017 Apr 8 05:02 INSTALL.macppc -rw-r--r-- 1 root wheel 1820 Apr 9 04:55 SHA256 -rw-r--r-- 1 root wheel 160818907 Apr 8 05:02 base67.tgz -rw-r--r-- 1 root wheel 10387990 Apr 8 05:03 bsd -rw-r--r-- 1 root wheel 10479893 Apr 8 05:03 bsd.mp -rw-r--r-- 1 root wheel8285332 Apr 8 05:03 bsd.rd -rw-r--r-- 1 root wheel 6917 Apr 8 05:03 bsd.tbxi -rw-r--r-- 1 root wheel 72141076 Apr 8 05:03 comp67.tgz -rw-r--r-- 1 root wheel2790961 Apr 8 05:03 game67.tgz -rw-r--r-- 1 root wheel 0 Apr 9 04:56 keep -rw-r--r-- 1 root wheel7634013 Apr 8 05:03 man67.tgz -rw-r--r-- 1 root wheel 19256513 Apr 9 04:55 xbase66.tgz -rw-r--r-- 1 root wheel 19319974 Apr 9 04:55 xbase67.tgz -rw-r--r-- 1 root wheel 40293235 Apr 9 04:55 xfont66.tgz -rw-r--r-- 1 root wheel 40293238 Apr 9 04:56 xfont67.tgz -rw-r--r-- 1 root wheel 12732887 Apr 9 04:56 xserv66.tgz -rw-r--r-- 1 root wheel 12755370 Apr 9 04:56 xserv67.tgz -rw-r--r-- 1 root wheel4608898 Apr 9 04:56 xshare66.tgz -rw-r--r-- 1 root wheel4608911 Apr 9 04:56 xshare67.tgz and 6.7-beta installed after a reboot kern.version=OpenBSD 6.7-beta (GENERIC) #693: Tue Apr 7 00:39:20 MDT 2020 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC rgc > > rgc wrote: > > > misc@ > > > > was trying to sysupgrade to latest snapshot but got this
macpcc sysupgrade missing files
misc@ was trying to sysupgrade to latest snapshot but got this rgc:/home/rgc:94$ doas sysupgrade -kn Fetching from http://ftp.jaist.ac.jp/pub/OpenBSD/snapshots/macppc/ SHA256.sig 100% |*| 1882 00:00 Signature Verified Verifying old sets. INSTALL.macppc 100% |***| 48017 00:00 base67.tgz 100% |*| 153 MB00:18 bsd 100% |*| 10144 KB00:03 bsd.mp 100% |*| 10234 KB00:03 bsd.rd 100% |*| 8091 KB00:05 bsd.tbxi 100% |*| 6917 00:00 comp67.tgz 100% |*| 70450 KB00:12 game67.tgz 100% |*| 2725 KB00:01 man67.tgz100% |*| 7455 KB00:03 sysupgrade: Error retrieving http://ftp.jaist.ac.jp/pub/OpenBSD/snapshots/macppc/xbase66.tgz: 404 Not Found rgc:/home/rgc:91$ doas sysupgrade -kn doas (r...@apbg4.my.domain) password: Fetching from http://ftp.jaist.ac.jp/pub/OpenBSD/snapshots/macppc/ SHA256.sig 100% |*| 1882 00:00 Signature Verified Verifying old sets. sysupgrade: Error retrieving http://ftp.jaist.ac.jp/pub/OpenBSD/snapshots/macppc/xbase66.tgz: 404 Not Found rgc:/home/rgc:93$ doas vi /etc/installurl rgc:/home/rgc:94$ doas sysupgrade -kn Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/macppc/ SHA256.sig 100% |*| 1972 00:00 Signature Verified Verifying old sets. sysupgrade: Error retrieving https://cdn.openbsd.org/pub/OpenBSD/snapshots/macppc/xbase66.tgz: 404 Not Found i'm running kern.version=OpenBSD 6.6-current (GENERIC) #690: Tue Mar 31 16:32:01 MDT 2020 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC rgc
Re: heads up: amd64 snap
On Sat, Mar 07, 2020 at 04:19:17PM +0100, Otto Moerbeek wrote: > It looks like some BIOS do not like the recent biosboot changes. > Symptoms are a hang in the bios. > > I reverted them, the next amd64 snap should be ok again. > > -Otto i read notice last Sat ... Mon i was in the office and updated my "toy machine" with OpenBSD ... but not all the mirrors have fetched the latest snapshot, yet. i got bad snapshot. reading the whole thread it seems the most affected brand was Dell. the "toy machine" is a Dell Vostro 470 BIOS A14. it seems the Dell BIOS reads the disks before even going into a boot selection menu. for this Dell, going to BIOS means selecting the option from the "boot selection menu". HDD with bad biosboot + USB (install66.fs) fails to bring up the boot selection menu. i had to remove the HDD data cable for the machine to get back the "boot selection menu". - rgc
Re: upgrade i386 kernel to amd64
On Mon, Mar 02, 2020 at 03:14:06PM -0800, Justin Muir wrote: > If so, just upgrade system? Re-compile kernel? Other options? hi, i had the unenviable experience to downgrade an amd64 to i386 system with 6.6-current. this method is unsupported. i wanted to have a 32-bit cross compile system for macppc. 1 backup important files on the amd64 system 2 saved a list of installed port packages on my amd64 system. $ pkg_info -mz > save 3 then deleted all port packages $ doas pkg_delete -X 4 manually downloaded i386 tarballs and install the i386 bsd.rd file as bsd.upgrade. reboot. perform "upgrade". reboot to i386 system. 5 reinstalled the port packages $ doas pkg_add -l save 6 specifically installed sysclean and ran it. this *could* delete all remnants of the amd64 system. $ doas pkg_add sysclean $ doas sysclean $ doas vi /etc/sysclean.ignore (read the sysclean(8) *carefully*) i've done the "upgrade" a few months back ... and have done several -snapshot sysupgrade's to the i386 system. the viper lurking behind the shadows has not struck me yet. lastly, did i already mention that this method is unsupported? - rgc
experience setting up a low memory machine
misc@
sharing a recent experience with OpenBSD 6.6 and old, low spec, low memory
devices.
remember the Toshiba Libretto? back in 2000, OpenBSD got some CPU time on
one of mine. sadly that Libretto is now dead, and with the current state of
affairs, it wont be able to run OpenBSD.
last weekend i was able to snag one of the Libretto's cousin. this one is a
Cassiopeia Fiva 102. sligthly larger than the 70CT. has a touchpad, has USB,
a parallel, serial, IRDA, VGA, PS/2 port, an extra USB port on the dock. it
has 64Mb RAM (32Mb base + a 32Mb DIMM in the slot), expandable to 96Mb ...
if i can find old DIMMs. 6Gb PATA drivea. Cardbus slot. CPU is a Cyrix.
battery is toast but ... still a good looking ~20 year old laptop.
first order of bussiness, upgrade the disk. i have a 2x CF to PATA adapter
which i used. this adapter has a jumper to select which CF is the master.
for installing -current, i dded the install66.fs to a 512Mb CF. set that as
master and a 64Gb Sandisk as slave. install was smooth. first boot was OK.
then i noticed a big problem. the system seems to "hang" after 10mins.
testing more, i let the machine stand overnight. no change. i have the
command prompt, pressing ENTER creates a new line but i don't get the prompt
back. maybe it is the CF card. switched cards. tried 32Gb and 16Gb. same.
i thought it was the RAM ... i disable Fast boot ... and POST detected no
issues with the RAM. also i"ve installed -current several times already with
no hiccups, if the DIMM had issues it should have manifested when
decompressing the large tarball packages.
mounted the CF with "noatime" -> no change
vm.swapencrypt.enable = 0 -> no change
library_aslr=NO -> no change
in one final effort, i reinstalled everything again, rebooted, log in ...
and started top(1). lo and behold ... after 10mins i got my "hang" and a
probable culprit ...
every boot OpenBSD relinks the kernel ... i stared at the top display and
saw ld on top with around 170Mb ... literally out of memory ... and out of
swap space. on machines with small memory swap is configured by disklabel
as 2x physmem. in my case 122Mb swap was calculated but it was not enough
for the kernel relinking.
reinstalled everything again but customized the disklabel ... 4Gb of swap
was configured ... well i did waste 2Gb since 32-bit archs can only use 2Gb
and i'm too lazy to re-install again.
so that's something to watch out for when setting up low memory systems.
i was expecting ld to just segfault ... bec of the out of memory condition
but i never saw a segfault.
at the moment no more psuedo "hangs" ... but relink spews out an error
on every reboot:
(SHA256) /bsd: OK
LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o ${OBJS}
size: newbsd: not object file or archive
*** Error 1 in /usr/share/relink/kernel/GENERIC (Makefile:1125 'newbsd': @size
newbsd ; umask 007; echo mv newbsd newbsd.gdb; rm -f newbsd)
- and dc0 (i have 2 of these, 32-bit PC Card)
dc0 at cardbus0 dev 0 function 0 "Xircom X3201-3" rev 0x03: irq 11, address
00:06:29:xx:xx:xx
tqphy0 at dc0 phy 0: 78Q2120 10/100 PHY, rev. 11
can't see anyone on my network ... i see the ARP packets but i
can not ping anyone on my newly created network (sneakernet via USB
flash drives with BE and LE machines is complicated).
these cards work on my Powerbook G4.
- but axe0 works! slow (3-4ms ping to a local machine) ... but it works.
axe0 at uhub1 port 1 configuration 1 interface 0 "Apple Computer Ethernet
A1277" rev 2.00/0.01 addr 3
axe0: AX88772, address 10:9a:dd:xx:xx:xx
ukphy0 at axe0 phy 16: Generic IEEE 802.3u media interface, rev. 1: OUI
0x000ec6, model 0x0006
- so does urtwn0
urtwn0 at uhub1 port 2 configuration 1 interface 0 "I-O DATA DEVICE, INC.
WN-G150UM" rev 2.00/2.00 addr 4
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 34:76:c5:xx:xx:xx
but not much testing done yet.
- and urndis0 has issues
urndis0 at uhub1 port 2 configuration 1 interface 0 "Sony 501SO" rev 2.00/3.10
addr 3
urndis0: using RNDISurndis0: IOERROR
urndis0: query failed
: unable to get hardware address
ugen0 at uhub1 port 2 configuration 1 "Sony 501SO" rev 2.00/3.10 addr 3
urndis0 detached
ugen0 detached
ugen0 at uhub1 port 2 "Sony 501SO" rev 2.00/3.10 addr 3
ugen0 detached
- of course no Xorg
yorosiku ~
PS
and thanks for all the efforts of past and present developers ...
PPS
back to trying to understand PPC assembly and ofw ...
OpenBSD 6.6-current (GENERIC) #502: Thu Jan 16 11:34:46 MST 2020
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 63979520 (61MB)
avail mem = 47181824 (44MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 01/13/00, BIOS32 rev. 0 @ 0xfb970
apm0 at bios0: Power Management spec V1.2 (slowidle)
pcibios0 at bios0: rev 2.1 @ 0xf/0xbde8
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdfc0/48 (1 entries)
pcibios0: PCI Exclusive IRQs:
Re: 6.6-current #590 error
On Thu, Jan 09, 2020 at 07:35:17PM +0900, rgc wrote: > misc@ > > just a heads-up #590 has some issues. > > $ uname -a > OpenBSD pcfj10.my.domain 6.6 GENERIC.MP#590 amd64 > > $ pkg_info -mz > Cwd.c: loadable library and perl binaries are mismatched (got handshake key > 0xb70, needed 0xb60) > > yorosiku ~ > misc@ loaded up #594 and had the same issue. but i have another machine that i just updated to the same snapshot. this other machine is running properly. so it is a problem on my setup on this particular laptop. a hint came up after executing LD_DEBUG=1 perl `which pkg_info` doing dtors obj 0x5cb5a122800 @0x5cb0d78b7c0: [/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/Cwd/Cwd.so] after moving the [/usr/local/libdata/perl5] directory, everything went fine. perl seems to have re-created the files with latest versions. yorosiku ~
6.6-current #590 error
misc@ just a heads-up #590 has some issues. $ uname -a OpenBSD pcfj10.my.domain 6.6 GENERIC.MP#590 amd64 $ pkg_info -mz Cwd.c: loadable library and perl binaries are mismatched (got handshake key 0xb70, needed 0xb60) yorosiku ~
