Re: Userspace serial console not working since OpenBSD-7.1 release

2022-09-15 Thread James Stark
It appears that a small amount of the output was lost coming across
the serial console.  Hopefully that has what you need.  if not I can
try booting bsd.rd and getting dmesg that way.   ACPU dumps are
attached.

James

>> OpenBSD/amd64 BOOT 3.55
boot> bsd.70
booting hd0a:bsd.70: 14841112|594/]=0x15ce690
entry point at 0x81001000
 [ using 3122832 bytes of bsd ELF symbol table ]
Copyright (c) 1982fornia.  All rights reserved.
Copyright (c) 1995-2021 OpenBSD. All rights reserved.  https://www.OpenBSD.org

hu Sep 30 14:25:29 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4267245568 (4069MB)
avail mem = 4121886720 (3930MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9f800 (22 entries)
bios0: vendor American Megatrends Inc. version "080
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI
acpitimer0 at acpi0: 3579545 Hzdr 0xfee0: PC-AT compatUSB5(S4)
EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4) P0P4(S4) P0P5(S4)
P0P6(S4) P
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1800.21 MHz, 06-1c-0a
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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MC-substates=0.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1799.99 MHz, 06-1c-0a
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,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: disabling user TSC (skew=207)
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1799.98 MHz, 06-1c-0a
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,A,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu2: 512KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Atom(TM) CPU D525 @ 1.80GHz, 1799.98 MHz, 06-1c-0a
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu3: disabling user TSC (skew=202)
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (P0P1)
acpiprt2 at acpi0: bus 1 (P0P4)
acpiprt3 at acpi0: bus -1 (P0P5)
acpiprt4 at acpi0: bus 2 (PP0P7)
acpiprt6 at acpi0: bus 4 (P0P8)
acpiprt7 at acpi0: bus -acpipci0 at acpi0 PCI0
acpicmos0 at acpi0
acpibtn0 at acpi0: PWRB
acpicpuu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
 pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02
inteldrm0 at pci0 dev 2 function 0 "Intel Pineview Video" rev 0x02
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: apic 4 int 16, PINEVIEW, v 0x02 at pci0 dev 2 function 1
not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 4 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 4 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x02: apic 4 int 19
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x02: apic 4 int 18
uhub0 at usb0 configuration 1 inrev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 02: msi
io0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIus 1
ppb1 at pci0 dev 28 function 2 "Intel 82801I PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
00:30:18:a5:6e:6a
ppbel 82801I PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
em1 at pci3 dev 0x00: msi, address 00:30:18:a5:6e:6b
ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x02: msi
p dev 0 function 0 "ASMedia ASM1042 xHCI" rev 0x00: msi, xHCI 0.96
usb1 at xhci0: USB revision 3.0
uhub1 at usb1 configuration 1 interface 0 "ASMedia xHCI root hub" rev
3.00/1.00 addr 1
uhci3 at pci0 dev 29 function 0  function 1 "Intel 82801I USB" rev
0x02: apic 4 int 19
uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x02: apic 4 int 18
ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x02: apic 4 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 "92
pci5 

Re: Unable to complete secure online login

2022-09-15 Thread patrick keshishian
On 9/15/22, Alton Shaw  wrote:
> Completely new user "test01", fired up fresh installation of Firefox,
> new blank tab, closed all other Mozilla's initial tabs, cleared
> cookies/history/cache/etc, browsed to my bank's login page. Attempted
> login but received the same result: We’re currently having technical
> issue Please try again later.
>
> I've no idea how to proceed from here.  Is there a log or console
> somewhere within OpenBSD that I should be watching/checking?

I had a similar problem with Brave browser on MacOS
attempting to login to a site.  Although different
OS and different browser, this experience may help
you in debugging your case.

I was getting similar login issue with a site.  I
don't often login to this site.  My last successful
login was possibly in May using the same OS and
same browser (but possibly an earlier version).

By turning "Shields down" for that particular site,
the login process went through successfully.  The
Brave Shields block various trackers, ads, finger-
printing, and cross-site cookies.

If FF has similar "protections", you may try
turning those off to see if that helps your
situation.

--patrick



Re: Unable to complete secure online login

2022-09-15 Thread Alton Shaw
Completely new user "test01", fired up fresh installation of Firefox, 
new blank tab, closed all other Mozilla's initial tabs, cleared 
cookies/history/cache/etc, browsed to my bank's login page. Attempted 
login but received the same result: We’re currently having technical 
issue Please try again later.


I've no idea how to proceed from here.  Is there a log or console 
somewhere within OpenBSD that I should be watching/checking?


