Re: MacBookAir5,2 panic at boot on aml running -current

[Mike Larkin]

On Mon, Aug 08, 2016 at 10:47:39AM +0200, si...@slackware.it wrote:
> Hello OpenBSD developers,
> I'm running -current on a MacBookAir5,2 and it panics very early at startup 
> with the following message: 
> https://sid77.slackware.it/tmp/macbookair_panic.jpg which I've transcribed 
> below.
> 
> 3402 Called: \_SB_.BAT0.UBIF
> 34e3 Called: \_SB_.BAT0._BIF
> 34e3 Called: \_SB_.BAT0._BIF
> panic: aml_die aml_convert:2075
> Stopped at Debugger+0x9: leave
> TID PID UID PRFLAGS PFLAGS CPU COMMAND
> * 0 0 0 0x1 0x200 0 swapper
> Debugger() at Debugger+0x9
> panic() at panic+0xfe
> 
> _aml_die() at _aml_die+0x193
> aml_convert() at aml_convert+0x6d
> aml_store() at aml_store+0x175
> aml_parse() at aml_parse+0xf4c
> aml_eval() at aml_eval+0x1c8
> aml_parse() at aml_parse+0x183d
> aml_eval() at aml_eval+0x1c8
> aml_evalnode() at aml_evalnode+0x74
> acpibat_getbif() at acpibat_getbif+0x73
> acpibat_getbif() at acpibat_getbif+0x5f
> acpibat_getbif() at acpibat_getbif+0x1bc
> acpibat_getbif() at acpibat_getbif+0x140
> end trace frame: 0x81abaac0, count 0
> 
> This is happening with both 6th and 7th August snapshots, wasn't happening on 
> the 5th and haven't tried the 8th August snapshot yet.
> I know this is not enough for a bug report, but the panic happens so early on 
> boot that the internal usb keyboard of the laptop is not working yet (except 
> for the power button) nor an external one (tested, just in case).
> 
> Cheers,
> Marco
> 
> -- 
> Marco Bonetti
> 

Following up on old emails ...

If this is still an issue, we'll need a sendbug from the snapshot that worked.

-ml

uvm_fault at fd_getfile

[Vegar Linge Haaland]

Hi, I am having some trouble troubleshooting a kernel crash and would like
to ask for some help debugging.
Sorry if this is the wrong list.

Its running on an ESXi. I don't have any physical hw to test on easily
available. 
I've had this error on 5.9 release, and a couple of current version up to
and including the one I am testing with now (from 05.09.16).
I have not yet tested on 6.0 release.

I am trying to use logstash+elasticsearch on OpenBSD (from packages) as a
central logging service.
But after logging for a couple of days it crashes with the following
message:
(I am writing this off screen,  there might be typos..)

