Kernel panic (possibly inteldrm related)

2017-07-23 Thread Laurence Tratt 
>Synopsis:  Kernel panic (possibly inteldrm related)
>Category:  kernel
>Environment:
System  : OpenBSD 6.1
Details : OpenBSD 6.1-current (GENERIC.MP) #0: Sun Jul 23 11:17:14 
BST 2017
 
ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
Since the inteldrm update on both my desktop (a Skylake machine) and
laptop (X1 Carbon 3rd gen) I have experienced random kernel panics.
I've now had a ddb trace from both machines (both panic with "malloc:
out of space in kmem_map"). The first ddb (from the desktop) is here
(from a kernel a few days old; limited information as my keyboard didn't
work at the ddb prompt):

  https://imagebin.ca/v/3UPGaXO2uK54

The second (from the laptop with snapshot from yesterday and a kernel
built today) is here:

  https://imagebin.ca/v/3UPI4KUtloXi

and then various output from ddb (tar file with several JPEGs inside):

  https://www.dropbox.com/s/xuhzpmftvz9vshj/ddb_output.tar?dl=0

extsmaild (http://tratt.net/laurie/src/extsmail/) appears to be causing
the final panic, but given that it's just in a "wake every 60 seconds
and see if new files have appeared in a directory" loop, I'm not sure
why. I have also tried killing it, and still experienced at least 1 or 2
panics (albeit not ones that have ended up in ddb), so I suspect
extsmaild is a symptom but not the cause. Interestingly, if I "boot -c"
and "disable inteldrm" the panics go away on my desktop (I haven't yet
tried this on my laptop).

The dmesg below is from my laptop with a snapshot from yesterday and a 
kernel
built today.
>How-To-Repeat:
Happens intermittently (generally within a hour of light-to-medium
usage).
>Fix:
Unknown.

dmesg:
OpenBSD 6.1-current (GENERIC.MP) #0: Sun Jul 23 11:17:14 BST 2017
ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 8238284800 (7856MB)
avail mem = 7982817280 (7613MB)
User Kernel Config
UKC> quit
Continuing...
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (66 entries)
bios0: vendor LENOVO version "N14ET35W (1.13 )" date 04/07/2016
bios0: LENOVO 20BTS05Q00
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP 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, 2594.44 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,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2594442560 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.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 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,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) i7-5600U CPU @ 2.60GHz, 2594.00 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,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) i7-5600U CPU @ 2.60GHz, 2594.00 MHz
cpu3:

Re: armv7/sunxi/sxie

2017-07-23 Thread Mark Kettenis 
> Date: Sat, 22 Jul 2017 11:21:31 +0300
> From: Artturi Alm 
> 
> Hi,
> 
> anyone else having issues with sxie? w/bsd.rd from latest snapshot
> it was unable to get ip from dhcpd even.
> 
> this is what it does look like at the other side:
> 
> 11:01:15.170089 e6:29:5b:e9:e6:29 5b:e9:e6:29:5b:e9 5be9 342: 
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629
> 11:01:15.170353 e6:29:5b:e9:e6:29 5b:e9:e6:29:5b:e9 5be9 342: 
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629 5be9 e629 5be9 e629 5be9
>  e629 5be9 e629
> 
> just to make sure there was nothing physically wrong in my setup,
> i attached usb-ethernet(axen), and got the ip like expected, this
> was in a row to the earlier garbage w/o rebooting in between.
> 
> i haven't used it for like a year, so got no time frame when this
> has appeared, anyone w/ideas?
> -Artturi

I'm upgrading my A10s-ALinuXino-Micro over sxie(4), so the driver
defenitely still works for me.

Re: v6 autoconf broken in bsd.rd