Re: X11 keeps reverting display to state from a few seconds ago

2022-09-15 Thread James Cook
On Tue Sep 13, 2022 at 2:52 AM UTC, James Cook wrote:
> On Sun Sep 11, 2022 at 3:50 AM UTC, Jonathan Gray wrote:
> > On Sun, Sep 11, 2022 at 03:18:47AM +, James Cook wrote:
> > > >Synopsis:X11 keeps showing images from a few seconds ago
> > > >Category:kernel
> > > >Environment:
> > >   System  : OpenBSD 7.2
> > >   Details : OpenBSD 7.2-beta (GENERIC.MP) #718: Fri Sep  9 14:46:40 
> > > MDT 2022
> > >
> > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > > 
> > >   Architecture: OpenBSD.amd64
> > >   Machine : amd64
> > > >Description:
> > >   After the latest sysupgrade -s, every few seconds, the contents of my
> > >   display briefly goes back to what it was a few seconds ago.
> >
> > What were you running before this?
>
> OpenBSD 7.2-beta (GENERIC.MP) #714: Fri Sep  2 15:20:16 MDT 2022 
>
> > some defaults for power saving features recently changed
> >
> > does this diff change what you see?
>
> It seems to fix the problem, but I'm not certain, because the behaviour
> started to become much less obvious after I sent this bug report (but
> before I tried your diff). I would see the occasional short flicker
> rather than reversions lasting nearly a second. With your diff I haven't
> seen any flickers.
>
> Going back to the Sep 9 snapshot kernel (which I was using when I filied
> this bug) I tried to find things that would trigger the problem the reliably,
> so I could try the same things with your diff, but I couldn't find a way
> to trigger it. (Mostly I just tried vigorously scrolling in Firefox
> assuming taxing the graphics card would trigger it, but that didn't
> work.)
>
> -- 
> James

At this point I'm 95% sure the diff fixed the problem. I have been
running the new kernel for a few days with no flickering, and whenever I
go back to /obsd to compare, I eventually see a flicker or two.

-- 
James



Re: Unable to complete secure online login

2022-09-15 Thread Landry Breuil
Le Thu, Sep 15, 2022 at 05:40:47AM -0700, Alton Shaw a écrit :
> So I completely removed Firefox, Firefox-ESR, & Chromium and then reinstall
> Firefox.  Started Firefox, without changing any settings went straight to my
> banking site, tried to login and received exactly the same result: "/We’re
> currently having technical issue Please try again later./"
> 
> At this point I don't know what to try next.

Removing browsers is one thing, did you try with a clean profile ?
reinstalling browsers wont do anything if you dont remove old
profiles...

> Also, would surf behave differently than any of the other browsers with
> regards to "natted" and "/29"

surf uses webkitgtk.



Re: Unable to complete secure online login

2022-09-15 Thread Alton Shaw
So I completely removed Firefox, Firefox-ESR, & Chromium and then 
reinstall Firefox.  Started Firefox, without changing any settings went 
straight to my banking site, tried to login and received exactly the 
same result: "/We’re currently having technical issue Please try again 
later./"


At this point I don't know what to try next.

So far I've tried to login using Firefox, Firefox-ESR, Chromium, and 
surf with only the latter being successful and all of the other three 
resulting in the same error.  Within Firefox, after clearing the 
history, cookies, and the cache, I used Agent Switcher to attempt to 
login as Firefox/Windows 10 without success (same error).


I'm stumped, any suggestions as to what to try.

Also, would surf behave differently than any of the other browsers with 
regards to "natted" and "/29"


On 2022-09-14 15:30, Alton Shaw wrote:
Thanks Crystal.  I'm thinking my next step is to pkg_delete each of 
the browsers except surf and then pkg_add mozilla-firefox and give it 
a try with the as-installed default settings. At least surf provides 
me a work around which is appreciated when it comes time to pay the 
bills :-]


On 2022-09-14 14:57, Crystal Kolipe wrote:

On Wed, Sep 14, 2022 at 12:05:02PM -0700, Alton Shaw wrote:

I next installed surf and pointed it 
tohttps://secure.royalbank.com/statics/login-service-ui/index#/full/signin?LANGUAGE=ENGLISH
and I was able to login without any problems.

Glad that worked :-).


I have no idea what that means in that Firefox, Firefox-ESR, & Chromium
won't work but surf does

Basically, it means that the bank is not overly fussy about which browser you
are using, and what settings you are using, (which is what I expected).

In other words, they are not 'blocking all browsers except for a specific few',
but rather for some reason your particular configuration is tripping them up.

So it should be fixable.


