Re: Randomish Reboots on Current

2016-06-20 Thread Daniel Wilkins
On Mon, Jun 20, 2016 at 10:19:36AM +0200, Erling Westenvik wrote:
> On Sun, Jun 19, 2016 at 07:54:45PM -0700, Philip Guenther wrote:
> > On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins  
> > wrote:
> > > Has anyone else been hvaing random reboots on current? The system freezes 
> > > up for
> > > maybe 30 seconds or so, then reboots. I have a hunch that it's something 
> > > with my
> > > wifi card because occasionally during a reboot it'll error saying 
> > > something about
> > > MIC errors and then reboot, or just freeze+reboot during the netstart 
> > > portion of boot.
> > > The other thing that makes me think it's network is that it tends to 
> > > happen during
> > > relatively network heavy things, like when I'm doing ssh X forwarding 
> > > while watching
> > > streaming video, but this isn't always the case.
> > >
> > > This is a recent thing that just seems to have randomly appeared; it was 
> > > working
> > > fine before and then it started rebooting one day; I hadn't updated the 
> > > snapshot
> > > although I've tried that since to see if it helped. There's no panic so I 
> > > don't
> > > have any ddb info, but I've attached dmesg and dmesg.boot.
> > 
> > Saying "before" without what that *means* leaves us guessing.  What
> > was the date of the snapshot or build you had installed *before* this
> > occurred?  Maybe it's still showing in an old /var/log/message.* file?
> 
> And you should probably try upgrading to the newest snapshot released
> yesterday (Jun 19). AFAIK there hasn't been a new snapshot since Jun 2,
> which is the date in your dmesg(8), and there seems to have been some
> commits on iwn(4) on Jun 3.
> 
> -- 
> Erling Westenvik
> 

I upgraded to the latest snapshot while I was in class and the reboot happened 
again
within 10 minutes of me getting home; guess there was no fix in there. The fact 
that I was
fine all day when away from home has me convinced that it's an issue in the WPA 
support
at least, since the problem doesn't manifest at all on open networks.



Re: Randomish Reboots on Current

2016-06-20 Thread Daniel Wilkins
Sorry about that, but the issue appeared separate of an upgrade; I just 
mentioned that
I upgraded to point out that the problem wasn't something that's since been 
fixed.
The messages log (attached anyway) coincides with what I said before; it seem 
to be a
behavior that happens when the network runs into a Michael MIC failure. A bit 
of googling
said that it was a problem which occurs on a network when the router thinks 
that someone's
trying to get around the WPA and that the correct behavior is basically that 
the network
is shut down temporarily; not totally sure where the reboot comes in (doesn't 
handle
something right in the driver, I guess? And it hangs the network card.)