2017-07-23 Thread Florian Obser 
On Sat, Jul 22, 2017 at 02:05:27PM -, Christian Weisgerber wrote:
> On 2017-07-22, Florian Obser  wrote:
> 
> > reenabling debug output on the ramdisk I see this:
> >
> > engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 1 - 25467
> > configure_dfr: 1
> > engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 2 - 25467
> > configure_address: 1
> > engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 3 - 25467
> > configure_address: 1
> > configure_interface: vio0
> > configure_interface: vio0
> > fatal in main: SIOCAIFADDR_IN6: File exists
> > # RTM_NEWADDR: vio0[1]
> > RTM_NEWADDR: vio0[1]
> > RTM_DELADDR: vio0[1]
> > engine exiting
> > fatal in engine: msgbuf_write: Broken pipe
> >
> > Maybe you can only have one v6 address on the ramdisk?
> 
> Well, I can manually configure additional addresses:
> 
> --->
> # ifconfig egress
> em0: flags=208843 mtu 1500
> lladdr 00:0d:b9:41:06:a4
> llprio 3
> groups: netboot egress
> media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
> status: active
> inet 172.16.0.2 netmask 0xff00 broadcast 172.16.0.255
> inet6 fe80::20d:b9ff:fe41:6a4%em0 prefixlen 64 scopeid 0x1
> inet6 fddd:28ee:243:0:384d:91e7:fefc:b697 prefixlen 64 autoconf 
> autoconfprivacy pltime 2171 vltime 520983
> inet6 fddd:28ee:243::2 prefixlen 64
> inet6 2003:e5:cbc0:a01::2 prefixlen 64
> <---
> 

This is a problem with the kernel routing table not being mpatch
capable, you can see this with v4, too:

# ifconfig vio0
vio0: 
flags=248843 
mtu 1500
lladdr 52:54:00:c7:09:1b
llprio 3
groups: egress
media: Ethernet autoselect
status: active
inet 192.168.178.178 netmask 0xff00 broadcast 192.168.178.255
inet6 fe80::5054:ff:fec7:91b%vio0 prefixlen 64 scopeid 0x1
# route -n show -inet
Routing tables

Internet:
DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
default192.168.178.1  UGS04 - 8 vio0
127/8  127.0.0.1  UGRS   00 32768 8 lo0
127.0.0.1  127.0.0.1  UHhPl  12 32768 1 lo0
192.168.178/24 192.168.178.178UCPn   10 - 4 vio0
192.168.178.1  54:67:51:de:e7:ce  UHLchP 12 - 3 vio0
192.168.178.17852:54:00:c7:09:1b  UHLPl  0   16 - 1 vio0
192.168.178.255192.168.178.178UHPb   00 - 1 vio0

# ifconfig vio0 inet alias 192.168.178.179/24
ifconfig: SIOCAIFADDR: File exists
# ifconfig vio0
vio0: 
flags=248843 
mtu 1500
lladdr 52:54:00:c7:09:1b
llprio 3
groups: egress
media: Ethernet autoselect
status: active
inet 192.168.178.178 netmask 0xff00 broadcast 192.168.178.255
inet6 fe80::5054:ff:fec7:91b%vio0 prefixlen 64 scopeid 0x1
# route -n show -inet
Routing tables

Internet:
DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
127/8  127.0.0.1  UGRS   00 32768 8 lo0
127.0.0.1  127.0.0.1  UHhPl  12 32768 1 lo0
192.168.178.17852:54:00:c7:09:1b  UHLPl  0   16 - 1 vio0

note how we lost a bunch of routes, including 192.168.178.0/24
now you can add 192.168.178.179/24:

# ifconfig vio0 inet alias 192.168.178.179/24
# route -n show -inet
Routing tables

Internet:
DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
127/8  127.0.0.1  UGRS   00 32768 8 lo0
127.0.0.1  127.0.0.1  UHhPl  12 32768 1 lo0
192.168.178/24 192.168.178.179UCPn   10 - 4 vio0
192.168.178.17852:54:00:c7:09:1b  UHLPl  0   16 - 1 vio0
192.168.178.17952:54:00:c7:09:1b  UHLPl  01 - 1 vio0
192.168.178.25208:62:66:8b:84:20  UHLcP  01 - 3 vio0
192.168.178.255192.168.178.179UHPb   00 - 1 vio0

# ifconfig vio0
vio0: 
flags=248843 
mtu 1500
lladdr 52:54:00:c7:09:1b
llprio 3
groups: egress
media: Ethernet autoselect
status: active
inet 192.168.178.178 netmask 0xff00 broadcast 192.168.178.255
inet6 fe80::5054:ff:fec7:91b%vio0 prefixlen 64 scopeid 0x1
inet 192.168.178.179 netmask 0xff00 broadcast 192.168.178.255



here is the same thing for IPv6:

# ifconfig vio0 inet6 2001:db8::1/64
# route -n show -inet6
Routing tables

Internet6:
DestinationGateway