other than perhaps I need to fiddle with third
party cookies & security settings as suggested by Otto.

If surf works in it's default configuration, then you do NOT need third party
cookies enabled, as surf does not enable them by default.




Re: re(4) drivers not working

2022-09-15 Thread Adam Szewczyk
Ok, I will check if I have some time to perform installation on actual HW,
but the idea is to be able to run it on xen. There is growing interest in
using OpenBSD, as a sys-net for Qubes OS instead of the original one based
on Linux. So it is crucial for me to be able to use re(4) and iwm(4) with
my NICs on Xen. I understand that if the issue will be caused by having xen
in the middle I should report the issue to its maintainers.

czw., 15 wrz 2022 o 02:03 Jonathan Gray  napisał(a):

> On Wed, Sep 14, 2022 at 10:23:32PM +0200, Adam Szewczyk wrote:
> > After installation of OpenBSD as HVM on Qubes OS with passed through
> > Realtek NIC driver starts to spamming with "re0: watchdog timeout"
> message
> > and not working. Attaching dmesg.
>
> Try without xen.  It may be messing up interrupts.
>
> >
> > OpenBSD 7.1 (GENERIC.MP) #465: Mon Apr 11 18:03:57 MDT 2022
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 1040183296 (991MB)
> > avail mem = 991436800 (945MB)
> > random: good seed from bootblocks
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfc10 (12 entries)
> > bios0: vendor Xen version "4.14.5" date 08/24/2022
> > bios0: Xen HVM domU
> > acpi0 at bios0: ACPI 4.0
> > acpi0: sleep states S3 S4 S5
> > acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT
> > acpi0: wakeup devices
> > acpitimer0 at acpi0: 3579545 Hz, 32 bits
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins, remapped
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2593.27 MHz, 06-9e-0a
> > cpu0:
> >
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> > cpu0: 256KB 64b/line 8-way L2 cache
> > cpu0: smt 0, core 0, package 0
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 100MHz
> > cpu1 at mainbus0: apid 2 (application processor)
> > cpu1: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2592.03 MHz, 06-9e-0a
> > cpu1:
> >
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> > cpu1: 256KB 64b/line 8-way L2 cache
> > cpu1: smt 0, core 1, package 0
> > acpihpet0 at acpi0: 6250 Hz
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpipci0 at acpi0 PCI0
> > acpicmos0 at acpi0
> > "ACPI0007" at acpi0 not configured
> > "ACPI0007" at acpi0 not configured
> > acpicpu0 at acpi0: C1(@1 halt!)
> > acpicpu1 at acpi0: C1(@1 halt!)
> > cpu0: using VERW MDS workaround (except on vmm entry)
> > pvbus0 at mainbus0: Xen 4.14
> > xen0 at pvbus0: features 0x2705, 2048 grant table frames, event channel 1
> > xbf0 at xen0 backend 0 channel 6: disk
> > scsibus1 at xbf0: 1 targets
> > sd0 at scsibus1 targ 0 lun 0: 
> > sd0: 10240MB, 512 bytes/sector, 20971520 sectors
> > xbf1 at xen0 backend 0 channel 7: disk
> > scsibus2 at xbf1: 1 targets
> > sd1 at scsibus2 targ 0 lun 0: 
> > sd1: 2048MB, 512 bytes/sector, 4194304 sectors
> > xbf2 at xen0 backend 0 channel 8: disk
> > scsibus3 at xbf2: 1 targets
> > sd2 at scsibus3 targ 0 lun 0: 
> > sd2: 10240MB, 512 bytes/sector, 20971520 sectors
> > xnf0 at xen0 backend 113 channel 9: address 00:16:3e:5e:6c:00
> > pci0 at mainbus0 bus 0
> > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> > pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> > pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
> channel
> > 0 wired to compatibility, channel 1 wired to compatibility
> > pciide0: channel 0 disabled (no drives)
> > pciide0: channel 1 disabled (no drives)
> > piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: SMBus
> > disabled
> > xspd0 at pci0 dev 2 function 0 "XenSource Platform Device" rev 0x01
> > vga1 at pci0 dev 3 function 0 "Bochs VGA" rev 0x02
> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> > wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> > ehci0 at pci0 dev 4 function 0 "Intel 82801DB USB" rev 0x10: apic 1 int
> 35
> > usb0 at ehci0: USB revision 2.0
> > uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
> > 2.00/1.00 addr 1
> > re0 at pci0 dev 6 function 0 "Realtek 8168" rev 0x15: RTL8168H/8111H
> > (0x5400), msi, address 98:fa:9b:11:d0:cf
> >