Re: Installing a snapshot to a USB key using bsd.rd

[Rodney Polkinghorne]

Thanks Stuart

> Better to test sooner, if it still fails, if you can get a good report
> written up there's still some chance of a fix before release.

The machine is a cheap Dell laptop that's about 10 years old.  It's
possible that an innocent change in the software triggered a latent
hardware fault.

> Perhaps you caught the mirror mid-update, does it still happen now?

I did think of that.  Minutes after the install failed, I confirmed
that the mtimes on the Aarnet mirror were 10 hours old.  I might have
been mislead by timezones, and I'll try again tonight.

Rodney

Re: Installing a snapshot to a USB key using bsd.rd

[Stuart Henderson]

On 2018-03-18, Rodney Polkinghorne  wrote:
> Thanks for the replies.  I suspect this is the answer I needed: don't
> try to install a 6.2 snapshot just before version 6.3 is released,
> instead wait for the release and install that.

The only adaptations regarding it approaching release you need should be
setting the install path, and using -Dsnap when installing packages.

>> You need to be sure to use the bsd.rd from the snapshot!
>
> I'm pretty sure that's what I booted.  Does any other bsd.rd have a
> default path of pub/OpenBSD/6.3/i386?
>
>> You say install, which is very different from upgrade.
>
> I'm running 6.1 on my laptop hard disk, and I wanted to install a
> recent snapshot to a USB key.  The back story involves an upgrade to
> 6.2 stable, a kernel failure whenever I started X Windows, and a
> desire to reproduce the fault while preserving a bootable system on
> the hard disk.
>
> I'll wait for the 6.3 release, and see if X still crashes the kernel.

Better to test sooner, if it still fails, if you can get a good report
written up there's still some chance of a fix before release.

Re: Installing a snapshot to a USB key using bsd.rd

[Stuart Henderson]

On 2018-03-17, Rodney Polkinghorne  wrote:
> Hi
>
> This is my first post here, I appreciate how much work you all do, please
> be gentle. :-)
>
> Could someone please tell me how to install the latest snapshot, or point
> me at some instructions that work?  I tried the following:
>
> 1. Download bsd.rd and SHA256.sig from
> http://mirror.aarnet.edu.au/pub/OpenBSD/snapshots/
>
> 2. Fail to verify the 6.3 signatures, because I'm running 6.1.  (It would
> be nice if the signify man page had instructions to download and verify
> openbsd--base.pub.)

You can fetch this from src/etc/signify via cvsweb, or untar ./etc/signify
fron 6.2's base62.tgz.

> 3. Reboot, with boot> boot sd0a:/root/bsd.rd
>
> 4. Choose to install to sd1 (a USB key), default options, location of sets
> is http, HTTP server is mirror.aarnet.edu.au.
>
> 5. The default server directory is pub/OpenBSD/6.3/i386, override that with
> snapshots instead of 6.3
>
> 6. Leave all sets selected, and say done
>
> At this point, the installer reported that SHA256.sig had downloaded and
> verified, and that bsd downloaded but failed its checksum test.
>
> Possibly the answer is to ignore the checksums, but I want to ask first.

Perhaps you caught the mirror mid-update, does it still happen now?

Re: Installing a snapshot to a USB key using bsd.rd

[Rodney Polkinghorne]

Thanks for the replies.  I suspect this is the answer I needed: don't
try to install a 6.2 snapshot just before version 6.3 is released,
instead wait for the release and install that.

> You need to be sure to use the bsd.rd from the snapshot!

I'm pretty sure that's what I booted.  Does any other bsd.rd have a
default path of pub/OpenBSD/6.3/i386?

> You say install, which is very different from upgrade.

I'm running 6.1 on my laptop hard disk, and I wanted to install a
recent snapshot to a USB key.  The back story involves an upgrade to
6.2 stable, a kernel failure whenever I started X Windows, and a
desire to reproduce the fault while preserving a bootable system on
the hard disk.

I'll wait for the 6.3 release, and see if X still crashes the kernel.

Thanks again