On Sun, Jun 19, 2016 at 07:54:45PM -0700, Philip Guenther wrote:
> On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins  wrote:
> > Has anyone else been hvaing random reboots on current? The system freezes 
> > up for
> > maybe 30 seconds or so, then reboots. I have a hunch that it's something 
> > with my
> > wifi card because occasionally during a reboot it'll error saying something 
> > about
> > MIC errors and then reboot, or just freeze+reboot during the netstart 
> > portion of boot.
> > The other thing that makes me think it's network is that it tends to happen 
> > during
> > relatively network heavy things, like when I'm doing ssh X forwarding while 
> > watching
> > streaming video, but this isn't always the case.
> >
> > This is a recent thing that just seems to have randomly appeared; it was 
> > working
> > fine before and then it started rebooting one day; I hadn't updated the 
> > snapshot
> > although I've tried that since to see if it helped. There's no panic so I 
> > don't
> > have any ddb info, but I've attached dmesg and dmesg.boot.
> 
> Saying "before" without what that *means* leaves us guessing.  What
> was the date of the snapshot or build you had installed *before* this
> occurred?  Maybe it's still showing in an old /var/log/message.* file?
> 
> 
> Philip Guenther
Jun 17 00:00:01 Hetalia newsyslog[12898]: logfile turned over
Jun 17 00:00:01 Hetalia syslogd: restart
Jun 17 00:11:07 Hetalia ntpd[52754]: tls connect failed: 2607:f8b0:4003:c03::69 
(www.google.com): connect: No route to host
Jun 17 00:15:24 Hetalia apmd: battery status: high. external power status: not 
connected. estimated battery life 60% (122 minutes)
Jun 17 00:26:08 Hetalia ntpd[62489]: tls connect failed: 2607:f8b0:4003:c03::69 
(www.google.com): connect: No route to host
Jun 17 00:35:25 Hetalia apmd: battery status: low. external power status: not 
connected. estimated battery life 50% (103 minutes)
Jun 17 00:41:08 Hetalia ntpd[25317]: tls connect failed: 2607:f8b0:4003:c03::69 
(www.google.com): connect: No route to host
Jun 17 00:42:08 Hetalia apmd: battery status: low. external power status: 
connected. estimated battery life 47%
Jun 17 00:44:37 Hetalia Tor[37431]: Tor v0.2.7.6 running on OpenBSD with 
Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.0 and Zlib 1.2.3.
Jun 17 00:44:37 Hetalia Tor[37431]: Tor can't help you if you use it wrong! 
Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 17 00:44:37 Hetalia Tor[37431]: Read configuration file "/etc/tor/torrc".
Jun 17 00:44:37 Hetalia Tor[37431]: Opening Socks listener on 127.0.0.1:1920
Jun 17 00:44:37 Hetalia Tor[37431]: Parsing GEOIP IPv4 file 
/usr/local/share/tor/geoip.
Jun 17 00:44:38 Hetalia Tor[37431]: Parsing GEOIP IPv6 file 
/usr/local/share/tor/geoip6.
Jun 17 00:44:38 Hetalia Tor[37431]: We were built to run on a 64-bit CPU, with 
OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks 
accelerated support for the NIST P-224 and P-256 groups. Building openssl with 
such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) 
would make ECDH much faster.
Jun 17 00:44:38 Hetalia Tor[37431]: Bootstrapped 0%: Starting
Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 5%: Connecting to directory 
server
Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 80%: Connecting to the Tor 
network
Jun 17 00:44:40 Hetalia Tor[37431]: Bootstrapped 85%: Finishing handshake with 
first hop
Jun 17 00:44:41 Hetalia Tor[37431]: Bootstrapped 90%: Establishing a Tor circuit
Jun 17 00:44:48 Hetalia Tor[37431]: Tor has successfully opened a circuit. 
Looks like client functionality is working.
Jun 17 00:44:48 Hetalia Tor[37431]: Bootstrapped 100%: Done
Jun 17 00:45:17 Hetalia /bsd: iwn0: Michael MIC failure
Jun 17 00:48:28 Hetalia syslogd: start
Jun 17 00:48:28 Hetalia /bsd: iwn0: Michael MIC failure
Jun 17 00:48:28 Hetalia /bsd: OpenBSD 6.0-beta (GENERIC.MP) #2149: Mon May 30 
17:15:14 MDT 2016
Jun 17 00:48:28 Hetalia /bsd: 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Jun 17 00:48:28 Hetalia /bsd: real mem = 8237068288 (7855MB)
Jun 17 00:48:28 Hetalia /bsd: avail mem = 7982821376 (7613MB)
Jun 17 00:48:28 Hetalia /bsd: mpath0 at root
Jun 17 00:48:28 Hetalia /bsd: scsibus0 at mpath0: 

Re: Randomish Reboots on Current

