Re: pledge violation in firefox-60 on snapshots
$ grep SYS_fork /usr/include/sys/syscall.h #define SYS_fork2 See: https://marc.info/?l=openbsd-ports&m=152623658627250&w=2 You probably don't run dbus, so I assume you're going to need to start it up in your .xsession file. martijn@ On 05/16/18 03:59, William Orr wrote: > Hey there, > > When visiting the following health insurance site: > > https://www.cignaglobal.com/CASPAI/public/SignIn.do?application=CIEB_IPMI&country=GB&language=en&select-roles=all&safeReturn=https://www.cignaglobal.com/ma/pages/CASPA/Landing.html&domain=. > > Clicking the password field will consistently cause that tab in firefox > to crash with a pledge violation (calling fork): > > firefox[75379]: pledge "proc", syscall 2 > firefox[99617]: pledge "proc", syscall 2 > firefox[89996]: pledge "proc", syscall 2 > firefox[29564]: pledge "proc", syscall 2 > firefox[58111]: pledge "proc", syscall 2 > firefox[97980]: pledge "proc", syscall 2 > firefox[37363]: pledge "proc", syscall 2 > > Is anyone else seeing something similar? I've repro'd this in safe mode > with add-ons disabled. I'm runnning a snapshot as of 3 days ago with > firefox from packages. > > % pkg_info firefox > Information for inst:firefox-60.0 > > > Following is a full dmesg. Let me know if there's other info that I can > provide. There are other firefox pledge violations in there, but I have > no indication that they're related. > > Thanks! > > OpenBSD 6.3-current (GENERIC.MP) #29: Fri May 4 09:22:48 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17040244736 (16250MB) > avail mem = 16515768320 (15750MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xee7f0 (26 entries) > bios0: vendor American Megatrends Inc. version "P2.90" date 07/11/2013 > bios0: ASRock Z77 Extreme4 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT MCFG SSDT AAFT HPET SSDT SSDT SSDT BGRT > acpi0: wakeup devices UAR1(S4) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) > USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4) RP03(S4) RP04(S4) > RP05(S4) BR40(S4) RP06(S4) [...] > 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) i7-3770K CPU @ 3.50GHz, 3500.52 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,EST,TM2,SSSE3,CX16,xTPR,PDCM > > ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 100MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.02 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,EST,TM2,SSSE3,CX16,xTPR,PDCM > > ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,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) i7-3770K CPU @ 3.50GHz, 3500.02 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,EST,TM2,SSSE3,CX16,xTPR,PDCM > > ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,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) i7-3770K CPU @ 3.50GHz, 3500.02 MHz > cpu3: > 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,EST,TM2,SSSE3,CX16,xTPR,PDCM > > ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 0, core 3, package 0 > cpu4 at mainbus0: apid 1 (application processor) >
Re: pledge violation in firefox-60 on snapshots
Hi, I'm also facing similar issues with firefox-60.0 installed from ports: orion# tail -n 4 /var/log/messages May 15 21:01:58 orion /bsd: firefox[21099]: pledge "inet", syscall 105 May 15 21:01:58 orion /bsd: firefox[21099]: pledge "stdio", syscall 72 May 15 21:08:29 orion /bsd: firefox[13436]: pledge "inet", syscall 105 May 15 21:08:29 orion /bsd: firefox[13436]: pledge "stdio", syscall 28 orion# uname -a OpenBSD orion.lan 6.3 GENERIC.MP#38 amd64 It happens when I browse ebay.com website. Regards, -- Renato Aguiar
pledge violation in firefox-60 on snapshots
Hey there, When visiting the following health insurance site: https://www.cignaglobal.com/CASPAI/public/SignIn.do?application=CIEB_IPMI&country=GB&language=en&select-roles=all&safeReturn=https://www.cignaglobal.com/ma/pages/CASPA/Landing.html&domain=. Clicking the password field will consistently cause that tab in firefox to crash with a pledge violation (calling fork): firefox[75379]: pledge "proc", syscall 2 firefox[99617]: pledge "proc", syscall 2 firefox[89996]: pledge "proc", syscall 2 firefox[29564]: pledge "proc", syscall 2 firefox[58111]: pledge "proc", syscall 2 firefox[97980]: pledge "proc", syscall 2 firefox[37363]: pledge "proc", syscall 2 Is anyone else seeing something similar? I've repro'd this in safe mode with add-ons disabled. I'm runnning a snapshot as of 3 days ago with firefox from packages. % pkg_info firefox Information for inst:firefox-60.0 Following is a full dmesg. Let me know if there's other info that I can provide. There are other firefox pledge violations in there, but I have no indication that they're related. Thanks! OpenBSD 6.3-current (GENERIC.MP) #29: Fri May 4 09:22:48 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17040244736 (16250MB) avail mem = 16515768320 (15750MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xee7f0 (26 entries) bios0: vendor American Megatrends Inc. version "P2.90" date 07/11/2013 bios0: ASRock Z77 Extreme4 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT AAFT HPET SSDT SSDT SSDT BGRT acpi0: wakeup devices UAR1(S4) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) BR40(S4) RP06(S4) [...] 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) i7-3770K CPU @ 3.50GHz, 3500.52 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,EST,TM2,SSSE3,CX16,xTPR,PDCM ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.02 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,EST,TM2,SSSE3,CX16,xTPR,PDCM ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,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) i7-3770K CPU @ 3.50GHz, 3500.02 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,EST,TM2,SSSE3,CX16,xTPR,PDCM ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,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) i7-3770K CPU @ 3.50GHz, 3500.02 MHz cpu3: 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,EST,TM2,SSSE3,CX16,xTPR,PDCM ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3500.02 MHz cpu4: 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,EST,TM2,SSSE3,CX16,xTPR,PDCM ,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu4: 256
Re: print usb printer by [ Google Cloud Print for Chromium ]
On 05/15/18 18:19, IL Ka wrote: Hello Jordan, >> you can do some neat things and avoid having to remove the ulpt(4) driver from the kernel What can be the reason to remove it? Some people remove the ulpt driver to allow CUPS to interface easier with their printer. This solution has always irritated me, and I prefer using lpd to manage my printers. CUPS can still be used to print to an lpd based print server, the only difference is that CUPS isn't handling the spooling and network print jobs etc server-side. Obsd does not have FAQ about that, but freebsd has pretty good article: https://www.freebsd.org/doc/handbook/printing.html And almost everything covered by it is true for openbsd. This here is a good place to start: https://man.openbsd.org/lpd.8 No FAQ for printing, but the man pages are your friend. Many moons ago, I as complete rookie at Unix printing, managed to set up my friends restaurant using an OpenBSD lpd print server to drive all of his receipt and kitchen print jobs. I managed to pull this off using only the man pages. The OpenBSD man pages are a treasure trove of knowledge-- don't always depend on the FAQ's entirely! The FAQ serves to supplement the man pages, not replace them.
Re: print usb printer by [ Google Cloud Print for Chromium ]
Hello Jordan, >> you can do some neat things and avoid having to remove the ulpt(4) driver from the kernel What can be the reason to remove it? If I understand it correctly, this driver provides support for "USB printer class" ( http://www.usb.org/developers/docs/devclass_docs/usbprint11a021811.pdf ) It creates some kind of "channel" (like LPT port) which can be used to query printer status, obtain its ID etc. Application then sends plaintext or PCL or PostScript or whatever printer supports to this "channel". Sysadmin configures "printcap" by adding filters that convert data to PCL or postscript, and lpd creates "pool", while CUPS ties all layers providing IP Printing and other protocols to submit print jobs. Obsd does not have FAQ about that, but freebsd has pretty good article: https://www.freebsd.org/doc/handbook/printing.html And almost everything covered by it is true for openbsd.
Re: Cannot access internet with virtual switch
Thank you Koshibe-san for your reply. Here is the output of ping, after the steps: $ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sendmsg: Network is down ping: wrote 8.8.8.8 64 chars, ret=-1 ... So, it seems the ping fails, except, this time there is some output. > > Interestingly, while searching for addlocal, I encountered a > > presentation on switch [1]. On page 13 of that pdf, there is mention of > > the switch sharing the STP code with bridge. Would it be correct to > > assume that there would be no loops if there was STP in the switch? > > Even with a bridge, you'd need to enable STP and set priority values > on the ports for it to work, so you're correct - if there were any > loops, the bridge probably wouldn't have worked either. But you've > also seen that, for switch(4), the STP-related options aren't > available in ifconfig, and as far as I can tell switchd doesn't do > topology/loop detection (and probably won't want to rely on (R)STP to > do so). So, the code might be shared, but is likely not used. I do not know much about the network stack, but I went grepping in the source, and I encountered a bstp_create function call in the switch_clone_create function within sys/net/if_switch.c file. This bstp_create function seems to be defined in sys/net/bridgestp.c [2]. I may be wrong here, but the bridge seems to have some kind of STP, since there is the "rstp" in the ifconfig output. Whether the switch does indeed use STP, and if it does, does it work, is something that I unfortunately cannot determine. For tap0, I ran "tcpdump -nettti tap0" on a normal machine, without the above vether. I saw a large stream of messages. Then I ran it on em0 interface. The "tcpdump -nettti em0" closely matched the output of tap0 interface output. This led me to try to understand tap interfaces. I encountered an article [3] and an image [4]. My hunch is that tap0 is sort of the mirror equivalent of em0. In terms of that image, em0 is the green physical NIC and tap0 is the Virtual Uplink Port. And since they are connected to two ends of the same (imaginary) cable, they will have the same set of messages. This leads me to believe that I should pass all traffic on tap0. Again, this is based on my uneducated guess and searching, so I could be wrong. Passing all traffic on tap0 still does not lead to the ping reply. However, doing a tcpdump on em0 shows an echo request and echo reply whiile tcpdump on tap0 only shows an echo reply. This is irrespective of addlocal vether0. Also, this is irrespective of the pf configuration. Now, why does the echo request not show up on tap0 and what is exactly stopping the echo reply to reach the ping command - I cannot determine. I have done the usual block log, tcpdump -netti pflog0 routine. There is infrequent igmp2 output, but nothing related to icmp. In fact, I have also used a one line "pass" file for pf configuration, still no ping reply. Regards, ab [1] - http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/if_switch.c?rev=1.23&content-type=text/x-cvsweb-markup [2] - http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/bridgestp.c?rev=1.65&content-type=text/x-cvsweb-markup [3] - www.innervoice.in/blogs/2013/12/08/tap-interfaces-linux-bridge/ [4] - https://i2.wp.com/www.innervoice.in/blogs/wp-content/uploads/2013/12/VirtualNetwotk.png -|-|-|-|-|-|-|--
Re: print usb printer by [ Google Cloud Print for Chromium ]
On 05/15/18 13:04, Tuyosi T wrote: i think it is impossible to print USB only printers . I have successfully printed to several USB based printers in my time with OpenBSD, ranging from USB thermal receipt printers, USB restaurant dot matrix kitchen printers all the way up to your modern day consumer throw away HP printer. I also have had great success utilizing DB9/DB25 serial line printers with OpenBSD. With a bit of playing around with lpd(8) and your printcap(5) file, you can do some neat things and avoid having to remove the ulpt(4) driver from the kernel while still making the printer fully usable and available to CUPS and over the network.
Re: Viewport for man.openbsd.org -- readability on phones
Hi Solene, Solene Rapenne wrote on Wed, May 16, 2018 at 12:26:10AM +0200: > x...@dr.com writes: >> The "viewport" meta tag significantly improves readability and >> usability on my phone when I add it to http://man.openbsd.org pages: > See no offence here, I wonder what is the context leading to read man > pages on a phone? I can see some reasons for that: * Kernel freeze on your desktop computer, trying to figure out how to get into ddb (or whatever else to do). * Sitting next to your boyfriend on the train, who is using his laptop on his lap. The poor guy is obviously struggling and apparently doesn't quite know what he is doing. You quickly look it up on your phone to help him out and set him back on track. * Trying to do sh(1) scripting on your Android phone, which fails to have the required manual pages installed, and the OpenBSD manuals are easier to read and more precise than the Linux ones. * Remote support. Your client calls you on your cell phone while you are travelling and starts asking questions that require a quick look into the manual for precise answers. * ... :-) Salut, Ingo
Re: Viewport for man.openbsd.org -- readability on phones
Also great for when you need reading material in the restroom. On Tue, May 15, 2018 at 4:34 PM, Marc Espie wrote: > On Wed, May 16, 2018 at 12:26:10AM +0200, Solene Rapenne wrote: > > > > x...@dr.com writes: > > > > > The "viewport" meta tag significantly improves readability and > > > usability on my phone when I add it to http://man.openbsd.org pages: > > > > See no offence here, I wonder what is the context leading to read man > > pages on a phone? > > Happened just monday, got students checking some stuff about some system > functions and showing the documentation to me on their phone during recess. > > In that specific case, it was more practical for them than lugging the > laptop > outside. > >
Re: Viewport for man.openbsd.org -- readability on phones
On Wed, May 16, 2018 at 12:26:10AM +0200, Solene Rapenne wrote: > > x...@dr.com writes: > > > The "viewport" meta tag significantly improves readability and > > usability on my phone when I add it to http://man.openbsd.org pages: > > See no offence here, I wonder what is the context leading to read man > pages on a phone? Happened just monday, got students checking some stuff about some system functions and showing the documentation to me on their phone during recess. In that specific case, it was more practical for them than lugging the laptop outside.
Re: Viewport for man.openbsd.org -- readability on phones
x...@dr.com writes: > The "viewport" meta tag significantly improves readability and > usability on my phone when I add it to http://man.openbsd.org pages: See no offence here, I wonder what is the context leading to read man pages on a phone?
Re: Viewport for man.openbsd.org -- readability on phones
"Ingo Schwarze" wrote:
> But you fail to state what the actual problem is that you are
> trying to solve.
The pages at http://man.openbsd.org/ don't use the screen real
estate of my phone in a sensible way. All pages are "zoomed out"
by default, causing a frustrating user experience for me, when I
read OpenBSD man pages on the phone.
Please look at the screenshots. Here they are side-by-side:
https://viewports.github.io/man/sidebyside.html
The pictures to the left show the problem I'm trying to solve.
The pictures to the right show the solution I want.
> You also fail to state whether you have any
> idea what the root cause of the unstated problem might be.
>
> For example, is it somehow related to the CSS rule
>
> html { max-width: 100ex; } ?
>
> I'm not saying it is, i'm merely asking because i have no idea
> what your problem is.
I don't know the cause of the problem. I'll see if I can find it.
Re: 6.3 just died (not for the first time)
I have seen the same error here on a host around 2 days after the upgrade to
6.3 inclusing patches.
The keyboard wasnt working for me but the panic was the same.
Op 15 mei 2018 om 23:30 heeft Harald Dunkel
mailto:harald.dun...@aixigo.de>> het volgende
geschreven:
Hi folks,
6.3 just died. Last words:
login: kernel: protection fault trap, code=0
Stopped at export_sa+0x5c: movl0(%rcx),%ecx
ddb{0}> show panic
the kernel did not panic
ddb{0}> trace
export_sa(10,800033445e70) at export_sa+0x5c
pfkeyv2_expire(813d4c00,813d4c00) at pfkeyv2_expire+0x14e
tdb_timeout(800033446020) at tdb_timeout+0x39
softclock_thread(0) at softclock_thread+0xc6
end trace frame: 0x0, count: -4
ddb{0}> show registers
rdi 0x800033445e98
rsi 0x813d4c00
rbp 0x800033445e70
rbx 0x800033445e98
rdx 0x81abdff0cpu_info_full_primary+0x1ff0
rcx 0xdeadbeefdeadbeef
rax 0x81387510
r8 0x120
r90x81aa58d8netlock
r10 0x
r11 0x800033445ea0
r12 0x81387500
r13 0x3
r14 0x813d4c00
r15 0x90
rip 0x8121fefcexport_sa+0x5c
cs 0x8
rflags 0x10282__ALIGN_SIZE+0xf282
rsp 0x800033445e70
ss 0x10
export_sa+0x5c: movl0(%rcx),%ecx
ddb{0}> ps
PID TID PPIDUID S FLAGS WAIT COMMAND
74371 82200 1 0 30x82 ttyopngetty
64133 371566 1 0 30x100083 ttyin getty
73177 400616 1 0 30x100083 ttyin getty
2198 160363 1 0 30x100083 ttyin getty
66943 62449 1 0 30x100083 ttyin getty
77195 409193 1 0 30x100083 ttyin getty
30152 89639 1 0 30x100083 ttyin getty
54326 20290 1 0 30x100098 poll cron
813086330 1 0 30x80 kqreadapmd
21604 251912 61088 74 30x100092 bpf pflogd
61088 386173 1 0 30x80 netio pflogd
38994 395332 22137623 30x90 nanosleep zabbix_agentd
92334 256603 22137623 30x90 selectzabbix_agentd
5776 303931 22137623 30x90 netconzabbix_agentd
71818 109922 22137623 30x90 selectzabbix_agentd
28432 430198 22137623 30x90 nanosleep zabbix_agentd
55014 131036 54187 74 30x100092 bpf pflogd
54187 404660 1 0 30x80 netio pflogd
32954 132161 74424 74 30x100092 bpf pflogd
74424 72323 1 0 30x80 netio pflogd
22137 193504 1623 30x90 wait zabbix_agentd
230166037 1 0 30x80 poll openvpn
27849 148250 1 0 30x80 poll openvpn
78572 192037 1 0 30x80 poll openvpn
83974 209100 1 0 30x80 poll openvpn
1297 379204 1 99 30x100090 poll sndiod
72635 52767 1110 30x100090 poll sndiod
59204 423537 1 62 30x100090 bpf spamlogd
51694 290283 46867 62 30x100090 piperdspamd
76899 369277 46867 62 30x100090 poll spamd
46867 52758 1 62 30x100090 nanosleep spamd
51631 64028 1109 30x90 kqreadftp-proxy
74489 238300 13002 95 30x100092 kqreadsmtpd
69227 383337 13002103 30x100092 kqreadsmtpd
95912 255952 13002 95 30x100092 kqreadsmtpd
52092 398675 13002 95 30x100092 kqreadsmtpd
15268 264170 13002 95 30x100092 kqreadsmtpd
23823 51587 13002 95 30x100092 kqreadsmtpd
13002 289905 1 0 30x100080 kqreadsmtpd
39875 399764 1 0 30x80 selectsshd
84492 73143 16575 68 70x90sasyncd
16575 267935 1 0 30x80 selectsasyncd
5600 244082 24905 68 70x10isakmpd
24905 484997 1 0 30x80 netio isakmpd
15412 155977 1 0 30x100080 poll ntpd
71665 62722 35888 83 30x100092 poll ntpd
35888 382324 1 83 30x100092 poll ntpd
79699 454922 42559 74 30x100092 bpf pflogd
42559 472293 1 0 30x80 netio pflogd
90864 469513 67456 73 30x100090 kqreadsyslogd
67456 146341 1 0 30x100082
6.3 just died (not for the first time)
Hi folks,
6.3 just died. Last words:
login: kernel: protection fault trap, code=0
Stopped at export_sa+0x5c: movl0(%rcx),%ecx
ddb{0}> show panic
the kernel did not panic
ddb{0}> trace
export_sa(10,800033445e70) at export_sa+0x5c
pfkeyv2_expire(813d4c00,813d4c00) at pfkeyv2_expire+0x14e
tdb_timeout(800033446020) at tdb_timeout+0x39
softclock_thread(0) at softclock_thread+0xc6
end trace frame: 0x0, count: -4
ddb{0}> show registers
rdi 0x800033445e98
rsi 0x813d4c00
rbp 0x800033445e70
rbx 0x800033445e98
rdx 0x81abdff0cpu_info_full_primary+0x1ff0
rcx 0xdeadbeefdeadbeef
rax 0x81387510
r8 0x120
r90x81aa58d8netlock
r10 0x
r11 0x800033445ea0
r12 0x81387500
r13 0x3
r14 0x813d4c00
r15 0x90
rip 0x8121fefcexport_sa+0x5c
cs 0x8
rflags 0x10282__ALIGN_SIZE+0xf282
rsp 0x800033445e70
ss 0x10
export_sa+0x5c: movl0(%rcx),%ecx
ddb{0}> ps
PID TID PPIDUID S FLAGS WAIT COMMAND
74371 82200 1 0 30x82 ttyopngetty
64133 371566 1 0 30x100083 ttyin getty
73177 400616 1 0 30x100083 ttyin getty
2198 160363 1 0 30x100083 ttyin getty
66943 62449 1 0 30x100083 ttyin getty
77195 409193 1 0 30x100083 ttyin getty
30152 89639 1 0 30x100083 ttyin getty
54326 20290 1 0 30x100098 poll cron
813086330 1 0 30x80 kqreadapmd
21604 251912 61088 74 30x100092 bpf pflogd
61088 386173 1 0 30x80 netio pflogd
38994 395332 22137623 30x90 nanosleep zabbix_agentd
92334 256603 22137623 30x90 selectzabbix_agentd
5776 303931 22137623 30x90 netconzabbix_agentd
71818 109922 22137623 30x90 selectzabbix_agentd
28432 430198 22137623 30x90 nanosleep zabbix_agentd
55014 131036 54187 74 30x100092 bpf pflogd
54187 404660 1 0 30x80 netio pflogd
32954 132161 74424 74 30x100092 bpf pflogd
74424 72323 1 0 30x80 netio pflogd
22137 193504 1623 30x90 wait zabbix_agentd
230166037 1 0 30x80 poll openvpn
27849 148250 1 0 30x80 poll openvpn
78572 192037 1 0 30x80 poll openvpn
83974 209100 1 0 30x80 poll openvpn
1297 379204 1 99 30x100090 poll sndiod
72635 52767 1110 30x100090 poll sndiod
59204 423537 1 62 30x100090 bpf spamlogd
51694 290283 46867 62 30x100090 piperdspamd
76899 369277 46867 62 30x100090 poll spamd
46867 52758 1 62 30x100090 nanosleep spamd
51631 64028 1109 30x90 kqreadftp-proxy
74489 238300 13002 95 30x100092 kqreadsmtpd
69227 383337 13002103 30x100092 kqreadsmtpd
95912 255952 13002 95 30x100092 kqreadsmtpd
52092 398675 13002 95 30x100092 kqreadsmtpd
15268 264170 13002 95 30x100092 kqreadsmtpd
23823 51587 13002 95 30x100092 kqreadsmtpd
13002 289905 1 0 30x100080 kqreadsmtpd
39875 399764 1 0 30x80 selectsshd
84492 73143 16575 68 70x90sasyncd
16575 267935 1 0 30x80 selectsasyncd
5600 244082 24905 68 70x10isakmpd
24905 484997 1 0 30x80 netio isakmpd
15412 155977 1 0 30x100080 poll ntpd
71665 62722 35888 83 30x100092 poll ntpd
35888 382324 1 83 30x100092 poll ntpd
79699 454922 42559 74 30x100092 bpf pflogd
42559 472293 1 0 30x80 netio pflogd
90864 469513 67456 73 30x100090 kqreadsyslogd
67456 146341 1 0 30x100082 netio syslogd
54377 194590 79772115 30x100092 kqreadslaacd
81742 432607 79772115 30x100092 kqreadslaacd
79772 398085 1 0 30x80 kqreadslaacd
Re: Buying new laptop, looking for feedback
I've been using a 3rd gen x1 carbon for half a year now and havent had any problems OpenBSD 6.3-current (GENERIC.MP) #33: Mon May 7 18:59:05 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8261529600 (7878MB) avail mem = 8003121152 (7632MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries) bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017 bios0: LENOVO 20BTS0Y500 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.61 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache 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.1.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz cpu3: 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,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 3 (EXP1) acpiprt3 at acpi0: bus 4 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 10 (EXP6) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: NVP3, resource for PEG_ acpipwrres2 at acpi0: NVP2, resource for PEG_ acpitz0 at acpi0: critical temperature is 128 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpicmos0 at acpi0 "LEN0071" at acpi0 not configured "LEN0048" at acpi0 not configured acpibat0 at acpi0: BAT0 model "00HW003" serial 716 type LiP oem "SMP" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340F" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2494 MHz: speeds: 2601, 2600, 2500, 2300, 2100, 2000, 1800, 1700, 1500, 1400, 1200, 1100, 900,
Re: Viewport for man.openbsd.org -- readability on phones
On 2018-05-15 22.51.43 +0200, Ingo Schwarze wrote: > x...@dr.com wrote on Tue, May 15, 2018 at 07:47:45PM +0200: > > [meta name="viewport" content="width=device-width, initial-scale=1.0"] > > It is not defined in any standard. I have no objection to the rest of your email -- in fact, I agree that "viewport" should not matter and that the Web page should not need to change -- but I do want to clarify whether this is in a standard: https://www.w3.org/TR/html51/document-metadata.html#other-meta """ Extensions to the predefined set of metadata names may be registered in the WHATWG Wiki MetaExtensions page[1]. [ ... ] Conformance checkers may use the information given on the WHATWG Wiki MetaExtensions page to establish if a value is allowed or not: values defined in this specification or marked as "proposed" or "ratified" must be accepted """ [1] https://wiki.whatwg.org/wiki/MetaExtensions Shows "viewport" with the "Proposal" status, with a link to: https://drafts.csswg.org/css-device-adapt/#viewport-meta
Re: Viewport for man.openbsd.org -- readability on phones
Hi,
x...@dr.com wrote on Tue, May 15, 2018 at 07:47:45PM +0200:
> The "viewport" meta tag significantly improves readability and
> usability on my phone when I add it to http://man.openbsd.org pages:
>
> [meta name="viewport" content="width=device-width, initial-scale=1.0"]
There is no way i will use that.
It is not defined in any standard.
And i'm quite selective even with features defined in standards
because HTML and CSS standards are very badly proliferating.
In general, i stick to HTML 5.2 and CSS 2.1.
> My test results:
> - Microsoft Edge on Windows 10 Mobile (phone): significant improvement
I'm absolutely uninterested in test results.
I stick to (reasonably established) standards, and it's the job
of browsers to implement them. If a browser failes to implement
a standard that has been in force for a long time, that's a bug
in the browser and not my problem.
But you fail to state what the actual problem is that you are
trying to solve. You also fail to state whether you have any
idea what the root cause of the unstated problem might be.
For example, is it somehow related to the CSS rule
html { max-width: 100ex; } ?
I'm not saying it is, i'm merely asking because i have no idea
what your problem is.
Yours,
Ingo
Re: OpenBSD 6.3 AMD63 ond Dell Vostro 5470 System BIOS problems
Are you using BIOS/MBR or UEFI/GPT? It latter case, try BIOS/MBR.
OpenBSD 6.3 AMD63 ond Dell Vostro 5470 System BIOS problems
I have a Dell Vostro 5470 and I'm having problems with the BIOS after installing OpenBSD 6.3 AMD63. Simply after post install and reboot, the Dell logo disappears, there is no option to enter the BIOS with F2 or boot by F12. Then I have new access to the laptop installing again by livependrive with linux, FreeBSD or the openbsd itself. Install linux, windows and FreeBSD / NetBSD work normally, but the OpenBSD 6.3 AMD64 I do not want. All this, after post install and reboot. Has anyone solved this in any way? I called Dell and they do not know how to solve it. -- Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
Re: print usb printer by [ Google Cloud Print for Chromium ]
hi all . i at last find i can print if i use the printer which has both cups driver and wifi interface (for example EP-709A). so i do not need to use [ Google Cloud Print for Chromium ] . and i think it is impossible to print USB only printers . at this sate openbsd become everyday OS . --- regards
Re: Viewport for man.openbsd.org -- readability on phones
Tue, 15 May 2018 20:46:44 +0200 x...@dr.com > > Tue, 15 May 2018 19:47:45 +0200 x...@dr.com > > > The "viewport" meta tag significantly improves readability and > > > usability on my phone when I add it to http://man.openbsd.org pages: > > > > Hi anonymous, > > > > Could you please add it on some public space so I can check in Dillo too? > > > > Kind regards, > > Anton Lazarov > > Hi Anton, > > I actually did both. I forgot to mention it but I did test with Dillo, > and it's OK AFAICT. > > The test content is available here: > > https://viewports.github.io/ > https://github.com/viewports/viewports.github.io > > If the first link works you should see a table with rows like this: > > afterboot-original | afterboot-viewport | afterboot-original-png | > afterboot-viewport-png > > The table links to html and screenshots. Are you able to access it? > Hi anonymous, I replied before reading the rest of the message. No visible changes, it looks the same in Dillo I sometimes use to read a manual page on the web. Kind regards, Anton Lazarov
Re: Viewport for man.openbsd.org -- readability on phones
> Tue, 15 May 2018 19:47:45 +0200 x...@dr.com > > The "viewport" meta tag significantly improves readability and > > usability on my phone when I add it to http://man.openbsd.org pages: > > Hi anonymous, > > Could you please add it on some public space so I can check in Dillo too? > > Kind regards, > Anton Lazarov Hi Anton, I actually did both. I forgot to mention it but I did test with Dillo, and it's OK AFAICT. The test content is available here: https://viewports.github.io/ https://github.com/viewports/viewports.github.io If the first link works you should see a table with rows like this: afterboot-original | afterboot-viewport | afterboot-original-png | afterboot-viewport-png The table links to html and screenshots. Are you able to access it?
Re: Viewport for man.openbsd.org -- readability on phones
Tue, 15 May 2018 19:47:45 +0200 x...@dr.com > The "viewport" meta tag significantly improves readability and > usability on my phone when I add it to http://man.openbsd.org pages: Hi anonymous, Could you please add it on some public space so I can check in Dillo too? Kind regards, Anton Lazarov > [meta name="viewport" content="width=device-width, initial-scale=1.0"] > > It was suggested to me by a Microsoft Edge engineer as a fix for > mobile-unfriendly web sites. It was apparently invented by Apple > however, and is also recommended by Mozilla. > > Mozilla and Safari docs: > https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag > https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html > > My test results: > - Microsoft Edge on Windows 10 Mobile (phone): significant improvement > > - Chrome on OpenBSD-current: unaffected > - Firefox on OpenBSD-current: unaffected > - Lynx on OpenBSD-current: unaffected > - Microsoft Edge on Windows 10: unaffected > - Internet Explorer on Windows 10: unaffected > > My test site (with before/after html and screenshots): > https://viewports.github.io/ > > I hope and suspect that this will improve things for other small > screen devices too -- such as Android and iOS phones -- but I am > unable to test that. >
Viewport for man.openbsd.org -- readability on phones
The "viewport" meta tag significantly improves readability and usability on my phone when I add it to http://man.openbsd.org pages: [meta name="viewport" content="width=device-width, initial-scale=1.0"] It was suggested to me by a Microsoft Edge engineer as a fix for mobile-unfriendly web sites. It was apparently invented by Apple however, and is also recommended by Mozilla. Mozilla and Safari docs: https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html My test results: - Microsoft Edge on Windows 10 Mobile (phone): significant improvement - Chrome on OpenBSD-current: unaffected - Firefox on OpenBSD-current: unaffected - Lynx on OpenBSD-current: unaffected - Microsoft Edge on Windows 10: unaffected - Internet Explorer on Windows 10: unaffected My test site (with before/after html and screenshots): https://viewports.github.io/ I hope and suspect that this will improve things for other small screen devices too -- such as Android and iOS phones -- but I am unable to test that.
Re: Buying new laptop, looking for feedback
Hi, The specs on my Dell Latitude E5570 should similar to what you're looking at with the T470s. I'm very happy with running OpenBSD on it. The only limitations that I've noticed are: - I can't adjust screen brightness in OpenBSD. - The dedicated AMD R7 M370 doesn't work, but things run fine with the integrated Intel HD 530 - BIOS/firmware settings for HDD/SSD need to be switched from RAID to AHCI. - Very rarely, no input is registered from the keyboard or touchpad. Seems to be a BIOS bug because I've also observed it once after booting into Windows 10. Otherwise this one may be worth considering esp. if you could get it for a better price than the T470s. OpenBSD 6.3-current (GENERIC.MP) #36: Wed May 9 09:34:27 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17008320512 (16220MB) avail mem = 16484810752 (15721MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xea900 (105 entries) bios0: vendor Dell Inc. version "1.18.6" date 12/08/2017 bios0: Dell Inc. Latitude E5570 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT WSMT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT UEFI SSDT SSDT MSDM SLIC SSDT DMAR TPM2 SSDT ASF! WPBT acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] 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) i7-6820HQ CPU @ 2.70GHz, 2295.40 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,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) i7-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,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) i7-6820HQ CPU @ 2.70GHz, 2294.66 MHz cpu3: 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 MHz cpu4: 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 MHz cpu5: FPU,VME,DE,PSE,TSC,M
Re: Buying new laptop, looking for feedback
OpenBSD is brilliant on the T470s. No issues here. OpenBSD 6.3-current (GENERIC.MP) #0: Mon May 14 14:29:23 MDT 2018 basepr...@stef.traceyemery.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 25491316736 (24310MB) avail mem = 24710721536 (23565MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6f096000 (62 entries) bios0: vendor LENOVO version "N1WET42W (1.21 )" date 12/14/2017 bios0: LENOVO 20HFCTO1WW acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT BOOT BATB SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) RP09(S4) RP10(S4) RP11(S4) RP12(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2694.92 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2693.72 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2693.72 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2693.72 MHz cpu3: 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 58 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus 60 (RP09) acpiprt10 at acpi0: bus -1 (RP10) acpiprt11 at acpi0: bus -1 (RP11) acpiprt12 at acpi0: bus -1 (RP12) acpiprt13 at acpi0: bus -1 (RP13) acpiprt14 at acpi0: bus -1 (RP14) acpiprt15 at acpi0: bus -1 (RP15) acpiprt16 at acpi0: bus -1 (RP16) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP21) acpiprt22 at acpi0: bus -1 (RP22) acpiprt23 at acpi0: bus -1 (RP23) acpiprt24 at acpi0: bus -1 (RP24) acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), P
Buying new laptop, looking for feedback
Hello, I need a new laptop for work, OpenBSD compatible. The lenovo T470s seems interesting (i7, SSD 512GB, 14", 1920x1080) for a price < 1500 euros. Could someone confirm me that it works out of the box? If you know a recent model (that I can still buy online) with similar specs, feedback is welcome too. thx
Re: Cannot access internet with virtual switch
On Mon, May 14, 2018 at 1:01 PM, Aham Brahmasmi wrote: > Thank you Koshibe-san for your reply. > >> I've actually held back on that diff since it's a bit insufficient by itself. > > Ok. > >> Actually, you said that you had just em0 on that switch. Can you try >> adding a local port (addlocal instead of add) alongside em0? It will >> be a vether(4) interface that needs to be given em0's current address, >> in its place. > > Should I be doing the following? And if yes, what address should em0 > have? > > $ cat /etc/hostname.vether0 > inet 1.2.3.4 255.255.255.0 > $ cat /etc/hostname.em0 > inet ?.?.?.? 255.255.255.0 > $ doas ifconfig switch0 create > $ doas ifconfig switch0 add em0 > $ doas ifconfig switch0 addlocal vether0 > $ doas ifconfig switch0 up > > Here, 1.2.3.4 is the external public IP address of the machine > originally assigned to em0. em0 shouldn't have an address, and you'll also want to explicitly enable vether0. Otherwise that looks fine. >> > There is a continuous stream of messages when running "switchd -dvv": >> > ... >> >> I can't say what they are without the full output, but you will tend >> to see broadcasts (periodic or otherwise) like your second example >> even on your bridge. From a second look at your earlier logs, it seems >> the 1->1 'loops' are generated by the switch seeing VLAN traffic in >> other parts of the network. > > Ok. Would sharing the full output of "switchd -dvv" help? I wouldn't worry much about it, unless adding the local port doesn't work for you. > Interestingly, while searching for addlocal, I encountered a > presentation on switch [1]. On page 13 of that pdf, there is mention of > the switch sharing the STP code with bridge. Would it be correct to > assume that there would be no loops if there was STP in the switch? Even with a bridge, you'd need to enable STP and set priority values on the ports for it to work, so you're correct - if there were any loops, the bridge probably wouldn't have worked either. But you've also seen that, for switch(4), the STP-related options aren't available in ifconfig, and as far as I can tell switchd doesn't do topology/loop detection (and probably won't want to rely on (R)STP to do so). So, the code might be shared, but is likely not used. > Regards, > ab > [1] - https://www.openbsd.org/papers/bsdcan2016-switchd.pdf > -|-|-|-|-|-|-|--