Rodney

Re: the Alpha lives...

[Paul de Weerd]

Building a -current kernel took over an hour (I forgot to time it),
but it worked!  I'm now going to build a release, but that's going to
take several hours, if the kernel build time is any indication...

So here's the 6.3 dmesg (with some extra SCSI devices thrown into the
mix, for fun):

[ using 1147568 bytes of bsd ELF symbol table ]
consinit: not using prom console
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2018 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.3 (GENERIC) #0: Sun Mar 18 18:48:27 CET 2018
we...@alfalfa.alm.weirdnet.nl:/usr/src/sys/arch/alpha/compile/GENERIC
Digital Personal WorkStation 600au, 598MHz
8192 byte page size, 1 processor.
real mem = 536870912 (512MB)
rsvd mem = 1941504 (1MB)
avail mem = 515710976 (491MB)
mainbus0 at root
cpu0 at mainbus0: ID 0 (primary), 21164A-0 (unknown minor type 0)
cpu0: architecture extensions: 1
cia0 at mainbus0: DECchip 2117x Core Logic Chipset (Pyxis), pass 1
cia0: extended capabilities: 1
cia0: using BWX for PCI config and bus access
cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
pci0 at cia0 bus 0
dc0 at pci0 dev 3 function 0 "DEC 21142/3" rev 0x30: dec 550 irq 0, address 
00:00:f8:76:04:64
nsphy0 at dc0 phy 5: DP83840 10/100 PHY, rev. 1
pciide0 at pci0 dev 4 function 0 "CMD Technology PCI0646" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
cd0(pciide0:0:0): using PIO mode 3, DMA mode 1
pciide0: channel 1 disabled (no drives)
sio0 at pci0 dev 7 function 0 "Intel 82378IB ISA" rev 0x43
qlw0 at pci0 dev 12 function 0 "QLogic ISP1020" rev 0x05: dec 550 irq 8
qlw0: firmware rev 4.66.0, attrs 0x0
scsibus1 at qlw0: 16 targets, initiator 7
cd1 at scsibus1 targ 0 lun 0:  SCSI2 5/cdrom 
removable
cd2 at scsibus1 targ 1 lun 0:  SCSI2 5/cdrom 
removable
cd3 at scsibus1 targ 2 lun 0:  SCSI2 5/cdrom 
removable
cd4 at scsibus1 targ 3 lun 0:  SCSI2 5/cdrom 
removable
cd5 at scsibus1 targ 4 lun 0:  SCSI2 5/cdrom 
removable
sd0 at scsibus1 targ 5 lun 0:  SCSI2 0/direct removable
sd0: 96MB, 512 bytes/sector, 196608 sectors
st0 at scsibus1 targ 6 lun 0:  SCSI2 1/sequential removable
sd1 at scsibus1 targ 8 lun 0:  SCSI2 0/direct fixed 
serial.SEAGATE_ST34371W_JDD273270M5E3P
sd1: 4148MB, 512 bytes/sector, 8496884 sectors
sd2 at scsibus1 targ 9 lun 0:  SCSI2 0/direct fixed 
serial.IBM_DCAS-34330W_F3TD8398_
sd2: 4134MB, 512 bytes/sector, 8467200 sectors
sd3 at scsibus1 targ 10 lun 0:  SCSI2 0/direct fixed 
serial.IBM_DCAS-34330W_F3TE2118_
sd3: 4134MB, 512 bytes/sector, 8467200 sectors
ppb0 at pci0 dev 20 function 0 "DEC 21152" rev 0x02
pci1 at ppb0 bus 1
fxp0 at pci1 dev 8 function 0 "Intel 8255x" rev 0x0c, i82550: dec 550 irq 12, 
address 00:02:b3:61:21:e3
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
fxp1 at pci1 dev 9 function 0 "Intel 8255x" rev 0x08, i82559: dec 550 irq 16, 
address 00:02:b3:21:cd:c2
inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4
vga0 at pci1 dev 10 function 0 "Matrox MGA 1064SG 220MHz" rev 0x02
wsdisplay0 at vga0 mux 1
wsdisplay0: screen 0-5 added (80x25, vt100 emulation)
isa0 at sio0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x3bc/4 irq 7
mcclock0 at isa0 port 0x70/2: mc146818 or compatible
stray isa irq 14
stray isa irq 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd1a (92145ab06ead027c.a) swap on sd1b dump on sd1b
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
stray isa irq 3

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/ 

Re: the Alpha lives...

[Riccardo Mottola]

Hi Paul,

On 2018-03-18 15:55:34 +0100 Paul de Weerd  wrote:


I recently started to resurrect my old Alpha (Digital PWS 600au).  It
was spewing a garbled mess on serial console, so I had to find a PCI
video card to install in it first.  Then a PS/2 keyboard.  Then it
turned out to have reverted to the PWS 600a (AlphaBIOS, supposed to
run Windows NT).  This was due to a dead battery (no wonder, the
machine was in my storage for ~13 years).  However, with the battery
replaced, it booted fine into the OpenBSD 3.7 install that was still
on there.


compliments! I must admit the coolness factor!

I'm envious you can OpenBSD your alpha, while I am always been a SPARC 
(32) fan and now I have many machines but the only current OS is 
NetBSD!


I hope it will prove stable!

Riccardo

Re: With the latest snapshot there are some issues in Xfce, please help!

[Zsolt Kantor]

 For the snapshot packages I was told to use pkg_add -u first, and after that 
install the preferred package. That worked.
For the terminal I will check out the ports mailing list.For the touchpad, I 
got the point, thanks.


On Sunday, March 18, 2018, 2:37:40 PM GMT+2, Dave Voutila  
wrote:  
 
 Zsolt Kantor  writes:

> Hello to all.
> I installed the latest snapshot with Xfce. But there are some issues whit 
> Xfce. I found 3 problems.
>
> 1. The terminal size is very expanded, it is not 80x..., its 145x..., but if 
> I check the terminal properties the width setting is 80. Very strange.
>

The XFCE terminal? Might want to check ports@. No idea if this is an
upstream change or in the port itself.

> 2. There are some dependency problems when I try to install chromium
> or firefox. For instance the colord package can not be found in the
> snapshot packages repository, and other package dependency problems
> are also displayed. So I can't install Chromium or Firefox.

The snapshots are a moving target given the impending release of 6.3. 

Are you using `pkg_add -Dsnap firefox`? 

You might also need to grab the most recent build of -current if 
libraries were bumped. A dmesg would tell people if you're up to date
or not.

>
> 3. My synaptic touchpad is not fully functional. In Xfce the touchpad
> tab is missing from the mouse and touchpad configuration window. This
> is not the case of 6.2. In OpenBSD 6.2 it was there.
>

See note from 2017/12/05: https://www.openbsd.org/faq/current.html

You probably need a custom Xorg config, but if there is regression in
functionality I'm sure reporting the delta and a dmesg would be
helpful. Personally I've seen some improvements, but there were initial
regressions that were reported and I believe resolved or worked
around.

> Will these issues corrected until the release? Or should I send an e-mail to 
> the bug's mailing list?
>
> Thanks!
  

Re: X server keeps crashing in current/amd64

[Robert]

On Sun, 18 Mar 2018 13:41:26 +0100
Erling Westenvik  wrote:

> How long since you did an update before you started having problems? I
> had a similar situation some time ago on one of my current- machines
> that I hadn't updated in a long time.
> 
> Check the upgrade guides:
> https://www.openbsd.org/faq/upgrade62.html
> https://www.openbsd.org/faq/upgrade61.html
> And so on. And/or install sysclean(1) and have a look at its output.
> 
> Between upgrades I usually run:
> 
> # pkg_delete -[n]a
> 
> (-n being dry mode to see any changes without actually removing things.)
> 
> You may also take a look at pkg_check but read the man page first.
> 
> Best regards,
> 
> Erling

Bad wording from my side I guess... I am not compiling -current; I use
snapshots. And when I update (not on a regular base) to the newest
snapshot, I do a full fresh install using a shell script that does all
the additional configuration work for me.

So the problem is not a left-over from an upgrade operation.

kind regards,
Robert

Email web text messages to phone, but only at select times, but want to get later

[Chris Bennett]

I am using mod_perl/Apache (not for long, moving to base httpd) texting
both contact page and purchases info to my cell phone with
Email::Sender. But I don't want to get them in the middle of the night.
Right now I am just restricting them to acceptable hours, but I am
losing the texts at those hours.

Is there a way to send them to base smtpd to be sent once the right time
frame is OK, or do I just need to save them and run a cronjob to send
them later?

And I freely admit to being a little bit lazy on this, but I've been
working on repairing the big mess from when my old server company
shutdown all the servers without warning.
Plus I had the joy that the flu brings! Ugh.

I'm going to ask for help dealing with spam shortly before I start up
spamd, so I will be really digging into all of that shortly.
I've seen a ton of different methods and I don't know what's best at
all, so I will leave that for later. Not lazy for long!

Thanks,
Chris Bennett

the Alpha lives...

[Paul de Weerd]

Hi all,

I recently started to resurrect my old Alpha (Digital PWS 600au).  It
was spewing a garbled mess on serial console, so I had to find a PCI
video card to install in it first.  Then a PS/2 keyboard.  Then it
turned out to have reverted to the PWS 600a (AlphaBIOS, supposed to
run Windows NT).  This was due to a dead battery (no wonder, the
machine was in my storage for ~13 years).  However, with the battery
replaced, it booted fine into the OpenBSD 3.7 install that was still
on there.

Here's the dmesg from the latest snapshot (which is from October)
followed by the dmesg from what was still there:

I'll see if I can bring it into the 6.3 world too...

Paul 'WEiRD' de Weerd

[ using 1133880 bytes of bsd ELF symbol table ]
consinit: not using prom console
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2017 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.2-current (GENERIC) #157: Fri Oct 27 14:42:14 MDT 2017
dera...@alpha.openbsd.org:/usr/src/sys/arch/alpha/compile/GENERIC
Digital Personal WorkStation 600au, 598MHz
8192 byte page size, 1 processor.
real mem = 536870912 (512MB)
rsvd mem = 1941504 (1MB)
avail mem = 515784704 (491MB)
mainbus0 at root
cpu0 at mainbus0: ID 0 (primary), 21164A-0 (unknown minor type 0)
cpu0: architecture extensions: 1
cia0 at mainbus0: DECchip 2117x Core Logic Chipset (Pyxis), pass 1
cia0: extended capabilities: 1
cia0: using BWX for PCI config and bus access
cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
pci0 at cia0 bus 0
dc0 at pci0 dev 3 function 0 "DEC 21142/3" rev 0x30: dec 550 irq 0, address 
00:00:f8:76:04:64
nsphy0 at dc0 phy 5: DP83840 10/100 PHY, rev. 1
pciide0 at pci0 dev 4 function 0 "CMD Technology PCI0646" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
cd0(pciide0:0:0): using PIO mode 3, DMA mode 1
pciide0: channel 1 ignored (disabled)
sio0 at pci0 dev 7 function 0 "Intel 82378IB ISA" rev 0x43
qlw0 at pci0 dev 12 function 0 "QLogic ISP1020" rev 0x05: dec 550 irq 8
qlw0: firmware rev 4.66.0, attrs 0x0
qlw0: ignoring premature mbox int
scsibus1 at qlw0: 16 targets, initiator 7
cd1 at scsibus1 targ 3 lun 0:  SCSI2 5/cdrom 
removable
sd0 at scsibus1 targ 8 lun 0:  SCSI2 0/direct fixed 
serial.SEAGATE_ST34371W_JDD273270M5E3P
sd0: 4148MB, 512 bytes/sector, 8496884 sectors
sd1 at scsibus1 targ 9 lun 0:  SCSI2 0/direct fixed 
serial.IBM_DCAS-34330W_F3TD8398_
sd1: 4134MB, 512 bytes/sector, 8467200 sectors
sd2 at scsibus1 targ 10 lun 0:  SCSI2 0/direct fixed 
serial.IBM_DCAS-34330W_F3TE2118_
sd2: 4134MB, 512 bytes/sector, 8467200 sectors
ppb0 at pci0 dev 20 function 0 "DEC 21152" rev 0x02
pci1 at ppb0 bus 1
fxp0 at pci1 dev 8 function 0 "Intel 8255x" rev 0x0c, i82550: dec 550 irq 12, 
address 00:02:b3:61:21:e3
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
fxp1 at pci1 dev 9 function 0 "Intel 8255x" rev 0x08, i82559: dec 550 irq 16, 
address 00:02:b3:21:cd:c2
inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4
vga0 at pci1 dev 10 function 0 "Matrox MGA 1064SG 220MHz" rev 0x02
wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
isa0 at sio0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x3bc/4 irq 7
mcclock0 at isa0 port 0x70/2: mc146818 or compatible
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (92145ab06ead027c.a) swap on sd0b dump on sd0b
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
stray isa irq 4
stray isa irq 3