2016-06-20 Thread Erling Westenvik
On Sun, Jun 19, 2016 at 07:54:45PM -0700, Philip Guenther wrote:
> On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins  wrote:
> > Has anyone else been hvaing random reboots on current? The system freezes 
> > up for
> > maybe 30 seconds or so, then reboots. I have a hunch that it's something 
> > with my
> > wifi card because occasionally during a reboot it'll error saying something 
> > about
> > MIC errors and then reboot, or just freeze+reboot during the netstart 
> > portion of boot.
> > The other thing that makes me think it's network is that it tends to happen 
> > during
> > relatively network heavy things, like when I'm doing ssh X forwarding while 
> > watching
> > streaming video, but this isn't always the case.
> >
> > This is a recent thing that just seems to have randomly appeared; it was 
> > working
> > fine before and then it started rebooting one day; I hadn't updated the 
> > snapshot
> > although I've tried that since to see if it helped. There's no panic so I 
> > don't
> > have any ddb info, but I've attached dmesg and dmesg.boot.
> 
> Saying "before" without what that *means* leaves us guessing.  What
> was the date of the snapshot or build you had installed *before* this
> occurred?  Maybe it's still showing in an old /var/log/message.* file?

And you should probably try upgrading to the newest snapshot released
yesterday (Jun 19). AFAIK there hasn't been a new snapshot since Jun 2,
which is the date in your dmesg(8), and there seems to have been some
commits on iwn(4) on Jun 3.

-- 
Erling Westenvik



Re: Randomish Reboots on Current

2016-06-19 Thread Philip Guenther
On Sun, Jun 19, 2016 at 1:59 PM, Daniel Wilkins  wrote:
> Has anyone else been hvaing random reboots on current? The system freezes up 
> for
> maybe 30 seconds or so, then reboots. I have a hunch that it's something with 
> my
> wifi card because occasionally during a reboot it'll error saying something 
> about
> MIC errors and then reboot, or just freeze+reboot during the netstart portion 
> of boot.
> The other thing that makes me think it's network is that it tends to happen 
> during
> relatively network heavy things, like when I'm doing ssh X forwarding while 
> watching
> streaming video, but this isn't always the case.
>
> This is a recent thing that just seems to have randomly appeared; it was 
> working
> fine before and then it started rebooting one day; I hadn't updated the 
> snapshot
> although I've tried that since to see if it helped. There's no panic so I 
> don't
> have any ddb info, but I've attached dmesg and dmesg.boot.

Saying "before" without what that *means* leaves us guessing.  What
was the date of the snapshot or build you had installed *before* this
occurred?  Maybe it's still showing in an old /var/log/message.* file?


Philip Guenther



Randomish Reboots on Current

2016-06-19 Thread Daniel Wilkins
Has anyone else been hvaing random reboots on current? The system freezes up for
maybe 30 seconds or so, then reboots. I have a hunch that it's something with my
wifi card because occasionally during a reboot it'll error saying something 
about
MIC errors and then reboot, or just freeze+reboot during the netstart portion 
of boot.
The other thing that makes me think it's network is that it tends to happen 
during
relatively network heavy things, like when I'm doing ssh X forwarding while 
watching
streaming video, but this isn't always the case.


This is a recent thing that just seems to have randomly appeared; it was working
fine before and then it started rebooting one day; I hadn't updated the snapshot
although I've tried that since to see if it helped. There's no panic so I don't
have any ddb info, but I've attached dmesg and dmesg.boot.
OpenBSD 6.0-beta (GENERIC.MP) #2165: Thu Jun  2 08:37:59 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8237068288 (7855MB)
avail mem = 7982804992 (7612MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries)
bios0: vendor LENOVO version "G1ETA2WW (2.62 )" date 01/10/2014
bios0: LENOVO 2344BZU
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! 
UEFI UEFI MSDM SSDT SSDT DMAR UEFI DBG2
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.48 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
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.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 1197.28 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
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) i5-3320M CPU @ 2.60GHz, 1197.28 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
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) i5-3320M CPU @ 2.60GHz, 1197.28 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu2 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu3 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2
acpitz0 at acpi0: critical temperature is 200 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0071" at acpi0 not configured
"LEN0015" at acpi0 not configured
"SMO1200" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "45N1107" serial 24045 type LION oem "LGC"
acpiac0 at acpi0: AC unit offline
"LEN0078" at acpi0 not configured
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured