Date: Mon, 16 Mar 2015 19:31:49 +0100 From: Michael Fuckner <michael@fuckner.net> To: Konstantin Belousov <kostikbel@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Ryan Stone <rysto32@gmail.com>, Steven Hartland <killing@multiplay.co.uk> Subject: Re: Server with 3TB Crashing at boot Message-ID: <55072195.40609@fuckner.net> In-Reply-To: <20150316154022.GD2379@kib.kiev.ua> References: <5505827D.6060404@fuckner.net> <5505982E.9060201@fuckner.net> <20150315193202.GS2379@kib.kiev.ua> <2138577776.537937.1426455964006.JavaMail.open-xchange@ptangptang.store> <20150316091758.GY2379@kib.kiev.ua> <5506ADA4.8020207@fuckner.net> <20150316103140.GA2379@kib.kiev.ua> <5506B23F.20400@fuckner.net> <20150316105301.GB2379@kib.kiev.ua> <5506E8D6.30703@fuckner.net> <20150316154022.GD2379@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> kernel crashed instantly with the patches, bu maybe I made a mistake, >> serial was doing strange things. Recompiling now and booting again. I'll >> keep you updated. > Try to apply only the first patch for now, keeping the second (leaky patch) > out of scope. first patch doesn't look good, looks like ahci explodes ahcich0: AHCI reset... ahcich0: SATA connect timeout time=10000us status=00000000 ahcich0: AHCI reset: device not found ahcich1: AHCI reset... ahcich1: SATA connect time=1800us status=00000113 ahcich1: AHCI reset: device found ahcich1: AHCI reset: device ready after 0ms ahcich2: AHCI reset... ahcich2: SATA connect timeout time=10000us status=00000000 ahcich2: AHCI reset: device not found ahcich3: AHCI reset... ahcich3: SATA connect timeout time=10000us status=00000000 ahcich3: AHCI reset: device not found ahcich4: panic: boundary failed: ctx 0xfffff801a4c2ca00 start 0x131000 end 0x133000 boundary 0x1000 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff81c5e6f0 vpanic() at vpanic+0x189/frame 0xffffffff81c5e770 kassert_panic() at kassert_panic+0x132/frame 0xffffffff81c5e7e0 dmar_bus_dmamap_load_something() at dmar_bus_dmamap_load_something+0x35e/frame 0xffffffff81c5e890 dmar_bus_dmamap_load_buffer() at dmar_bus_dmamap_load_buffer+0x246/frame 0xffffffff81c5e910 bus_dmamap_load() at bus_dmamap_load+0x8d/frame 0xffffffff81c5e990 _nvme_qpair_submit_request() at _nvme_qpair_submit_request+0x1ca/frame 0xffffffff81c5e9e0 nvme_qpair_submit_request() at nvme_qpair_submit_request+0x38/frame 0xffffffff81c5ea10 nvme_ctrlr_start() at nvme_ctrlr_start+0x7b/frame 0xffffffff81c5ea80 nvme_ctrlr_start_config_hook() at nvme_ctrlr_start_config_hook+0xe/frame 0xffffffff81c5eaa0 run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x7c/frame 0xffffffff81c5eac0 boot_run_interrupt_driven_config_hooks() at boot_run_interrupt_driven_config_hooks+0x20/frame 0xffffffff81c5eb50 mi_startup() at mi_startup+0x118/frame 0xffffffff81c5eb70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why db> http://dedi3.fuckner.net/~molli123/temp/11-ixgbe.log I'll reboot now and check if I patched the file correctly. But this takes 45min. At least I figured out how to remove the empty Lines (Ctrl-a, shift-A). Don't run minicom inside a screen ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55072195.40609>