Old dmesg:


[ using 463776 bytes of bsd ELF symbol table ]
consinit: not using prom console
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2005 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 3.7-current (GENERIC) #489: Wed May 11 22:28:26 MDT 2005
dera...@alpha.openbsd.org:/usr/src/sys/arch/alpha/compile/GENERIC
Digital Personal WorkStation 600au, 598MHz
8192 byte page size, 1 processor.
total memory = 536870912 (524288K)
(1941504 reserved for PROM, 534929408 used by OpenBSD)
avail memory = 462487552 (451648K)
using 6529 buffers containing 53485568 bytes (52232K) of memory
mainbus0 (root)
cpu0 at mainbus0: ID 0 (primary), 21164A-0 (unknown minor type 0)
cpu0: Architecture extensions: 1
cia0 at mainbus0: DECchip 2117x 

Re: With the latest snapshot there are some issues in Xfce, please help!

[Dave Voutila]

Zsolt Kantor  writes:

> Hello to all.
> I installed the latest snapshot with Xfce. But there are some issues whit 
> Xfce. I found 3 problems.
>
> 1. The terminal size is very expanded, it is not 80x..., its 145x..., but if 
> I check the terminal properties the width setting is 80. Very strange.
>

The XFCE terminal? Might want to check ports@. No idea if this is an
upstream change or in the port itself.

> 2. There are some dependency problems when I try to install chromium
> or firefox. For instance the colord package can not be found in the
> snapshot packages repository, and other package dependency problems
> are also displayed. So I can't install Chromium or Firefox.

The snapshots are a moving target given the impending release of 6.3. 

Are you using `pkg_add -Dsnap firefox`? 

You might also need to grab the most recent build of -current if 
libraries were bumped. A dmesg would tell people if you're up to date
or not.

>
> 3. My synaptic touchpad is not fully functional. In Xfce the touchpad
> tab is missing from the mouse and touchpad configuration window. This
> is not the case of 6.2. In OpenBSD 6.2 it was there.
>

See note from 2017/12/05: https://www.openbsd.org/faq/current.html

You probably need a custom Xorg config, but if there is regression in
functionality I'm sure reporting the delta and a dmesg would be
helpful. Personally I've seen some improvements, but there were initial
regressions that were reported and I believe resolved or worked
around.

> Will these issues corrected until the release? Or should I send an e-mail to 
> the bug's mailing list?
>
> Thanks!

Re: X server keeps crashing in current/amd64

[Erling Westenvik]

On Sat, Mar 17, 2018 at 10:40:55PM +0100, Robert wrote:
> Since about two weeks the X server keeps crashing (segfault) most of the
> time when I start it (through xenodm).
> I have to restart it (rcctl restart xenodm) about 5-10 times
> until I get an (xfce) session that stays stable.
>
> I reinstalled today with the latest current/amd64, and now this issue became
> worse: In addition, even when I get a stable session, it crashes as
> soon as I do some actions, such as moving the mouse for a couple of
> seconds or starting Firefox.