uvm_fault(0x81911d00, 0x806511c8, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at fd_getfile+0x17: movq0(%rax,%rdx,8),%rax
ddb{1}>trace
fd_getfile() at fd_getfile+0x17
sys_close() at sys_close+0x33
syscall() at syscall+0x27b
--- syscall (number 6) ---
End of kernel
End trace frame: 0x12ad31441950, count: -3
0x12as2d87624a:

Now I get this error a while (~30 seconds) after starting elasticsearch.
I have placed some pictures of the output from trace, ps, show registers and
show vnode at: tmp.vegarlh.com
ddb>show vnode (http://tmp.vegarlh.com/fd_getfile%20panic4.PNG) shows a
negative usercount and hldcnt. It this normal?

Any clues as on how to troubleshoot further would be appreciated.
Unfortunately I haven't found a way to reproduce the error with a simper
setup yet.

OpenBSD 6.0-current (GENERIC.MP) #2421: Mon Sep  5 07:50:28 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8573091840 (8175MB)
avail mem = 8308776960 (7923MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (364 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 09/17/2015
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3)
S16F
(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3)
PE5
0(S3) [...]
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) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2492.93 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
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 65MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.26 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.24 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 0, package 1
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.03 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 1, package 1
cpu4 at mainbus0: apid 4 (application processor)
cpu4: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.51 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 0, core 0, package 2
cpu5 at mainbus0: apid 5 (application processor)
cpu5: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.22 MHz
cpu5:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu5: 256KB 64b/line 8-way L2 cache
cpu5: smt 0, core 1, package 2
cpu6 at mainbus0: apid 6 (application processor)
cpu6: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2493.45 MHz
cpu6:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AE
S,XS
AVE,AVX,HV,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu6: 256KB 64b/line 

Re: OpenBSD 6.0 IPv6 issue / kernel crash

[J.Sauer]

Martin Pieuchot wrote
> On 05/09/16(Mon) 16:39, Jens Sauer wrote:
>> Hello OpenBSD Community,
>> 
>> today i played a little bit with cisco routers and IPv6.
>> It seems like a plain OpenBSD 6.0 install crashes while
>> i reduced the IPv6 (cisco) RA parameters to a really short ammount.
>> This behaviour was for me reproducible three times.
>> 
>> All Screenshots and pcap files captured hopefully helps you
>> to find/solve the problem.
>> 
>> The crash occurs while i was pinging the R1 router continuosly
>> on it's IPv6 address 2001:db8:1000::1.
>> While pinging, i changed on R1 the RA plivetime and vlifetime from
>> 60/30 to 5/3. After a short time OpenBSD crashed!
>> 
>> I hope i have put enough information inside the .zip file for you to
>> figure out the problem.
> 
> Could you try a -current snapshot?  A lot of cleanup happened in this
> area and I'd like to know if you can still reproduce this crash.
> 
> Thanks,
> Martin

Hello Martin,
hello OpenBSD Community,

I have tested it again with OpenBSD 6.0 current #2250 and could reproducible
get the same result (Kernel Crash). Seems like the ping isn't involved
because the kernel crash happens even without it after changing the
RA p-/vlifetime to 5/3. The crash occurs just a couple of seconds after it.

This is a serious bug! An advertising IPv6 Router could crash a connected
OpenBSD6 Host (rtsol) just by changing the p-/vltime to short ammounts!

Snapshot: cd60.iso 2016-09-05
http://ftp.halifax.rwth-aachen.de/openbsd/snapshots/amd64/

Regards

J.Sauer

PS: Attachment: new screenshots( kernel crash/trace/ps), pcap and some more
infos.
OpenBSD6_current_snapshot.zip

  



--
View this message in context: 
http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-0-IPv6-issue-kernel-crash-tp303736p303794.html
Sent from the openbsd dev - bugs mailing list archive at Nabble.com.

Re: Boot fails on i386 -current

[Eivind Eide]

2016-09-03 23:04 GMT+02:00 Philip Guenther :
>
> Can you apply this patch in /usr/src/sys/dev/acpi/ and see if the
> resulting kernel works?  If so, please use sendbug to send in the acpidump
> output.
>
Got the problem of the unrelated compile error out of the way, so now
I can compile stock generic kernel. (Still same problem with that.)
https://marc.info/?l=openbsd-misc=147311135204412=2

However, with the acpi patch I get a different compile error, related
this time. Have I applied the patch wrong? I checked carefully

(...snip...)
cc  -Werror -Wall -Wimplicit-function-declaration  -Wno-main
-Wno-uninitialized  -Wframe-larger-than=2047  -fno-builtin-printf
-fno-builtin-snprintf  -fno-builtin-vsnprintf -fno-builtin-log
-fno-builtin-log2 -fno-builtin-malloc -fno-pie -O2 -pipe -nostdinc
-I../../../.. -I. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE
-DACCOUNTING -DKMEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG
-DSYSVSEM -DSYSVSHM -DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES
-DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660
-DUDF -DMSDOSFS -DFIFO -DFUSE -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN
-DTCP_SIGNATURE -DART -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE
-DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DKVM86
-DAPERTURE -DMTRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DEISAVERBOSE
-DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
-DWSDISPLAY_DEFAULTSCREENS="6" -DX86EMU -DONEWIREVERBOSE -DMAXUSERS=80
-D_KERNEL -MD -MP  -c ../../../../dev/acpi/acpimadt.c
../../../../dev/acpi/acpimadt.c: In function 'acpimadt_attach':
../../../../dev/acpi/acpimadt.c:258: error: 'struct cpu_attach_args'
has no member named 'cpu_number'
../../../../dev/acpi/acpimadt.c:311: error: 'struct cpu_attach_args'
has no member named 'cpu_number'
*** Error 1 in /usr/src/sys/arch/i386/compile/GENERIC (Makefile:1021
'acpimadt.o')
#



-- 



Eivind Eide

"ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD"
- Oceania Association of Autonomous Astronauts

Re: OpenBSD 6.0 IPv6 issue / kernel crash

[Martin Pieuchot]

On 05/09/16(Mon) 16:39, Jens Sauer wrote:
> Hello OpenBSD Community,
> 
> today i played a little bit with cisco routers and IPv6.
> It seems like a plain OpenBSD 6.0 install crashes while
> i reduced the IPv6 (cisco) RA parameters to a really short ammount.
> This behaviour was for me reproducible three times.
> 
> All Screenshots and pcap files captured hopefully helps you
> to find/solve the problem.
> 
> The crash occurs while i was pinging the R1 router continuosly
> on it's IPv6 address 2001:db8:1000::1.
> While pinging, i changed on R1 the RA plivetime and vlifetime from
> 60/30 to 5/3. After a short time OpenBSD crashed!
> 
> I hope i have put enough information inside the .zip file for you to
> figure out the problem.

Could you try a -current snapshot?  A lot of cleanup happened in this
area and I'd like to know if you can still reproduce this crash.

Thanks,
Martin