How long since you did an update before you started having problems? I
had a similar situation some time ago on one of my current- machines
that I hadn't updated in a long time.

Check the upgrade guides:
https://www.openbsd.org/faq/upgrade62.html
https://www.openbsd.org/faq/upgrade61.html
And so on. And/or install sysclean(1) and have a look at its output.

Between upgrades I usually run:

# pkg_delete -[n]a

(-n being dry mode to see any changes without actually removing things.)

You may also take a look at pkg_check but read the man page first.

Best regards,

Erling

> Xorg.log says (from various such occurences):
> (EE) Segmentation fault at address 0x64bfcd81018
> (EE) Segmentation fault at address 0x17e082969018
> (EE) Segmentation fault at address 0x78e6159b000
>
> Any ideas / recommendations on how to debug or fix this?
> (dmesg / xorg log below)
>
> Installing 6.2/amd64 removes the issue, so I don't think it's a hardware 
> problem.
>
> If it is relevant, this is an AMD Verde GPU, where the driver uses
> software rendering. Also, I disabled xhci in the kernel (using config) due to 
> https://marc.info/?l=openbsd-misc=143442925331480 .
>
> regards,
> Robert
>
>
> dmesg (current
> OpenBSD 6.3 (GENERIC.MP) #68: Fri Mar 16 01:24:47 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 17113550848 (16320MB)
> avail mem = 16587821056 (15819MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec380 (81 entries)
> bios0: vendor Dell Inc. version "A15" date 02/15/2017
> bios0: Dell Inc. OptiPlex 3020
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT SLIC SSDT SSDT SSDT HPET SSDT MCFG SSDT
> acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP04(S4) 
> PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S0) 
> EHC2(S0) XHC_(S0) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3492.35 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> acpitimer0: recalibrated TSC frequency 3292383348 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3491.93 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 4 (application processor)
> cpu2: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3491.93 MHz
> cpu2: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 2, package 0
> cpu3 at mainbus0: apid 6 (application processor)
> cpu3: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, 3491.93 MHz
> cpu3: 
> 

Re: X server keeps crashing in current/amd64

[Robert]

Hi Jonathan,

Thanks for the quick response!
I will test it as soon as a new snapshot becomes available.

I see that the changes are related to the cursor sprite - maybe this
will even fix the effect that currently the mouse cursor gets
temporarily duplicated on both screens during certain actions (such as
starting Firefox).

regards,
Robert


On Sun, 18 Mar 2018 10:51:00 +1100
Jonathan Gray  wrote:

> On Sat, Mar 17, 2018 at 10:40:55PM +0100, Robert wrote:
> > Hi,
> > 
> > Since about two weeks the X server keeps crashing (segfault) most of the
> > time when I start it (through xenodm).
> > I have to restart it (rcctl restart xenodm) about 5-10 times
> > until I get an (xfce) session that stays stable. 
> > 
> > I reinstalled today with the latest current/amd64, and now this issue became
> > worse: In addition, even when I get a stable session, it crashes as
> > soon as I do some actions, such as moving the mouse for a couple of
> > seconds or starting Firefox.
> > 
> > Xorg.log says (from various such occurences):
> > (EE) Segmentation fault at address 0x64bfcd81018
> > (EE) Segmentation fault at address 0x17e082969018
> > (EE) Segmentation fault at address 0x78e6159b000
> > 
> > Any ideas / recommendations on how to debug or fix this?
> > (dmesg / xorg log below)  
> 
> I see you have multiple screens in your Xorg log.
> 
> I've just committed an update to xf86-video-ati 18.0.1 which
> mentions fixing a crash with multiple screens.
> 
> https://lists.x.org/archives/xorg-announce/2018-March/002884.html
> 
> * The Xorg process could crash when multiple primary screens are
>   configured in xorg.conf.
> 
> Index: configure
> ===
> RCS file: /cvs/xenocara/driver/xf86-video-ati/configure,v
> retrieving revision 1.23
> diff -u -p -r1.23 configure
> --- configure 13 Mar 2018 06:13:13 -  1.23
> +++ configure 17 Mar 2018 23:25:41 -
> @@ -1,6 +1,6 @@
>  #! /bin/sh
>  # Guess values for system-dependent variables and create Makefiles.
> -# Generated by GNU Autoconf 2.69 for xf86-video-ati 18.0.0.
> +# Generated by GNU Autoconf 2.69 for xf86-video-ati 18.0.1.
>  #
>  # Report bugs to 
> .
>  #
> @@ -591,8 +591,8 @@ MAKEFLAGS=
>  # Identity of this package.
>  PACKAGE_NAME='xf86-video-ati'
>  PACKAGE_TARNAME='xf86-video-ati'
> -PACKAGE_VERSION='18.0.0'
> -PACKAGE_STRING='xf86-video-ati 18.0.0'
> +PACKAGE_VERSION='18.0.1'
> +PACKAGE_STRING='xf86-video-ati 18.0.1'
>  
> PACKAGE_BUGREPORT='https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Driver/Radeon'
>  PACKAGE_URL=''
>  
> @@ -1390,7 +1390,7 @@ if test "$ac_init_help" = "long"; then
># Omit some internal or obsolete options to make the list less imposing.
># This message is too long to be a string in the A/UX 3.1 sh.
>cat <<_ACEOF
> -\`configure' configures xf86-video-ati 18.0.0 to adapt to many kinds of 
> systems.
> +\`configure' configures xf86-video-ati 18.0.1 to adapt to many kinds of 
> systems.
>  
>  Usage: $0 [OPTION]... [VAR=VALUE]...
>  
> @@ -1460,7 +1460,7 @@ fi
>  
>  if test -n "$ac_init_help"; then
>case $ac_init_help in
> - short | recursive ) echo "Configuration of xf86-video-ati 18.0.0:";;
> + short | recursive ) echo "Configuration of xf86-video-ati 18.0.1:";;
> esac
>cat <<\_ACEOF
>  
> @@ -1616,7 +1616,7 @@ fi
>  test -n "$ac_init_help" && exit $ac_status
>  if $ac_init_version; then
>cat <<\_ACEOF
> -xf86-video-ati configure 18.0.0
> +xf86-video-ati configure 18.0.1
>  generated by GNU Autoconf 2.69
>  
>  Copyright (C) 2012 Free Software Foundation, Inc.
> @@ -2031,7 +2031,7 @@ cat >config.log <<_ACEOF
>  This file contains any messages produced by compilers while
>  running configure, to aid debugging if configure makes a mistake.
>  
> -It was created by xf86-video-ati $as_me 18.0.0, which was
> +It was created by xf86-video-ati $as_me 18.0.1, which was
>  generated by GNU Autoconf 2.69.  Invocation command line was
>  
>$ $0 $@
> @@ -2862,7 +2862,7 @@ fi
>  
>  # Define the identity of the package.
>   PACKAGE='xf86-video-ati'
> - VERSION='18.0.0'
> + VERSION='18.0.1'
>  
>  
>  cat >>confdefs.h <<_ACEOF
> @@ -19881,7 +19881,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_wri
>  # report actual input values of CONFIG_FILES etc. instead of their
>  # values after options handling.
>  ac_log="
> -This file was extended by xf86-video-ati $as_me 18.0.0, which was
> +This file was extended by xf86-video-ati $as_me 18.0.1, which was
>  generated by GNU Autoconf 2.69.  Invocation command line was
>  
>CONFIG_FILES= $CONFIG_FILES
> @@ -19947,7 +19947,7 @@ _ACEOF
>  cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
>  ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; 
> s/[\\""\`\$]/&/g'`"
>  ac_cs_version="\\
> -xf86-video-ati config.status 18.0.0
> +xf86-video-ati config.status 18.0.1
>  configured by $0, generated by GNU